reduce start delay blocks (#559) #563
Merged
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
* allow client to optimistically provide contract with the block hash for start_block + 1 * contract will verify provided hash was correct as part of highscore check * contract will also check hash prior to minting beasts * contract also provides a public slay_invalid_adventurers that can be used to slay adventurers started with wrong hash
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…k hash is available
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.
attack()after 11 blocks will work same as it did previously but now clients can callset_starting_entropy(adventurer_id, block_hash)when start_block + 1 hash is available and proceed to callattack()immediately after.