Base is an Ethereum Layer 2 (L2): it executes transactions on a separate network, then relies on Ethereum for settlement and security. A sequencer orders Base transactions into blocks. That makes Base feel fast, but it also means users should distinguish quick transaction inclusion from Ethereum-finalized withdrawals.
There is a current architecture change worth knowing. Base launched using the OP Stack, but in 2026 it began moving to a unified Base-operated codebase and release process called base/base. Base says its protocol specifications and code remain public, and independent clients are welcome. That shift changes who publishes node software and how upgrades are shipped; it does not mean Base stopped being an Ethereum L2. Base’s own stack announcement and public node repository describe the move.
This article reflects official Base documentation and project updates checked September 30, 2026. Fee rules, bridge routes, proof windows, and planned upgrades can change, so verify the current docs before moving funds or operating a node.
Base’s documentation describes a user’s transaction charge as two components: an L2 execution fee for processing the transaction on Base and an L1 security fee that estimates the cost of publishing transaction data to Ethereum. The L1 component varies with Ethereum conditions, while the L2 base fee responds to demand on Base. Neither a transaction receipt nor a headline fee total is the same thing as net sequencer revenue: Ethereum data publication and other operating expenses matter when estimating what an operator retains.
Base’s historical agreement with the Optimism Collective used a contribution formula: the greater of 2.5% of sequencing revenue or 15% of profit after L1 data-submission costs. That figure is often repeated as if it were a permanent fee on every Base transaction. It was a revenue-sharing commitment tied to Base’s Superchain participation. In February 2026, an Optimism governance response said the prior Superchain revenue share would not continue as Base moved to its own stack. A separate OP Enterprise customer arrangement was discussed separately and should not be treated as the old Superchain contribution.
The public material checked for this article does not establish a current, complete public split of Base’s gross fee revenue, Ethereum data costs, operating costs, and retained net revenue. Do not infer Base’s profit from transaction volume, average gas fees, or the historic 2.5% / 15% formula alone.
What you can do: When comparing fee claims, identify whether the number is user-paid fees, sequencer gross revenue, data-availability expense, or net profit. For the old revenue-sharing arrangement, read the dated Optimism governance response about Base rather than relying on a legacy explainer.
A canonical withdrawal is the protocol’s direct Base-to-Ethereum exit. It is a three-stage process: start the withdrawal on Base, prove on Ethereum that the withdrawal is included in a valid Base state, then finalize on Ethereum after the applicable proof window. The user needs an Ethereum transaction for the prove and finalize steps, though a relayer or bridge interface may submit them.
As of Base’s Beryl upgrade, activated on mainnet June 25, 2026, the documented finalization window is five days for a single-proof dispute game. A one-day fast path is available when both a Trusted Execution Environment (TEE) proof and a zero-knowledge (ZK) proof back the same proposal. The proof window begins after the withdrawal is proved; posting the relevant Base state to Ethereum usually adds roughly 20 to 60 minutes, plus time and gas to submit the prove and finalization transactions. The one-day option is conditional, not the default promise for every withdrawal.
A third-party fast bridge may deliver funds sooner by using its own liquidity, relayers, or market makers. That service does not shorten Base’s canonical proof window, and it introduces the bridge provider’s separate liquidity, counterparty, and smart-contract risks.
What you can do: Before bridging out, decide whether you need a trust-minimized canonical exit or a faster provider route. Check the bridge’s current route, any liquidity limits, fees, and the exact proof path, then keep enough ETH on Ethereum for the prove and finalize calls if you are using the canonical route.
Base’s withdrawal documentation explains the steps and proof timing. Its Beryl release notes confirm the five-day and one-day windows.
Base announced Stage 1 decentralization in April 2025. The milestone included permissionless fault proofs—anyone can propose or challenge a state claim—and a Security Council that shares control over contract upgrades. Stage 1 reduces reliance on the chain operator for state verification, but it is not the same as eliminating all privileged upgrade or emergency roles.
Base’s current security documentation describes upgrades as requiring both Coinbase signers and the Security Council. It describes a 3-of-6 Coinbase multisig and an 8-of-11 council, with the two groups together requiring a 75% threshold. The documentation’s member roster is dated February 2026. In its February stack announcement, Base said it would add an independent signer in place of Optimism as it transitioned away from the OP Stack. Because council membership and signing arrangements can change, verify the live roster and contract configuration before relying on an old description.
There is another common overstatement: “Base is Stage 2 now because it has multiproofs.” Base’s updates say the multiproof design—combining TEE and ZK proofs—is a step toward Stage 2 and supports faster withdrawals. The latest stack announcement still describes Base as Stage 1 while the team works on its roadmap. A technical feature that supports a stage requirement is not, by itself, proof that all stage criteria are met.
What you can do: Check the current Base Security Council specification, the Stage 1 announcement, and the latest proof-system release. Treat Stage 2 as an objective until Base publishes a status that says it has been reached and independent criteria support that claim.
Base’s 2026 plan centers on running and upgrading the network from its unified stack, publishing releases through base/base, expanding proof systems, and developing Base-specific governance and neutrality safeguards. The roadmap emphasizes open specifications and inviting independent client implementations. That is meaningful, but a public repository is not the same as a diverse set of production clients: operators still need to adopt them, and the network needs to demonstrate that they remain compatible through upgrades.
Base’s Beryl upgrade introduced Reth V2 and shorter withdrawal windows. The next Cobalt mainnet upgrade is listed by Base as scheduled for September 30, 2026, subject to the live status page; node operators were instructed to use Base software version 1.4.2 or later. Because an activation time can move, check the Base status page and the current upgrade calendar before upgrading a node.
Base has also described a longer path toward Stage 2, more proof diversity, and Base-specific governance. These are roadmap items, not guarantees of a date or a particular economic outcome. A move to a Base-operated stack can increase release autonomy and shipping speed while also concentrating more responsibility on Base’s own engineering and governance systems.
What you can do: If you run infrastructure, pin the exact Base release and fork activation before upgrading. If you are evaluating decentralization, track separate evidence for proof participation, council composition, independent clients, upgrade delays, and governance authority instead of relying on a single stage label.
| Claim | What the evidence supports | Action |
|---|---|---|
| “Every Base withdrawal takes one day.” | Five days is the single-proof window; one day is conditional on the dual TEE and ZK path. | Confirm the proof path for your specific withdrawal. |
| “Base still pays the old Superchain revenue share.” | The prior arrangement ended with the move away from Superchain participation; separate commercial arrangements are not the same fee share. | Use recent disclosures and do not extrapolate historic percentages. |
| “Stage 1 means Base has no centralized control.” | Fault proofs are permissionless, while upgrades still involve Coinbase signers and a Security Council. | Inspect the live signer set and upgrade rules. |
| “A fast bridge changes Base’s canonical withdrawal time.” | Liquidity providers can advance funds; they do not change the protocol’s proof window. | Compare convenience with provider and liquidity risk. |
Base combines Ethereum settlement with its own fast sequencer, fee market, withdrawal proofs, and upgrade process. The most useful current distinctions are simple: user fees are not net sequencer profit; the historic Superchain revenue share is not a current Base revenue guarantee; canonical withdrawals are five days or conditionally one day; and Stage 1 decentralization still includes governed upgrade signers. Verify the route, proof window, current council, and node release that apply to your decision.
Primary sources: Base network fees; Base withdrawals; Base’s unified stack roadmap; Base multiproof roadmap.
Learn how Filecoin’s FVM and FEVM relate to storage deals, when to use direct deals or managed tools, and which metrics reveal real network demand.
Understand how Lido’s stETH rewards accrue, what validator concentration means, and how to choose between the withdrawal queue and selling stETH.
Understand how Rocket Pool minipools pair operator and pooled ETH, why rETH can trade away from its protocol exchange rate, and how to assess operator rewards, costs, and risks.
Understand how USDS differs from DAI, when conversion matters, how sUSDS fits in, and which Sky governance changes users should verify in 2026.
How Jupiter routes Solana swaps, what fees users may pay, how JUP governance works, and which execution and aggregator risks matter in 2026.
Learn how Ondo’s OUSG and USDY tokenized Treasury products work, what OUSG’s published instant-redemption limits mean, and which issuer, liquidity, fund, and blockchain risks to check.
Compare JitoSOL, native SOL staking, and JTO governance while tracing MEV tips, protocol fees, buybacks, and the risks that affect realized returns.
Learn how Wormhole Guardians, VAAs, and token routes work, what to verify before bridging, and which warning signs call for a different route.
Learn how Pyth’s pull-oracle model delivers price updates on demand, what update fees cost as of September 2026, and how to protect smart contracts from stale or uncertain prices.
Learn how Injective’s on-chain order books work, what INJ burns actually signal, and how to assess liquidity, trading activity, and bridge dependencies.
