Tuesday, October 13, 2026

Creating liberating content

South Korea clears way...

South Korea has established procedures for courts to seize and sell debtors' cryptocurrency...

The Future Of Money...

America is carrying $40 trillion in debt, and the dollar...

EU targets MiCA loophole...

EU finance ministers agreed to shift oversight of major crypto companies to a...

Strategy Smash Buys $21.5M...

Bitcoin juggernaut Strategy has bought more BTC as it pivots...

Base’s Cobalt upgrade adds another rule to affect token balances

Base’s Cobalt upgrade, scheduled for mainnet Sept. 30 at 18:00 UTC, will let issuers of B20 tokens configure balance seizures separately from ordinary transfer restrictions. For a token that enables the feature, a holder could remain free to transfer while still being eligible for administrative reassignment.

B20 is Base’s native ERC-20-compatible token standard, offered in Asset and Stablecoin variants. It already gives administrators control over roles and policies governing balance movements, and now it will also govern the administrative powers over those balances.

Role assignments identify who can exercise a particular power, while policy settings determine which accounts an operation can affect. Changing a token’s rules and executing a balance operation involve distinct permission checks.

Separate seizure permissions

The new administrative operation, called seizeWithMemo, moves a specified amount from a holder to another address. It preserves total supply and skips ordinary transfer policies and holder allowances.

Read More:  The NFT party is over and everybody now owes storage rent

An issuer must configure which accounts lose their exemption before the function can take their tokens. The setting, SEIZE_EXEMPT_POLICY, exempts everyone when left unset. Configuring eligibility alone is insufficient: execution requires SEIZE_ROLE, an unpaused seizure function, a permitted recipient, and sufficient balance.

B20 issuers can separately allow transfers, enable administrative seizure or burn blocked balances, with seizure disabled by default.

A separate recipient policy determines where the seized tokens can go, and leaving that policy unset allows any otherwise valid destination. The holder’s ability to make an ordinary transfer does not answer either seizure-policy question.