
Base's Cobalt upgrade lets users submit time-bound transactions that stay dormant until set conditions are met, and adds three B20 token standard features.
In brief
- Cobalt adds Validity Transactions, signed transactions held until user-set conditions such as price or block number are met.
- B20 gains Composite Policies, Schedule Multiplier Updates and seizeWithMemo; existing integrations keep working.
- Indexers must update to the new ABI for the hardfork.
What happened
Base announced Cobalt, an upgrade with two main parts: Validity Transactions and B20 enhancements two primary changes.
Validity Transactions let users submit a signed transaction through base_sendRawTransactionValidity with criteria that must all hold before it is eligible for inclusion remain dormant until user-specified criteria are met.
In Base's example, a trader sets a pool price of at least 4,000
USDC and a block bound; the transaction is held while the price sits at 3,950 and lands at 4,012 once both conditions are met Both must hold.
Base says it does not choose the swap or set the conditions Base does not choose the swap.
Why it matters
For traders, the API is neutral infrastructure that keeps submissions private until they land, and users do not need to poll or resend keeping their submissions private until they land.
For issuers, B20 adds Composite Policies that combine allowlists and blocklists with OR or AND logic, Schedule Multiplier Updates aligned with ERC-8056 for events such as splits, and a seizeWithMemo function for authorized administrators where seize is enabled three additions are now live.
Base says existing integrations keep working, but indexers will need to update to the new ABI for the hardfork update to the new ABI.
What to watch
Base plans 200ms blocks, down from 2s, protocol-level smart accounts called Base Transactions, and EVM improvements tied to Glamsterdam Over the coming months.
Separately, Ethereum set Glamsterdam for Sepolia on 6 October with the mainnet date undecided Glamsterdam for Sepolia on 6 October.