Skip to main content

Celestia

Celestia v11 to cap gas from non-blob transactions at 100 million per block under CIP-53

CIP-53, targeting Celestia's v11 upgrade, limits the gas that non-blob transactions can declare in one block to 100,000,000. Blob and PayForFibre transactions are exempt, and no v11 date is set yet.

Celestia's next network upgrade, v11, is set to include a new limit on how much execution work a block can carry. CIP-53, added to Celestia's CIP repository on 29 October 2026, caps the total gas that ordinary (non-blob) transactions may declare in a single block at 100,000,000.

What CIP-53 changes

Today Celestia limits blocks by size in bytes and by message counts, but not by the work needed to execute them: the consensus parameter for maximum block gas is set to -1, meaning no limit. CIP-53 adds a block validity rule for v11:

  • The gas limits declared by all non-blob transactions in a block, other than PayForFibre transactions, must add up to at most 100,000,000 (MaxSDKGas).
  • Block proposers leave out transactions that would push a block past the cap.
  • Validators reject a proposed block that goes over it.
  • The mempool (CheckTx) refuses any single transaction whose declared gas limit is above the cap on its own.

Blob and PayForFibre transactions are left out of the sum, because their gas mainly pays for data bytes rather than execution. According to the proposal, the limit is meant as a general backstop against gas-metered work that grows with its input, including weaknesses not yet found, and works alongside existing per-message limits. In a 3,500-block sample of mainnet, the busiest block declared 3.3 million gas in non-blob transactions, about 3% of the new cap.

The cap is a fixed constant rather than a governance parameter. Asked about this in review, the author said a constant was chosen for consistency and to keep the protection in place.

What it means for validators and delegators

Nothing changes until v11 activates, and no date for v11 has been announced. When it does, the rule is part of block validity, so it comes with the v11 software that validators must run. Going by the mainnet sample, normal traffic is far below the cap, so ordinary users and rollups that post blobs should see no difference. Builders who send unusually gas-heavy non-blob transactions should check that no single transaction declares more than 100,000,000 gas.

Validator status and governance are on the Celestia dashboard.

Sources