Base activated its third mainnet upgrade, Cobalt, on September 30 at 18:00 UTC, completing its two-hour maintenance window at 20:00 UTC after Sepolia activated the same fork seven days earlier, according to Base's public status page and the Cobalt upgrade specification at basehub.org.

What did the upgrade actually change?

Cobalt adds B20 asset functions, transactions conditional on chain state, a registry for future upgrade scheduling in monitoring mode and an on-chain method for registering certain trusted-execution-environment prover signers. The asset layer is the load-bearing one. Issuers gained:

• Two composite policy types, Union and Intersect, for combining existing B20 transfer rules.
• A scheduled multiplier that changes displayed token balances at a future time without each holder signing.
• A seizure operation, seizeWithMemo, that moves a holder balance under issuer authority when policy permits, superseding the older burnBlocked flow.

crypto.news described the result in its October 1 coverage: "The update introduces Validity Transactions, allowing users to set transactions aside until specified conditions are met, with built-in time limits."

Base's published node minimum moved to v1.4.2 for mainnet. v1.4.1 followed the consensus fork but missed RPC forwarding changes for validity transactions; v1.4.0 does not contain the activation. A node that follows the fork without forwarding the new transaction type correctly presents a partial view of what users treat as a uniform network.

What was removed before activation?

Three items from the public discussion did not ship. Payment of network fees in B20 tokens was dropped from the fork specification on September 29, one day before activation. Faster 200-millisecond blocks belong to a proposed later Denim upgrade, not Cobalt. Native account abstraction has no scheduled mainnet gate in this fork.

The deletions matter for institutional evaluation. A token standard against which a compliance team benchmarks must reflect what an issuer can actually invoke today, not the surrounding roadmap.

How does seizeWithMemo differ from a conventional freeze?

The new operation moves tokens from a holder in one administrative step and can leave a reason marker in the on-chain record, per the B20 issuer operations guide. A smart contract verifies that the calling account has authority and that configured exemptions apply. It cannot decide whether a court order was valid, whether the issuer matched the correct defendant, or whether a holder's complaint should succeed.

The B20 precompile reference specifies that a token whose issuer has not configured the applicable policy slot has no seizure capability. Two assets using the same standard can carry sharply different holder rights.

What does a scheduled multiplier do to a balance?

The function lets an issuer coordinate a corporate action without requiring each holder to sign. If a holder's displayed quantity moves from 10 units to 20 at a 2-for-1 ratio while the economic claim per unit halves, value need not change.

The reconciliation is manual. If token units double while an exchange or oracle retains an old price-per-unit reference, a chart or collateral engine can misstate exposure by a factor of two. Analysts normalizing historical supply must apply the multiplier in force at each timestamp before claiming that deposits surged or supply inflated.

What do Union and Intersect composite policies express?

Union permits an operation if any underlying policy accepts it. Intersect requires multiple underlying conditions to pass. A Union policy can describe transfers allowed to approved broker wallets or a designated redemption contract. An Intersect arrangement can require both sender and receiver to meet separate conditions.

Composite policies can make a regulated asset easier to describe in reusable modules. They can also obscure why a transfer reverted if the interface reports only a generic failure.

Does holding a B20 token settle the underlying claim?

No. A tokenized equity product may appear as a balance on Base while rights to the reference security sit with a broker, custodian or contractual issuer. The token standard cannot force a transfer agent to recognize the wallet holder as a shareholder. The same address may trade a token on-chain and still fail an off-chain eligibility test at redemption.

As tokenized stock volume on Base crossed the $100 million mark earlier this year, the procedures Cobalt operationalizes have shifted from abstract debate into specific design choices facing each issuer.

What should an institution verify before treating a B20 asset as collateral?

• Supply reconciliation. Reported token supply at the backing report's snapshot, adjusted for the multiplier then in force, set against the custodian's stated position at the same timestamp and unit.
• Transfer behavior. Configured policies read directly from the contract. Simulated transfers between eligible, ineligible and redemption addresses compared with published eligibility rules.
• Seizure recourse. An issuer-published case reference for every material administrative move, naming the authority invoked, the applicable term and the appeal channel.
• Lending exemption. Whether the lending contract sits in any exemption the issuer can revoke and what happens to collateral when holder eligibility changes mid-loan.

The chain supplies evidence for each test. It does not supply the answer.

Watch items through the next fork cycle: Base's roadmap points to Denim for 200-millisecond blocks and a separate working item on B20 fee payment, neither of which shipped with Cobalt; settlement assumptions calibrated against the September 30 fork should be re-tested once those changes reach mainnet.