Base Details B20 Seize Functionality and Composite Policies for Cobalt Hardfork
The upcoming network upgrade introduces administrative balance reassignment and multi-policy authorization rules for asset and stablecoin issuers.
Key points
- Base's Cobalt hardfork will introduce seizeWithMemo to reassign balances without reducing token supply 1.
- PolicyRegistry will support composite UNION and INTERSECT policies referencing two to four simple child lists 2.
- The legacy burnBlocked function remains dialable, and seize functionality is strictly opt-in per asset 1.
Documentation released on Sept. 30 details two major updates coming to the Base network's B20 token specification during the upcoming Cobalt hardfork 12. The network is introducing a dedicated administrative seizeWithMemo function alongside composite policy logic in the PolicyRegistry, altering how token issuers handle blocked balances and compliance rules on-chain 12.
At the Cobalt activation, the B20 standard—which governs both standard B20 assets and stablecoins—will gain a native administrative balance transfer mechanism 1. This operation shifts administrative balance removal from the legacy burnBlocked function to seizeWithMemo, allowing an authorized administrator to reassign balances directly to a treasury or specified address without modifying total supply 1. The function is restricted by a new SEIZE_ROLE, an independent pause vector, and two policy slots: SEIZE_EXEMPT_POLICY and SEIZE_RECEIVER_POLICY 1. The legacy burnBlocked method remains callable and unchanged for backward compatibility, though issuers seeking to destroy seized balances must now seize tokens to an intermediate address and subsequently execute a standard burn 1. Base noted that the feature is opt-in per token: unconfigured seize policy slots default to an always-allow state, causing unauthorized seize attempts to revert 1.
Composite Rules in PolicyRegistry
Alongside the balance transfer updates, Base is expanding its PolicyRegistry with composite policies using UNION and INTERSECT gates 2. Previously, combining multiple permissions—such as an internal know-your-customer list and a broader sanctions list—required issuers to manually sync flattened lists using off-chain infrastructure 2.
Under the Cobalt specification, issuers can combine between two and four simple allowlists or blocklists into a single composite policy without copying membership entries 2. Checks are evaluated dynamically against the live state of referenced child policies and short-circuit to optimize execution gas 2. The changes to the registry are strictly additive, maintaining compatibility with existing simple policies deployed during the current Beryl era 2. At the time of writing, broader markets traded flat to slightly lower on the day, with $ETH hovering at $2,673 and total crypto market capitalization at $2.84T. Base confirmed that Cobalt has not yet activated, leaving the new selectors currently undialable on-chain 1.
Questions this story raises
- Does seizeWithMemo reduce total token supply?
- No. Unlike burnBlocked, seizeWithMemo functions as an administrative transfer from a target account to a specified destination, leaving totalSupply unchanged [1].
- Are existing Beryl policies and functions broken by the Cobalt update?
- No. The changes are backward compatible: burnBlocked remains dialable, and existing simple allowlists and blocklists continue to function normally [1][2].
Sources
- [1] B20: Seize Functionality - Base Documentation — docs.base.org, September 30, 2026
- [2] PolicyRegistry: Composite Policies (UNION / INTERSECT) - Base Documentation — docs.base.org, September 30, 2026
Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.