Repository navigation
Conversation
EIP-8198 pairs a slot duration change with an EIP-7892 blob schedule entry at the upgrade, so Bogota inherits the blob target, maximum and update fraction like any named fork after Prague. Drop the provisional 12/18 values from the fork and the tests that asserted them.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## eips/bogota/eip-8198 #3871 +/- ##
=======================================================
Coverage ? 95.01%
=======================================================
Files ? 673
Lines ? 40891
Branches ? 3769
=======================================================
Hits ? 38854
Misses ? 1424
Partials ? 613
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Rewrite the removed blob transition tests to check that the fork block keeps the parent fork's blob target, maximum, and update fraction, and mark the block-level constraint section not applicable.
Remove the sentences describing the EIP-7892 entry, which this EIP no longer carries, and take the fork block's blob counts from the new fork as the other transition tests do.
2 tasks done
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 21, 2026
) * fix(spec-specs,tests): keep the blob schedule unchanged at Bogota EIP-8198 pairs a slot duration change with an EIP-7892 blob schedule entry at the upgrade, so Bogota inherits the blob target, maximum and update fraction like any named fork after Prague. Drop the provisional 12/18 values from the fork and the tests that asserted them. * feat(tests): pin the blob schedule unchanged at the Bogota fork Rewrite the removed blob transition tests to check that the fork block keeps the parent fork's blob target, maximum, and update fraction, and mark the block-level constraint section not applicable. * refactor(test-forks,tests): drop the blob schedule entry mentions Remove the sentences describing the EIP-7892 entry, which this EIP no longer carries, and take the fork block's blob counts from the new fork as the other transition tests do. --------- Co-authored-by: fselmo <fselmo2@gmail.com>
8 tasks done
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
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.
EIP-8198 shortens the slot duration while keeping fee dynamics per unit of wall-clock time close to their previous values, and leaves the blob change to an EIP-7892
BLOB_SCHEDULEentry scheduled with the slot duration change (made explicit in ethereum/EIPs#12552, which drops the provisional blob values from the EIP). #3703 instead hardcoded the provisional target 12, maximum 18 and update fraction 12018519 as Bogota fork constants, so they apply even on networks that keep 12-second slots, and clients copying it (ethrex, reth, geth) ignore the genesis BPO chain from Bogota on; in a local run of the heze-devnet-2 configuration this split Besu, which follows EIP-7892, from ethrex and reth at the first Bogota block with blobs. This keeps Bogota's blob constants inherited like any named fork after Prague, leaving the blob change to a BPO scheduled alongside the slot duration change, and removes the tests that asserted the hardcoded values; the remaining EIP-8198 suite (144) and the Bogota blob suites (tests/cancun/eip4844_blobs/test_excess_blob_gas.py, tests/osaka/eip7918_blob_reserve_price, 9470) fill cleanly.