add state-sync txs in body and handle data in eth/69 messages#26
Closed
marcello33 wants to merge 6 commits intomainfrom
Closed
add state-sync txs in body and handle data in eth/69 messages#26marcello33 wants to merge 6 commits intomainfrom
marcello33 wants to merge 6 commits intomainfrom
Conversation
Author
|
Splitting the PR. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In this PR, we implement the canonical inclusion of state-sync txs in block bodies, as per relative PIP.
This PR reflects the Erigon's changes for two PRs in bor:
The PR introduces a new typed system transaction, which is included to blocks that execute StateSync events.
Such txs have zero gas/fees and does not run EVM code, but anchors all StateSync outcomes into the canonical transaction/receipt set. This results in inclusion of such txs into transactionsRoot, receiptsRoot, and logsBloom.
Also, we implement the ability to send state-sync transaction receipts in eth/69 protocol, allowing nodes to persist the state-sync transaction receipts.
The changes requires a hard fork.