Quick answer: Base’s Cobalt hard fork went live on mainnet on September 30, 2026, at 18:00 UTC, after a Sepolia testnet run on September 23. Two things matter most. First, it adds “validity transactions,” signed transactions that Base holds until onchain conditions are met. Second, it gives issuers of B20 tokens (Base’s native token standard) new controls, including a function that lets an authorized admin move a blocked holder’s balance to another address. Those controls are opt-in per token. If an issuer hasn’t configured a seizure policy, that token has no seizure capability. Your wallet, your balances and your addresses don’t change because of the fork itself.
That’s the short version. The longer one is more interesting, because Cobalt quietly changes a basic assumption many crypto users carry around: that holding the keys means holding the asset. For a certain class of tokenized assets on Base, that assumption now comes with fine print.
What Cobalt Is, and Where It Sits in Base’s 2026 Roadmap
Cobalt is a hard fork of Base, the Ethereum layer-2 network incubated by Coinbase. According to a CryptoRank report, it’s Base’s third upgrade of 2026, following Azul in May and Beryl in June. Another summary we read says Beryl is the upgrade that introduced the B20 token standard in the first place, so Cobalt is best read as the follow-up that gives B20 more teeth.
The mainnet timeline, as reported by several outlets that cite Base’s upgrade documentation:
- Sepolia testnet activation: September 23, 2026, 18:00 UTC
- Mainnet activation: September 30, 2026, 18:00 UTC, with a maintenance window from 18:00 to 20:00 UTC
- Required node software: Base v1.4.2 or later (node operators only)
One site we checked gave the activation date as October 1, but that looks like a slip. A documentation update in Base’s public docs repository on GitHub marks Cobalt as live on mainnet at September 30, 2026, 18:00 UTC (Unix timestamp 1790791200), and that matches the other outlets we read.
Validity Transactions: Transactions That Wait
The headline feature for traders is the validity transaction. Per the descriptions published around the upgrade, it’s a signed transaction that Base includes only when specified onchain conditions match. The network holds it, checks the conditions as each block is built, and includes it only once they’re all met.
The conditions can test an account balance, a contract’s storage, a block number, or a Flashblock index. Base’s own examples, as relayed by the coverage, are conditional swaps and state-dependent withdrawals. Think of a limit order, except the condition isn’t limited to price and the check happens at the protocol level rather than in an app’s backend.
Here’s a scenario. Say you want to swap into a token only if your wallet has received a payment you’re expecting, and you want the whole thing to expire if it hasn’t arrived within a set number of blocks. Before, you’d either watch the chain yourself or trust a bot to do it. With a validity transaction, the condition and the deadline travel with the transaction itself.
Early coverage disagreed on whether the feature was live on mainnet or still testnet-only. That has since been settled: Base’s docs repository now removes the “soon” and experimental labels and lists the validity-transaction RPC method (base_sendRawTransactionValidity) as available on both mainnet and Sepolia through sequencer endpoints. Even so, it’s a brand-new feature. If you plan to rely on it, test with a tiny amount first.
B20 Changes: The Part That Affects Holders
B20 is Base’s native token standard, aimed at assets that need compliance logic built in, such as tokenized securities. Cobalt expands what issuers can do with it. The reported changes:
- Scheduled multiplier updates. An issuer can schedule a future change to everyone’s balances, for example to reflect a stock split, without needing a signature from each holder. One summary says this tracks the ERC-8056 standard.
- Union and Intersect policies. Issuers can combine two to four allowlists or blocklists using OR (union) or AND (intersect) logic. A KYC allowlist plus a sanctions blocklist is the obvious pairing.
- Simplified transfer-blocking. The process for stopping a given address from moving a token got easier to configure.
- SeizeWithMemo. Authorized administrators can transfer a blocked holder’s balance to another address, with an onchain memo, instead of destroying it. It replaces the older burnBlocked function, which reportedly still works but is deprecated.
That last one is the item generating the most discussion, and it deserves a plain-English reading. Traditional finance has always had mechanisms to freeze or reassign securities: court orders, regulatory actions, error corrections, lost-certificate processes. If tokenized securities are going to live on a public chain, regulated issuers will want similar tools. Cobalt provides them at the token level.
The flip side is the one crypto veterans notice immediately. For a B20 token with seizure enabled, “not your keys, not your coins” gets a footnote. The key still signs your transactions, but an authorized party may be able to reassign the balance.
The opt-in point is the one to remember
Multiple sources stress the same limit: these powers apply only to tokens whose issuers chose to enable them. As one report put it, a token whose issuer hasn’t configured the applicable policy slot has no seizure capability. Existing tokens on Base aren’t affected just because the network upgraded.
So the practical question isn’t “Can Base seize my assets?” It’s “Does this specific token’s issuer have a seizure policy configured, and who holds that authority?” Those answers differ token by token.
Where the Sources Disagree: B20 Fee Payment
This one’s a small but useful example of why we cross-check. Early planning discussions reportedly included letting users pay network fees in B20 tokens. One report says that item was removed from Cobalt’s scope on September 29, the day before activation. Another summary lists fee payment in B20 tokens among the official changes.
We can’t reconcile those from here. The safer reading is that fee payment in B20 tokens shouldn’t be assumed to be available until you’ve confirmed it in Base’s documentation. The same caution applies to two other items that early coverage mentioned: native account abstraction (EIP-8130) isn’t in Cobalt’s official feature list according to one source, and the faster 200-millisecond blocks were deferred to a later upgrade.
Under the Hood: Dynamic Upgrades and TEE Registration
Two infrastructure changes are less exciting for traders but matter for how Base evolves.
Dynamic upgrades. A smart contract stores upgrade timestamps, and nodes query it to apply changes without requiring a new client release for each one. At launch, mainnet reportedly runs this in “metrics-only mode,” meaning it’s observing rather than driving activations yet.
TEE signer registration. Trusted Execution Environment registration moves to onchain verification of AWS Nitro attestations, which removes a dependency on external RISC Zero proving services. It’s a plumbing change, but it shrinks the number of outside services the chain’s proving setup relies on.
What’s Next: Denim and 200ms Blocks
The next planned fork is Denim. Its documentation page describes Base sealing blocks five times per second instead of once every two seconds, adding a millisecond-resolution clock that contracts can read, and extending RPC responses to report time at that resolution. It would also retire the current Flashblocks system.
Timing is another place sources differ. Several news summaries say Denim is “targeted for October 2026.” The Denim specification page itself lists a Base Sepolia planning target of October 2026 and a Base mainnet planning target of November 2026, and says these are planning targets without confirmed activation timestamps. We’d weight the spec page, since it’s closest to the source.
The same page carries a warning developers should take seriously: contracts that use block counts to measure time (timelocks, vesting, governance windows) would run at one-tenth of their intended length, because block numbers would advance ten times faster while block.timestamp doesn’t change speed. If you build on Base, that’s worth reading before Sepolia activation.
Why This Matters Beyond Base
Base is described by CryptoRank as the largest Ethereum layer-2 by total value locked, at roughly $2.5 billion. That’s a single-source figure and TVL moves daily, so treat it as a rough scale marker only. For a broader look at how Base stacks up against its rivals, see our Arbitrum vs Optimism vs Base comparison.
The bigger story is regulatory design. U.S. regulators have been warming to tokenized assets, a theme we covered in our piece on the CFTC and tokenized assets and in our look at the SEC’s innovation exemption. Institutions that issue tokenized stock will want compliance checks, split mechanics and recovery tools. Cobalt is Base’s bid to be the place that offers them.
It also connects to Ethereum’s own roadmap. One of the summaries lists Glamsterdam’s EVM improvements among Base’s longer-term plans. We track that upgrade in our Glamsterdam explainer.
A Practical Checklist Before You Hold a B20 Token
Imagine you’re offered a tokenized equity on Base and the interface looks like any other token swap. Before you buy, it’s reasonable to ask a few questions:
- Is it a B20 token, and which policies has the issuer configured?
- Is a seizure policy set? If so, who holds the authority, and under what stated conditions can it be used?
- Does the issuer publish how it handles court orders, sanctions screening and errors?
- Does your wallet or exchange (Binance Wallet reportedly supports B20 trading) tell you about these controls, or hide them?
None of this makes tokenized assets bad. It just means the risk model is different from holding ETH or a typical DeFi token. You’re taking on issuer risk alongside market risk.
FAQ
When did the Base Cobalt upgrade go live?
Mainnet activation was September 30, 2026, at 18:00 UTC, following Sepolia on September 23. One outlet reported October 1, but Base’s own documentation update and most other sources say September 30.
Can Base now seize my tokens?
No, not by default. The seizure function applies only to B20 tokens whose issuers configured the relevant policy. Tokens without that policy have no seizure capability, according to reporting on the upgrade.
What is a validity transaction?
It’s a signed transaction that Base includes only when specified onchain conditions, such as a balance, contract storage value, block number or Flashblock index, are met. Base’s documentation lists the feature as available on mainnet and Sepolia, though it’s new, so test with small amounts first.
Do I need to do anything as a regular user?
No. Balances and addresses were unaffected. Node operators needed Base v1.4.2 or later. Binance reportedly paused Base transfers from 17:00 UTC on upgrade day while trading continued.
What is Denim?
Denim is Base’s next planned hard fork, centered on native 200ms blocks. Its spec page lists planning targets of October 2026 for Sepolia and November 2026 for mainnet, without confirmed activation timestamps.
Key Takeaways
- Cobalt activated on Base mainnet September 30, 2026, at 18:00 UTC, after a September 23 Sepolia run.
- Validity transactions let a signed transaction wait for onchain conditions, and Base’s docs list them as live on mainnet.
- B20 issuers gain scheduled multipliers, Union and Intersect policies, and SeizeWithMemo, all opt-in per token.
- Check each token’s policy configuration before assuming it behaves like a plain ERC-20.
- Fee payment in B20 tokens and native account abstraction are reported inconsistently. Verify before relying on them.
- Denim’s 200ms blocks are planned next, with mainnet reportedly targeted for November per the spec page.
Sources
- crypto.news: Base Cobalt upgrade puts new controls inside tokenized assets
- Altcoin Buzz: Base Cobalt Upgrade adds conditional transactions and new B20 rules
- Bitrue: Base Cobalt Upgrade Explained
- CoinGabbar: What Is Base Cobalt Upgrade?
- CryptoRank: Base Ships Cobalt Hard Fork
- SpendNode: Base Activates Cobalt Upgrade With Issuer Controls
- BaseHub: Denim Upgrade Overview
Disclaimer: This article is for educational purposes only and isn’t financial, legal or tax advice. Crypto assets are volatile and tokenized assets carry issuer and regulatory risks. Always do your own research (DYOR) and consult a qualified professional before making decisions.