Network Information
Block Building
This page outlines how Base blocks are built.
Overview
This section describes how blocks are ordered on the Base networks. The ordering is separate from the UX, for example the sequencer could be building Flashblocks every 200ms, without these Flashblocks being exposed publicly. In this scenario, block ordering would change but the user experience would remain consistent. The Base networks are currently configured in the following ways:| Network | Current Configuration | Upcoming Deployments |
|---|---|---|
| Base Mainnet | Flashblocks | None |
| Base Sepolia | Flashblocks | None |
Configurations
Flashblocks
Currently, blocks are built using op-rbuilder and priority fee auctions occur every 200ms. There are two changes from the vanilla ordering to be aware of:Timing
Flashblocks are built every 200ms, each ordering a portion of the block. Unlike the current system where later-arriving transactions with higher priority fees can be placed at the top of the block, Flashblocks creates a time-based constraint. Once a Flashblock is built and broadcast, its transaction ordering is locked even if a transaction with a higher priority fee arrives later, it cannot be included in earlier, already built Flashblocks.High Gas Limits
If your app creates transactions with large gas limits, we recommend monitoring to detect any changes in inclusion latency. Transactions with gas limits over 1/10 of the current block gas limit (currently 14 million gas), face additional constraints:- Each Flashblock can only use a portion of the block’s total gas limit
- Flashblock 1: up to 1/10 of the total gas
- Flashblock 2: up to 2/10 of the total gas
Vanilla
Blocks are built every 2s by op-geth. Transactions within those blocks are ordered by priority fee, see the (code).Changelog
- 7th July: Enabled Flashblocks on Base Mainnet
- 15th May: Ended testing Flashblocks on Base Mainnet
- 15th May: Started testing Flashblocks on Base Mainnet
- 25th Feb: Enabled Flashblocks on Base Sepolia
Per-Transaction Gas Maximum
On September 10, we’ll begin enforcing a per‑transaction gas cap of 16,777,216 gas (2^24) on Base. This aligns Base with the in‑flight L1 proposal, improves network predictability, and has no effect on fees for typical users. We’ll activate it first on Base Sepolia on September 3, then activate it on Base mainnet temporarily for one day on September 10 as a warning. This will be activated permanently on Base mainnet on September 17.
What’s changing
Today, a single transaction can request any gas up to the block gas limit. With this change, transactions that specify gas > 16,777,216 will be rejected by the mempool before inclusion.Why we’re doing this
- Predictability & resilience. Bounding single‑tx execution reduces extreme outliers and makes block building more stable.
- Consistency with Ethereum. The L1 community is converging on a 2^24 per‑tx cap; we’re aligning early so builders don’t have to juggle different rules across layers.
- No practical impact for most builders. The overwhelming majority of Base transactions are far below this cap.
Action items for developers
- If you manually set large gas limits, update your code to stay ≤ 16,777,216.
- For batch jobs or complex on‑chain work, split large jobs into smaller calls.
- If you maintain custom tooling, surface a clear message when the cap hits.
FAQ
- Does this change the block gas limit or fees? No. This is a per‑transaction guardrail.
- Will contract deployments break? Typical deployments are well below the cap. If yours isn’t, consider slimming bytecode or chunking initialization.
eth_sendTransaction or eth_sendRawTransaction will return a JSON-RPC error (for example: exceeds maximum per-transaction gas limit). This cap does not change the block gas limit or the block validity conditions (that will come later with EIP 7825).