Base Cobalt adds conditional transactions and issuer controls

Base activated its Cobalt upgrade on mainnet on Sept. 30, adding transactions that wait for specified onchain conditions and new controls for assets using its B20 standard. The upgrade changes both how a transaction becomes eligible for inclusion and how issuers can manage token transfers. The Block’s report on Base’s launch says Cobalt is the network’s third mainnet upgrade.

How do Cobalt’s conditional transactions work?

Validity Transactions are signed transactions paired with conditions on chain state; Base holds them until those conditions match, according to the network’s explanation reported by The Block. For example, a swap can become eligible only if a pool reaches a specified USDC price before a set block. If the condition is not met in time, the transaction is never included.

That differs from a transaction submitted for ordinary inclusion, which competes for a place under the network’s usual fee rules without waiting for a user-defined state condition. The conditional route gives users a way to specify both a trigger and a deadline. Base says submissions can remain private until they land. The mechanism therefore offers more control over execution criteria, while tying eligibility to the conditions attached to each transaction.

What new powers does Cobalt give B20 issuers?

Cobalt extends B20, which Base introduced with its Beryl upgrade in June, with three additions: composite transfer policies, scheduled multiplier updates and a seizure function. Composite Policies let issuers combine existing allowlists and blocklists using AND or OR logic. A recipient, for example, could be required to appear on both a KYC list and an accreditation list.

Scheduled Multiplier Updates let issuers schedule changes to how an asset balance is displayed, including for a stock split; Base says existing Beryl integrations will continue to work. The new seizeWithMemo function lets an authorized administrator reassign a holder’s balance when seizure is enabled, with the transaction recording the source, destination, amount and memo onchain. Cointelegraph reports issuers choose whether to enable the function and who can use it, and Base cannot initiate transfers itself. These controls can support compliance and asset administration, while putting consequential transfer permissions in issuer hands.

What should users and developers watch next?

The near-term test is how applications and issuers use the new transaction and B20 functions, including whether integrations adopt scheduled multiplier updates and composite policies. Base’s announcement, as reported by The Block, also listed future plans: reducing block times from two seconds to 200 milliseconds, adding protocol-level support for sponsored fees and bundled transactions, and adopting some changes planned for Ethereum’s Glamsterdam upgrade. Those remain plans; Cobalt’s confirmed changes are the live conditional transaction system and B20 additions. Cointelegraph’s account of the upgrade also places it alongside Base’s recent push into tokenized finance, including B20’s use for tokenized stocks.