EIP-8138 Hard Fork Meta: BPO3 (Hardfork Meta - BPO3)

No call decision · Scaling & data · EIP status Draft · created 2026-01-27

A meta EIP that formally records the third BPO upgrade (BPO3), which adjusts only blob capacity parameters without a full network upgrade. The specific values and activation timing have not yet been finalized.

Why it is needed

Ethereum is progressively increasing the capacity of blobs, the space rollups use to post data. Previously, changing even a single blob count required waiting for a major network upgrade, a hard fork. Thanks to the Blob-Parameter-Only (BPO) upgrade mechanism introduced by EIP-7892, blob-related values can now be changed on their own. However, if such changes happen frequently, it becomes hard to track which values applied at which stage and when. Following the earlier meta EIPs that recorded BPO1 and BPO2, this EIP officially records the target, maximum, activation time, and derivation rule for the third adjustment, BPO3, in one place, so that client implementers, tool developers, capacity planners, and long-term analysts can all reference the same baseline values.

What changes

Today

After EIP-8138

Who is affected

In depth

The role of BPO upgrades and this meta EIP

A Blob-Parameter-Only (BPO) upgrade, as defined by EIP-7892, changes only blob-related protocol parameters and touches no other protocol behavior. This EIP is the meta EIP documenting the third such upgrade, BPO3. It is not a proposal to change code; its purpose is to record the canonical reference for the changed parameter values and activation information, improving traceability for client implementations, tooling, capacity planning, and long-term analysis. All timestamps are expressed in Unix epoch seconds (UTC).

Parameter derivation rule

BPO3's parameters are derived by a deterministic rule. The Blob Target is set to the Blob Maximum value of the previous upgrade (BPO2), and the Blob Maximum is calculated as that Blob Target multiplied by 1.5, rounded up. The source explains that recording this derivation rule itself, not just the resulting values, improves predictability for client implementations, tooling, capacity planning, and long-term analysis across successive BPO upgrades.

BPO3's parameters are not yet finalized.

In the original's BPO-3 Parameters table, the values for Activation Time (UTC), Blob Target, Blob Max, and Base Fee Update Fraction are all unspecified (TODO). The original states that these values and the activation time will be derived once Ethereum client configurations are finalized, and will be reflected in the EIP once the canonical mainnet settings are confirmed. The example values bpo3Time and blobSchedule.bpo3's target, max, and baseFeeUpdateFraction are likewise placeholders only.

Continuity with past blob schedules

The original records the blob schedules of past upgrades as a basis for comparison. Cancun had a target of 3, a max of 6, and a Base Fee Update Fraction of 3,338,477; Prague had 6, 9, and 5,007,716; BPO1 had 10, 15, and 8,346,193; BPO2 had 14, 21, and 11,684,671. BPO3 is built directly on top of BPO2's parameters as a baseline, continuing the staged expansion toward higher data availability limits.

Security considerations

BPO upgrades adjust blob throughput parameters, which can affect network load characteristics. The original states that careful monitoring, staged rollout, and ecosystem-wide coordination are needed to ensure stability. The Backwards Compatibility, Test Cases, and Reference Implementation sections have not yet been written.

Current status: Draft

This EIP is in Draft status, created on January 27, 2026. All core parameter values remain unconfirmed and several sections are empty, so the content may change going forward. The finalized figures will be reflected in this document once client configurations are set.

Original EIP · ← EIPs