Network Status and Incident History
status.base.org reports the live status of Base Mainnet and Base Sepolia components, including block production, batch submission, Flashblocks, the transaction pool, deposits, withdrawals, and the public RPC API.- Incident history: status.base.org/history lists past incidents with their timelines and resolutions.
- Notifications: subscribe on status.base.org to receive incident updates.
- Postmortems: Base publishes detailed postmortems for major incidents on the Base Engineering Blog, for example the June 25th block production outage postmortem.
Audits
Third-party audit reports for the Base Stack are published in the open-source repositories they cover. Each report lists its scope, the reviewed commit, the findings, and how each finding was resolved.- Smart contracts: base/contracts audits, including the multiproof, proof, Cobalt, and dynamic upgrade contract reviews.
- Node and precompiles: base/base audits, including the B20 precompile and dynamic upgrade node reviews.
- Audit competitions: Immunefi reports, including the Azul hardfork competition.
OptimismPortal contracts, are in Optimism’s security reviews.
Bug Bounties and Audit Competitions
Base runs bug bounty programs on HackerOne (offchain components and infrastructure) and Cantina (deployed smart contracts), and ran a public Immunefi audit competition for the Azul upgrade. See Report a Vulnerability for award limits, scope, and how to submit a report.Censorship Resistance and Sequencer Liveness
Base currently operates a single active sequencer. The sequencer runs as a high-availability cluster in which leadership transfers to a follower if the current leader stops producing blocks. See the Flashblocks architecture for the components involved. If the sequencer censors your transactions or stops producing blocks, you can still get a transaction onto Base by sending it as a deposit through theOptimismPortal contract on Ethereum:
- Deposits must be included. Each L1 block defines the deposits that must be included in the first L2 block of its sequencing epoch. A block that omits them is invalid under the derivation rules.
- Maximum delay. If the sequencer does not post batches to Ethereum, nodes wait one sequencing window and then derive the missing L2 blocks themselves, including the pending deposits. On Base the sequencing window is 3,600 L1 blocks, about 12 hours at a 12-second L1 block time (see Configuration).
Open-Source Sequencer Components
The software that orders and sequences Base transactions is open source:
The ordering rules these components implement are described in Transaction Ordering. Node operators independently derive and verify the canonical chain from batches and deposit data published on Ethereum.