Alternative using timestamps to approximate teleport duration #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's an alternative to calculating teleportation period duration using
block.timestamp/ UNIX epochtime. It provides a simple approach on figuring duration aside from calculating future block times.It's not perfect, it doesn't account for leap seconds or for issues with block producers setting a future timestamp. However, for short durations and non-time specific critical use cases it provides an easy to configure alternative.
Pending: Update to README and providing different options in the REPO rather than replacing the existing Blackhole.sol contract.
This is not ready for a merge. Presenting for review / strategies / discussion. 👍