BEP-440: Implement EIP-2935: Serve historical block hashes from state #2721
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.
Description
BEP-440: Implement EIP-2935: Serve historical block hashes from state
Rationale
tell us why we need these changes...
Example
use node-deploy(bfc5db87b54db995ac06dd3b38d40a2a77bd89a8) to test
bsc_cluster.sh
, then set up the clusterget blockhash of
blockNumber=11
get zero hash
get blockhash of
blockNumber=12
get expected hash
Changes
code implement following ethereum/go-ethereum#29465
but the logic for deployment is different from the raw eip-2935
Notable changes: