Base released "Cobalt," the third network upgrade of the year for the Coinbase-incubated Ethereum layer-2, introducing conditional transaction support and three changes to the B20 token standard that backs Coinbase's tokenized equity products.

According to Base's documentation, the conditional transaction feature lets users submit transactions that stay dormant until specified price or block-height conditions are met. Base lists the new method as running on test networks only, with no mainnet date disclosed.

The mechanism adapts exchange-style conditional orders — limit, stop-loss, take-profit — to on-chain execution, settling once the trigger condition fires.

What does the seize function add to B20?

The upgrade adds three modifications to B20, including a seize function. That capability gives authorized addresses administrative control over tokens issued under the standard. B20 supports Coinbase's tokenized equity offerings, a product line the exchange has expanded across multiple markets.

The two B20 changes accompanying the seize function were not enumerated in the Cobalt release notes, leaving their specific scope undocumented in the public materials reviewed.

Why do conditional transactions matter?

Conditional transactions shift execution responsibility from centralized matching engines to on-chain settlement logic. A dormant transaction encodes its trigger conditions at signing and waits in a pre-confirmation state until those conditions resolve, then propagates and confirms as a standard transaction.

Base's documentation frames the feature as part of the network's effort to bring exchange primitives on-chain without custodial intermediaries.

For active traders, stop-losses, take-profits, and price-triggered entries can now be expressed as signed transactions rather than as instructions routed through a custodian. The dormant stage also means the transaction does not compete for block inclusion until its conditions clear, which can reduce certain MEV-extraction patterns tied to predictable order flow.

What does the compliance posture imply for issuers?

The seize function signals an explicit compliance orientation for B20. Tokenized securities issued under the standard carry on-chain identifiers for the underlying equity, settlement timestamps, and corporate-action hooks. The administrative recovery path introduced in Cobalt gives issuers and authorized counterparties a defined mechanism to retrieve or restrict tokens under specified conditions.

That mirrors how regulated securities operate off-chain, where transfer agents and clearing brokers can place holds, reverse erroneous transfers, and execute court-ordered seizures.

Base's documentation does not state whether the seize function will apply only to tokenized stocks or to other B20-compliant assets, nor does it name the authorized addresses eligible to invoke the function. Those governance details will shape how institutional issuers evaluate the standard for production tokenization pipelines.

What comes next?

Base has not published a mainnet activation date for conditional transactions, and the testnet-only status suggests the feature will undergo further specification changes before production deployment. The B20 modifications ship alongside the Cobalt upgrade itself.

Protocols and market makers building on Base should expect a separate signaling or governance step if conditional transactions move to mainnet, given the feature's implications for mempool dynamics and MEV supply.