Base has rolled out a network upgrade called Cobalt, adding conditional transactions and new functions for assets issued under its B20 standard. The change is live on the chain, according to the project, and it's aimed at developers building on Base who need more control over how transactions and tokens behave.
What conditional transactions actually do
Conditional transactions let a transfer or contract call execute only when a preset condition is met. On a base level, that means a payment or swap doesn't have to fire the moment it's submitted. Instead, it can wait for a specific state to be true before it goes through.
For builders, that opens up patterns that previously required custom smart contracts or off-chain watchers. A conditional transaction could, for example, depend on another on-chain event or a specific account balance before it's allowed to settle. Base hasn't published a full list of supported conditions, but the upgrade puts the capability directly into the network's transaction flow rather than leaving it to external tooling.
B20 assets get new functions
The Cobalt upgrade also introduces new functions for assets issued under Base's B20 standard. B20 is Base's token format, and the added functions are meant to give issuers and developers more ways to manage and interact with those assets.
Base hasn't spelled out every new function in detail, but the upgrade treats B20 assets as a first-class part of the network's feature set. That's a signal that Base wants its native token standard to be more than a basic transfer mechanism — it's pushing B20 toward the kind of programmable behavior that developers expect from modern token standards.
Why Base is shipping this now
Base has been competing for developer attention against other Ethereum Layer 2 networks, and feature rollouts like Cobalt are part of that push. Conditional transactions and expanded B20 functions aren't cosmetic changes — they touch how transactions are validated and how tokens are issued and controlled.
The upgrade lands without a lot of fanfare, which fits Base's pattern of shipping technical changes and letting developers figure out what to build with them. There's no token sale or incentive program attached to Cobalt, at least not one Base has announced. It's an infrastructure release.
What developers need to check
Anyone running a node, an indexer, or a B20-related service on Base should verify that their tooling handles the new transaction type and the updated B20 functions. Base hasn't said whether old B20 assets are automatically compatible with the new functions or whether issuers need to take action to enable them. That's the first thing to confirm.
For end users, nothing changes immediately — conditional transactions only matter if an app chooses to use them. But over time, wallets and dApps that adopt the feature could start showing pending transactions that wait for conditions to resolve, which is a different experience from the instant-submit model most people are used to.
Base hasn't published a timeline for when the first apps will use conditional transactions or when B20 issuers are expected to adopt the new functions. Developers building on the network now have the tools; what they do with them is the open question.
