Skip to content

Disable blobs in EL #376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DiogoSantoss merged 9 commits into from
Dec 11, 2025
Merged

Disable blobs in EL #376

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
33634ce
Disable Nethermind blobs
KaloyanTanev Nov 6, 2025
525434b
Disable reth blobs
KaloyanTanev Nov 6, 2025
92fefb7
add history pruning and retention epochs
DiogoSantoss Dec 10, 2025
9564d38
rm blobssupport flag
DiogoSantoss Dec 11, 2025
ef1ffbd
uncomment holesky
DiogoSantoss Dec 11, 2025
c3d4674
add full flag to reth
DiogoSantoss Dec 11, 2025
86b63b7
remove txpool limit on reth
DiogoSantoss Dec 11, 2025
dee543b
add defaults
DiogoSantoss Dec 11, 2025
6408a7a
remove nethermind flags
DiogoSantoss Dec 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions compose-el.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,9 @@ services:
--Metrics.Enabled=true
--Metrics.ExposePort=8008
--Sync.SnapSync=true
--Sync.AncientBodiesBarrier=4367322
--Sync.AncientReceiptsBarrier=4367322
--Sync.AncientBodiesBarrier=${NETHERMIND_ANCIENT_BODIES_BARRIER:-0}
--Sync.AncientReceiptsBarrier=${NETHERMIND_ANCIENT_RECEIPTS_BARRIER:-0}
Copy link
Contributor

@OisinKyne OisinKyne Nov 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2025-11-06 at 16 46 42

Setting 0 would mean downloading the full chain. shouldnt we bump this to like 20000000 or higher? (currently at 23.7m on mainnet)

Copy link
Contributor

@OisinKyne OisinKyne Nov 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Digging a little further, does it make sense to prune history with this flag
Screenshot 2025-11-06 at 17 02 50

and maybe we need a pruning trigger too? not clear to me if pruning will happen without one? (doesn't seem right that it wouldn't unless this is set, so maybe i don't understand, maybe its the difference between in-memory pruning vs full pruning, which is what hybrid offers)
Screenshot 2025-11-06 at 17 00 36

--TxPool.BlobsSupport=Disabled
Copy link
Contributor

@OisinKyne OisinKyne Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a new concern about this. IIUC, an update was made to allow a CL to fetch blobs from a local ELs mempool. analysis showed that 30-70% of all blobs get imported this way depending on the client. Disabling the blobpool may hurt performance more than we gain from not proposing blobs in the rare case of a local block. Maybe nethermind will separate this behaviours into a different flag. we probably shouldn't turn on this feature if my concern is valid, will try and dig up the reference i remember on twitter.

Copy link
Contributor

@OisinKyne OisinKyne Nov 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NethermindEth/nethermind#9686. Nethermind addressed this for us :D --Blocks.BlockProductionBlobLimit option

networks: [dvnode]
volumes:
- ./data/nethermind:/nethermind/data
Expand Down Expand Up @@ -68,6 +69,7 @@ services:
--http.addr=0.0.0.0
--http.port=8545
--metrics=0.0.0.0:8008
--txpool.blobpool-max-count=0
Copy link
Contributor

@OisinKyne OisinKyne Nov 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like reth defaults to no pruning (archive node), we should fix that or we'll eat everyone's disk if they swap to reth
Screenshot 2025-11-06 at 17 07 05

networks: [dvnode]
volumes:
- ./data/reth:/reth/data
Expand Down
3 changes: 2 additions & 1 deletion docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,10 @@ services:
--JsonRpc.Port=8545
--Metrics.Enabled=true
--Metrics.ExposePort=8008
--Sync.SnapSync=true
--Sync.AncientBodiesBarrier=${NETHERMIND_ANCIENT_BODIES_BARRIER:-0}
--Sync.AncientReceiptsBarrier=${NETHERMIND_ANCIENT_RECEIPTS_BARRIER:-0}
--Sync.SnapSync=true
--TxPool.BlobsSupport=Disabled
networks: [dvnode]
volumes:
- ./data/nethermind:/nethermind/data
Expand Down