Base Cobalt upgrade turns on conditional trades

The Base Cobalt upgrade is Base's third 2026 mainnet hard fork, and the write-ups that landed on October 1 described a chain that can hold a signed transaction until on-chain conditions match, plus a thicker toolset for issuers of B20 tokens. Base's own engineering post is dated September 30 and does not print a clock. CryptoBriefing and a Bitbase explainer both put mainnet activation at September 30, 18:00 UTC, which is 9:00 p.m. MSK. Crowdfund Insider says the hard fork went live on September 30 after a Sepolia week, without that clock.

TL;DR - Base says Cobalt adds Validity Transactions and three B20 features: composite policies, scheduled multipliers, and seizeWithMemo. - CryptoBriefing says node operators needed v1.4.2 and that Binance paused Base transfers during the window. Bitbase repeats the v1.4.2 floor. - Faster 200 millisecond blocks and paying gas in B20 were not part of this fork, according to Base's "what's next" list and a later explainer.

What actually happened

The company post, Introducing Base Cobalt, says users submit one signed transaction through base_sendRawTransactionValidity with conditions that keep it excluded until every condition is true. The worked example is a swap that waits for a pool price of at least 4,000 USDC and a block number below 1,157,000. If the deadline block arrives first, Base says the transaction is never included. The post says the criteria stay off the trader's public submission until the transaction lands, and that Base does not choose the swap. Meeting the predicate still does not promise inclusion. Ordinary fee competition applies once the transaction is eligible.

On tokens, Base says existing Beryl integrations keep working. Composite policies let an issuer combine a KYC allowlist and an accreditation list with AND or OR, reading each source list at transfer time so a removal blocks the next transfer without a copied member file. Scheduled multiplier updates are aligned to ERC-8056. Base's example queues a 2x multiplier and says a raw balance of 100 stays 100 while wallets that read the multiplier show 200. Nothing is minted or burned in that example. seizeWithMemo lets an authorized administrator move a frozen balance in one transfer and attach a memo, and only if that token has seizure enabled. Base says it does not decide who qualifies and does not initiate the seizure. The issuer does.

Crowdfund Insider's October 1 story, bylined 7:11 a.m. on the page, matches those three B20 additions and adds operational color from the spec: composite policies as AND or OR over live lists, a multiplier that can be canceled before it activates, and seizeWithMemo replacing an earlier burnBlocked path when moving funds is preferred to destroying them. It also says Cobalt includes an L1 registry that could later store fork timestamps, and an on-chain path for registering TEE prover signers by checking Nitro attestations. Indexers, it says, need the updated B20 ABI.

CryptoBriefing, dated September 30, confirms the 18:00 UTC activation, a week on Sepolia before mainnet, and the v1.4.2 node floor. It says Binance halted Base transfers during the window and that early reports showed a clean activation. It is vaguer on B20, calling the token changes a reliability improvement, whereas Base's post names the three functions. Where CryptoBriefing is specific, and the other pages do not contradict it, is the exchange pause and the client version. It also says Denim, a fourth upgrade, is already aimed at October 2026. Base's own "what's next" section lists 200 millisecond blocks, protocol-level smart accounts with gas sponsorship and batching, and a subset of Ethereum's Glamsterdam EVM changes. A Bitbase explainer sourced to crypto.news, read for this draft, says fee payment in B20 was removed from Cobalt on September 29 and that 200 millisecond blocks belong to a later Denim proposal. That lines up with Base putting those items in the future list rather than in the shipped fork. The Bitbase piece is more interpretive than the other two. Its useful hard claims are the ones that match the spec: mainnet at 18:00 UTC on September 30, node minimum v1.4.2, and seizure only where a token policy allows it.

What did not ship

None of this turns a B20 balance into a share. Base's disclaimer says it is not the issuer, broker, or transfer agent for third-party B20 tokens, and that seizure and freezing are the issuer's choices. A tokenized ticker can still fail an off-chain eligibility test. Readers following that market can compare Injective StockDrop and Binance bStocks pairs, which are different venues with their own custody stories.

What to do as a reader

Treat the Base Cobalt upgrade as the September 30 fork, not as the later Denim list. If you run a Base node or an indexer, the check is mechanical: confirm the client is at least v1.4.2 and that your decoder understands the new B20 events. If you hold a tokenized asset on Base, open that token's policy instead of assuming Cobalt gave every contract a seize button. Base says seizure has to be enabled per token. A multiplier changes the displayed unit, not, by itself, the legal claim.

If you are an advanced trader curious about validity transactions, read the docs for fees, ordering, and what happens at the deadline before you sign one. The 4,000 USDC example is an illustration in the engineering post, not a live pool guarantee. The Base Cobalt upgrade is infrastructure. It is not a promise that conditional orders fill, that a token is a stock, or that a faster block time is already live.