Max blob flag for local builders
Authors: , , , , , ,
Canonical data: /latest/eips/7872.json
Adds a flag to set the maximum number of blobs a local builder will put in a block
Timeline
Key Benefits
- ● Gives operators control over blob load.
- ● Mitigates blob availability risks on low bandwidth.
- ● EL-only change with limited surface area.
- ● No changes to transaction or consensus formats.
Trade-offs & Considerations
No trade-offs documented yet.
Stakeholder Impact
End Users
No direct UX changes; transaction semantics remain identical. Only block composition may vary by operator settings.
Application Developers
No EVM or API changes. Apps sending blob transactions behave the same; inclusion depends on local builder caps.
Wallet Developers
No transaction format or signing changes. Wallet functionality unaffected by this configuration-only execution change.
Tooling / Infrastructure
Execution-layer builder tooling should expose and respect a configurable max-blobs parameter. Relays and CL nodes unchanged.
Layer 2s
No protocol changes. Locally built L1 blocks may include fewer blob transactions when operators configure lower caps.
Stakers & Node Operators
Validators running local builders gain a tuning knob aligned with bandwidth. No consensus or fork-choice changes.
CL Client Developers
No code changes expected; EL-only behavior. Headers, fork choice, and gossip remain unchanged for consensus clients.
EL Client Developers
Add a config flag and enforce it during blob tx selection. Validate against protocol maximum and local cap.