-
Notifications
You must be signed in to change notification settings - Fork 51
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
feat(mpt): Block hash walkback #199
Merged
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
This was referenced Jun 2, 2024
This stack of pull requests is managed by Graphite. Learn more about stacking. |
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
3 times, most recently
from
June 2, 2024 00:21
c5c84ef
to
a977461
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
June 2, 2024 00:22
a977461
to
b754306
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
2 times, most recently
from
June 2, 2024 01:55
f2bbbb7
to
547e57e
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
June 3, 2024 22:51
547e57e
to
84055cb
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
June 3, 2024 22:56
84055cb
to
ca017ee
Compare
refcell
reviewed
Jun 4, 2024
refcell
reviewed
Jun 4, 2024
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
June 4, 2024 15:13
ca017ee
to
550522a
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
June 4, 2024 15:32
550522a
to
1b4bde0
Compare
refcell
approved these changes
Jun 4, 2024
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
June 4, 2024 16:04
1b4bde0
to
d3d94fa
Compare
Introduces the implementation for `Database::block_hash` for `TrieDB`, allowing the `BLOCKHASH` opcode to verifiably fetch a block hash within the most recent `256` blocks, not including the block that is currently being executed.
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
June 4, 2024 16:07
d3d94fa
to
5e701e3
Compare
This was referenced Jun 11, 2024
Closed
Closed
Closed
Merged
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.
Overview
Introduces the implementation for
Database::block_hash
forTrieDB
, allowing theBLOCKHASH
opcode to verifiably fetch a block hash within the most recent256
blocks, not including the block that is currently being executed.