Update deneb config vars #18
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
etan-status
reviewed
Nov 8, 2023
filoozom
approved these changes
Nov 8, 2023
Co-authored-by: Etan Kissling <[email protected]>
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.
Complete deneb config with Gnosis custom values
MAX_BLOBS_PER_BLOCKPreset
MAX_BLOBS_PER_BLOCKis set to 6 to have the same block structure as Ethereum mainnet. Having a higher value than what execution allows will increase slightly the DoS vector for invalid blobs. However, now blob sidecars have an inclusion proof, so the vector is highly reduced.With a
MAX_BLOBS_PER_BLOCKhigher than the max gas set in the execution spec, a malicious proposer could create a block referencing more blobs than possible. This block will be valid on consensus rules only. However, the execution node will reject the payload as its gas exceeds the maximum. A malicious proposer would therefore cause the network to consume ~3x more bandwidth than allowed, at the cost of missing a block proposal. Note that there's no free data availability, all nodes will eventually discard the block with too much blobsMIN_EPOCHS_FOR_BLOB_SIDECARS_REQUESTSMIN_EPOCHS_FOR_BLOB_SIDECARS_REQUESTSis increased to match the expected 2 weeks rollups consider today for Ethereum mainnet. The total disk requirement roughly equivalent to Ethereum mainnet since epochs are 2*12/5 faster