The layer-two network Base, developed by the American cryptocurrency exchange Coinbase, activated the Cobalt upgrade on 30 September. For issuers of B20-standard tokens, the fork adds the ability to schedule balance multipliers, seize balances with a record, and combine transfer policies. This makes the rules applied by a token more explicit and the issuer's identity more important.
The Cobalt upgrade specification states that mainnet activation was scheduled for 30 September, a week after Sepolia. Base's public status page indicated that the mainnet maintenance window opened at 18:00 UTC and closed at 20:00 UTC. The fork adds B20 asset features, chain-state-dependent transactions, a registry for scheduling future upgrades in monitor mode, and an on-chain method for registering designated attesting signers in a trusted execution environment. These are separate changes. The asset story begins with B20, the token format introduced in the previous Beryl upgrade.
The fork has launched, but not all of its features have been implemented
Two ideas previously discussed as part of Cobalt are absent from its current implementation. Paying network fees in B20 tokens was removed from the fork's task list on 29 September. Faster canonical blocks with a 200-millisecond response time belong to the proposed later Denim upgrade, not this activation. Native account abstraction has no mainnet gateway scheduled. Treating any of these features as working Cobalt features would create confusion between the roadmap and the code an issuer or trader can use today. This distinction matters especially for institutions assessing the token standard against current requirements.
According to the upgrade documentation, the minimum Base node version for mainnet is v1.4.2 . The previous version v1.4.1 included a timestamp but contained no changes to the forwarding of RPC requests confirming transaction validity; version v1.4.0 does not include mainnet activation. A node that follows the fork without correctly relaying the new transaction type may present a partial view of what users consider a single network. A code-level distinction is more telling than a general statement that Cobalt has launched.
The news hook is real, but it is not the whole point. The previous B20 activation already made it possible to place issuer-managed assets on Base. Cobalt expands what an issuer can do and complicates decisions related to transferring funds. The key question is who can invoke these features, under what legal obligation, and how a holder can verify the outcome.
A B20 balance is a bookkeeping entry naming the issuer
A tokenized stock product can be represented as a balance on Base, while rights to the underlying security sit with a broker, custodian, or contractual issuer. The token standard by itself cannot force a registrar to recognize a wallet owner as a shareholder. The link between on-chain balances and off-chain ownership rights is established by offering documents and the organizations responsible for collateral, redemption, and corporate actions. A token can be simultaneously technically transferable and restricted by contractual obligations.
The description of Coinbase's tokenized stock launch speaks of a market where collateral mechanisms and eligible users matter as much as trading interfaces. In this context, Cobalt's additions are not just developer conveniences. A policy can exclude a specific address, require a condition to be met, or permit only a certain class of transfers. An administrative seizure can change a balance. A multiplier can change how balances are displayed across different accounts. Each feature can support a legitimate operational need while also creating dependence on the issuer's decision or the security of an administrative key.
The B20 format must be examined at the token level. The fact that Base supports seizeWithMemo does not grant every B20 issuer the right to seize every token, let alone every ERC-20 token on Base. The B20 precompile reference states that a token whose issuer has not configured the corresponding policy slot has no seizure capability. An auditor must verify that token's policy and authorized accounts. Two assets using the same standard can have entirely different holder rights.
This is the first separation of control that can be sketched on a whiteboard: the blockchain decides whether a transaction complies with the established rules; the issuer decides which authorized administrative call to send; and the real-world asset provider is responsible for whether the token meets an enforceable requirement. Cobalt changes the first two layers. It does not solve the problem of the third. The same address can trade a token on-chain and still fail off-chain compliance checks at redemption.
Read also:
