introduce ForkedBlobSidecar for EIP-7688 Electra period before PeerDAS
#6451
Conversation
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
On `ELECTRA_FORK_EPOCH`, PeerDAS is not yet activated, hence the current mechanism based on `BlobSidecar` is still in use. With EIP-7688, the generalized indices of `BeaconBlockBody` get reindexed, changing the length of the inclusion proof within the `BlobSidecar`. Because network Req/Resp operations allow responses across fork boundaries, this creates the need for a `ForkedBlobSidecar` in that layer, same as already done for `ForkedSignedBeaconBock` for similar reasons. Note: This PR is only needed if PeerDAS is adopted _after_ EIP-7688. If PeerDAS is adopted _before_ EIP-7688, a similar PR may be needed for forked columns. Coincidental `Forked` jank can only be fully avoided if both features activate at the same epoch, actual changes to blobs aside. Delaying EIP-7688 for sole purpose of epoch alignemnt is not worth it.
etan-status
force-pushed
the
dev/etan/df-forkedblobs
branch
from
3a403ba to
d028bae
Compare
Is this particularly possible now? PeerDAS appears to 100% be in Fulu, so I don't see the scenario where PeerDAS is adopted after EIP-7688, even if EIP-7688 also lands in Fulu. |
|
I need this branch for 7688 testing, it is marked as draft. |
* track execution requests for builder API * insert the builder execution requests into the shim state transition
|
nimv2_2 failure is due to CI using incorrect Nim 2.0.6 version |
|
Integrated into This will eventually be rebased on top of Fulu, making this particular component irrelevant (as Fulu likely transitions away from |
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.
On
ELECTRA_FORK_EPOCH, PeerDAS is not yet activated, hence the current mechanism based onBlobSidecaris still in use. With EIP-7688, the generalized indices ofBeaconBlockBodyget reindexed, changing the length of the inclusion proof within theBlobSidecar. Because network Req/Resp operations allow responses across fork boundaries, this creates the need for aForkedBlobSidecarin that layer, same as already done forForkedSignedBeaconBockfor similar reasons.Note: This PR is only needed if PeerDAS is adopted after EIP-7688. If PeerDAS is adopted before EIP-7688, a similar PR may be needed for forked columns. Coincidental
Forkedjank can only be fully avoided if both features activate at the same epoch, actual changes to blobs aside. Delaying EIP-7688 for sole purpose of epoch alignemnt is not worth it.