We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems to be a bit overly prescriptive, especially given the size of the current reward, for certain use cases timestamps should be fairly safe.
Perhaps we can quantify what values, or granularities of time are safe.
Reference: https://ethereum.stackexchange.com/questions/413/can-a-contract-safely-rely-on-block-timestamp/432#432
The text was updated successfully, but these errors were encountered:
@djphillyg you can take this on when you're done your research. :)
Sorry, something went wrong.
Also still asking for a reference on the 12 minute rule.
It lacks a reference on that. I've looked at geth's code and it checks if it's older than the previous block + not more than 15 seconds in the future.
No branches or pull requests
It seems to be a bit overly prescriptive, especially given the size of the current reward, for certain use cases timestamps should be fairly safe.
Perhaps we can quantify what values, or granularities of time are safe.
Reference:
https://ethereum.stackexchange.com/questions/413/can-a-contract-safely-rely-on-block-timestamp/432#432
The text was updated successfully, but these errors were encountered: