Base activated its Cobalt upgrade on mainnet on September 30. The headline features sound unrelated: traders can submit transactions that wait for an onchain condition, while issuers of B20 assets get more programmable transfer and recovery controls.
They are actually part of the same trend. Base is moving behavior that normally lives in exchange software, bots, compliance databases or custom smart contracts closer to the chain itself.
That makes the network easier to use for sophisticated applications. It also means users need to understand that protocol-level convenience can include protocol-level control.
A Transaction Can Now Wait Without a Keeper
Cobalt introduces Validity Transactions. A signed transaction can carry conditions tied to onchain state or block height and remain pending until those conditions are satisfied.
Base gives a simple example: a trader could submit a swap that should only become eligible if a pool reaches a specified price before a specified block. If the condition is met in time, the sequencer can include the transaction. If not, it never lands.
That is not exactly the same thing as a centralized exchange limit order. The condition is attached to a normal account transaction and evaluated by the network’s inclusion machinery rather than by an exchange matching engine.
The practical effect is similar to an intent system, but without requiring every application to deploy a keeper bot or custom settlement contract. That matters as Base becomes a home for increasingly automated activity. Optimisus recently covered DopaMint’s attempt to coordinate more than 250 specialized agents on Base; infrastructure that can express conditions directly at transaction level gives those systems another primitive to build on.
The Transaction Stays Private Until It Lands
Base also says Validity Transactions can keep submissions private until they are included. That is useful for traders because broadcasting an order condition too early can expose intent to searchers, copy-traders or front-running strategies.
Privacy here is narrow. It does not turn Base into a private chain and does not hide the final transaction after inclusion. It reduces pre-inclusion information leakage.
That distinction is important because execution quality increasingly depends on what the market can see before a trade is final, not only what is recorded afterward.
B20 Is Becoming a Compliance Asset Standard
Cobalt also expands B20, Base’s ERC-20-compatible asset standard introduced with the earlier Beryl upgrade.
Composite Policies let issuers combine allowlists and blocklists with AND or OR logic. A tokenized fund, for example, could require a recipient to appear on both a KYC list and an accreditation list. If the address falls off either list, the transfer can fail without the issuer copying membership data into a separate application database.
Schedule Multiplier Updates let issuers change how balances are displayed on a future schedule, which Base positions as useful for events such as stock splits. And seizeWithMemo lets an authorized administrator reassign balances where seizure functionality has been enabled, while recording a memo onchain.
The Seizure Function Is Not a Bug. It Is a Permission Model
Crypto users often treat the ability to freeze or seize a token balance as evidence that an asset is not ‘real’ crypto. Regulated tokenized assets often need exactly those controls.
A security issuer may need to respond to a court order, sanctions designation, compromised account or legal transfer process. Building those functions explicitly into an asset standard can make the authority visible instead of burying it inside a proprietary contract.
The risk is not that seizure exists. The risk is that users do not know who can exercise it, under what conditions and whether that authority can change.
Optimisus made the same point in its recent analysis of tokenized silver: self-custody can coexist with issuer-level freeze and clawback powers. Cobalt makes that trade-off part of a reusable standard rather than a one-off token design.
Base Is Turning the Sequencer Into More Than a Block Builder
Validity Transactions give the Base sequencer responsibility for evaluating whether a signed transaction is currently eligible. B20 policies give issuers reusable controls over who can hold and transfer regulated assets.
Both reduce the amount of custom infrastructure applications need to maintain. Both also move more decision logic into shared network primitives.
That is the real story of Cobalt. The upgrade is not primarily about higher throughput. It is about making the chain behave more like financial infrastructure before the application layer asks it to.
Base says future work includes 200-millisecond blocks, native smart accounts and selected EVM changes from Ethereum’s Glamsterdam roadmap. If those arrive, Cobalt may be remembered less as a feature release than as the point where Base started turning common application patterns into protocol assumptions.
This is not financial advice.
Sources
- Base Status — Cobalt mainnet upgrade completed — Primary network status confirming the September 30 mainnet activation.
- Base Chain — in-flight transaction and B20 features — Primary Base developer surface showing Validity Transactions and B20 capabilities.
- The Block — Base launches Cobalt upgrade — Independent reporting on Validity Transactions, B20 policy composition and seizeWithMemo.
