This repository was archived by the owner on Jan 16, 2026. It is now read-only.
Conversation
This was referenced Jun 2, 2024
Contributor
Author
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
c5c84ef to
a977461
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
a977461 to
b754306
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
2 times, most recently
from
f2bbbb7 to
547e57e
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
547e57e to
84055cb
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
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
ca017ee to
550522a
Compare
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
550522a to
1b4bde0
Compare
refcell
approved these changes
Jun 4, 2024
clabby
force-pushed
the
cl/trie-db-block-walkback
branch
from
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
d3d94fa to
5e701e3
Compare
This was referenced Jun 11, 2024
Closed
Closed
Closed
Merged
theochap
pushed a commit
to ethereum-optimism/optimism
that referenced
this pull request
Dec 10, 2025
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.
theochap
pushed a commit
to ethereum-optimism/optimism
that referenced
this pull request
Jan 14, 2026
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.
This file contains hidden or 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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_hashforTrieDB, allowing theBLOCKHASHopcode to verifiably fetch a block hash within the most recent256blocks, not including the block that is currently being executed.