Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Details on the Approximation of time #4

Open
wighawag opened this issue Aug 20, 2022 · 2 comments
Open

Details on the Approximation of time #4

wighawag opened this issue Aug 20, 2022 · 2 comments

Comments

@wighawag
Copy link

wighawag commented Aug 20, 2022

Hi,

Reading the doc it says about timeForRound:

timeForRound

Given a NetworkInfo object, it calculates the approximate time the given round will be emitted at (approximate because the network must work together to create the randomness).

It would be great if it gave also worst case scenario in both direction or even better a probability distribution on a range of time, so applications can predict accordingly.

I also could not find what to expect on the mainnet, Is it a one minute kind of difference we can expect or a lot more ?
Thanks

@CluEleSsUK
Copy link
Contributor

Right now the network emits random numbers every 3s in testnet, so you can timelock encrypt something for that precision.
The network takes 0.8 seconds right now to generate the randomness together, so the precision isn't ms perfect - we think we can reduce that though!

Our timevault demo works on the order of minutes for nicer UX, but you can definitely have finer grained control.

@wighawag
Copy link
Author

wighawag commented Aug 20, 2022

Thanks @CluEleSsUK for the info. For my use case this should actually be plenty enough.

I leave the issue open as instead of returning a single number it could ideally return more data like mentioned above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants