Base Cobalt Goes Live With Conditional Transactions and B20 Tools

Base’s Cobalt upgrade went live on mainnet on Sept. 30, adding Validity Transactions and new controls to its B20 asset standard, according to The Block’s report on the launch, which cited a statement from Base. The changes let users attach conditions to transaction inclusion and give asset issuers more ways to manage transfers and balances.

How do Validity Transactions condition a trade?

Validity Transactions keep a submitted transaction dormant until specified conditions are met, Base told The Block. A trader could set a swap to become eligible for inclusion only if a pool reaches a chosen USDC price before a specified block. If that price condition is met in time, Base can include the transaction; if not, it is never included.

The conditions govern eligibility for inclusion. They do not make a trade happen at the target price or guarantee that it will be included. Base described the API as keeping submissions private until they land. That gives traders a way to set timing and state conditions without leaving the transaction visible while it waits.

What changes does Cobalt make to B20 assets?

Cobalt adds Composite Policies, Schedule Multiplier Updates and the seizeWithMemo function to B20. Composite Policies let issuers combine existing allowlists and blocklists with AND or OR logic. A fund could require a recipient to pass both a KYC check and an accreditation check; a transfer would fail if the recipient were removed from either list. Base said issuers can reuse live policies without copying membership lists or synchronizing them offchain.

Schedule Multiplier Updates let issuers schedule a change to how an asset’s balance is displayed, for example to reflect a stock split. The feature aligns B20’s asset multiplier with ERC-8056. Base said existing integrations will continue to work, while new integrations can adopt the updated standard over time.

Who can use seizeWithMemo?

The function lets an authorized administrator reassign a holder’s balance when seizure has been enabled for that asset. Base’s example was an administrator moving shares from a frozen account to a recovery wallet. The transaction records the source, destination, amount and memo onchain. This adds a recorded transfer path for cases where an issuer has enabled seizure; it does not make every B20 asset subject to seizure by default.

The three B20 changes address different issuer tasks: combining eligibility rules, updating displayed balances for corporate actions, and moving balances under enabled seizure controls. Alongside Validity Transactions, Cobalt expands how Base handles conditional execution and asset administration.