Cobalt hits Base mainnet with engineering improvements targeting transaction flexibility and upgrade automation

Base, the Coinbase-backed Ethereum Layer 2 network, activated its Cobalt hard fork on mainnet on September 30 at 18:00 UTC. The upgrade landed without significant disruptions after a week-long trial run on the Sepolia test network, and it brings a batch of infrastructure-level changes designed to make the chain more flexible, more efficient, and easier to upgrade in the future.

What Cobalt actually changes

The upgrade ships several distinct engineering improvements, each targeting a different part of Base’s operational stack.

First, there are updates to the B20 native token standard, a precompile originally introduced during the Beryl upgrade. Cobalt refines how B20 operates under the hood, though the practical effect for end users is improved reliability and consistency when interacting with tokens built on the standard.

Second, and arguably the most interesting addition, is the introduction of validity and conditional transactions. These allow a transaction to execute only if specific on-chain conditions are verified at the time of inclusion. If the conditions aren’t met, the transaction simply doesn’t execute.

Third, Cobalt establishes a framework for dynamic on-chain upgrade scheduling. Previously, coordinating hard forks required manual intervention and, in some cases, full restarts of client systems. The new framework lets future upgrades be scheduled and executed with less operational friction, which means less downtime and fewer coordination headaches for node operators.

Finally, the upgrade accelerates the registration process for Trusted Execution Environment (TEE) signers by moving verification fully on-chain. Migrating their registration to an entirely on-chain method removes a dependency on off-chain verification steps, tightening the security model while also speeding things up.

The rollout and its ripple effects

All node operators were required to update their software to Base v1.4.2 or newer ahead of the activation. Major exchanges took precautionary steps. Binance, for instance, halted transfers on the Base network during the upgrade window. Initial reports suggest the activation went cleanly, with no notable issues surfacing in the hours after Cobalt went live.

With Denim, the fourth upgrade in the series, already targeted for October 2026, the next hard fork is imminent.

Where this fits in the Layer 2 landscape

Base has been on an aggressive upgrade cadence in 2026. Azul activated on June 25, Beryl followed sometime after, and Cobalt landed at the end of September. Denim is expected next month. Four hard forks in roughly four months reflects a deliberate strategy to ship improvements incrementally rather than bundling everything into one risky mega-upgrade.

For developers and protocols already deployed on Base, the Cobalt changes are largely backward-compatible. The node software update was mandatory, but application-level code shouldn’t need significant changes. The new transaction types are additive, meaning existing transaction formats continue to work as before.