If you use Base regularly, you have probably never noticed a network upgrade happening. That is by design. But Base does update its underlying protocol on a recurring basis, and understanding what that process looks like can help you tell the difference between normal maintenance and something that actually needs your attention.
Base runs on shared, versioned software
Base is built on the OP Stack, the open source software framework also used by Optimism and several other rollups that together form the Superchain. Because Base shares this codebase, it also shares the Superchain's upgrade schedule. When the OP Stack ships a new protocol version, Base adopts it on its own timeline, usually shortly after Optimism does.
These upgrades are not cosmetic. They can change things like how transaction fees are calculated, how much data a block can hold, how quickly the network confirms deposits from Ethereum, or what opcodes and transaction types the network supports. Some are small technical adjustments. Others, like the original Bedrock upgrade that Optimism and Base were both built around, are foundational changes to how the whole chain operates.
The naming convention
OP Stack upgrades follow a geology theme, moving through the alphabet: Bedrock, Regolith, Canyon, Delta, Ecotone, Fjord, Granite, Holocene, and Isthmus, with more planned. If you see one of these names mentioned in a changelog or a developer announcement, it refers to a specific, dated protocol upgrade rather than a marketing label.
How an upgrade actually rolls out
Unlike a proof of work blockchain where a hard fork depends on miners choosing to run new software, a Base upgrade activates automatically at a predetermined L2 block timestamp that is written into the network's configuration ahead of time. Node operators, including the sequencer that orders Base's transactions, need to update their software before that timestamp. Software that has not been updated in time will diverge from the rest of the network and need to resync once it catches up.
This is coordinated well in advance. Upgrade specifications and target dates are published in the OP Stack's open source repositories and documentation before they go live, which gives node operators, block explorers, RPC providers, and app developers time to test against the new rules before they take effect.
Why you usually will not notice anything
For most wallet users, a Base upgrade is invisible. You are not running node software yourself, your wallet does not need a special update to keep working, and your balances, transaction history, and existing approvals are unaffected. The sequencer and the broader network handle the transition, and normal activity, sending tokens, swapping, bridging, continues through it.
The two exceptions worth knowing about:
Around the exact activation moment, there is a brief window where the network is more sensitive to configuration mismatches between infrastructure providers. This is one reason it is generally sensible to double check a transaction if something looks unusual for a few minutes after a widely publicized upgrade, the same caution you would apply after any major infrastructure change.
Some dapps or bridges may pause deposits or withdrawals briefly around an upgrade if their own infrastructure needs to be updated in step with the network. This is a decision made by the individual app, not a requirement of the upgrade itself, and reputable apps will usually post a notice beforehand.
What actually changes for builders versus users
It helps to separate who an upgrade is really aimed at:
- Node operators and infrastructure providers need to update their software before the activation timestamp, or their node stops following the canonical chain.
- App and contract developers may need to account for new opcodes, gas cost changes, or new transaction types if an upgrade introduces them.
- Wallet users generally do not need to do anything. Your wallet software is separate from the network's protocol layer, and wallets are not usually affected unless an upgrade specifically changes something at the transaction format level that wallet software needs to support, which is communicated ahead of time by wallet developers when it applies.
If you want to follow along
You do not need to track upgrade schedules to use Base safely, but if you are curious, upgrade specifications and activation dates are published in the OP Stack's public documentation and GitHub repositories, and Base's own developer channels typically summarize what is changing in plain language before each activation. This is mostly useful if you build on Base or run infrastructure. As a day to day user, the more practical habit is simply keeping your wallet app updated and paying attention to any notices from the specific dapps or bridges you use, since they are the ones who would flag anything that actually affects you.
The takeaway
Base's protocol evolves through scheduled, publicly documented upgrades inherited from the OP Stack, not sudden or contested forks. The process is built to be boring on purpose, activation happens at a known time, node operators update ahead of it, and the network keeps running. Unless you are running infrastructure or building a contract that depends on very specific protocol behavior, the practical impact on your day to day use of a Base wallet is close to zero.
Sources: Network upgrades, Optimism Documentation, Upgrade 15, Isthmus Hard Fork, Optimism Docs