BNB Chain Prepares CAS20 Token Standard With Governance-Controlled Activation

Jenner upgrade brings CAS20 token standard to BNB Chain

BNB Chain has released version 1.8.1 of its Jenner upgrade, which introduces CAS20, a new native token standard that separates who can create tokens from who controls them. The Chapel testnet will go live on Oct. 29 at 02:30 UTC, with a mainnet release expected in late November at a time yet to be announced.

CAS20 tokens would be built directly into the blockchain rather than existing as smart contracts. The proposed standard is called BEP-702 and is currently in draft form. Existing BEP-20 tokens, which are the most common type of token on BNB Chain, would not be affected.

The key change is that network governance, not individual issuers, would control whether new CAS20 tokens can be created at all. Issuers could have the technical code ready but still need a separate "feature switch" opened by governance before launching a token.

What CAS20 changes for issuers and holders

• Network governance appoints an activation administrator through GovHub, BSC's governance contract, who decides when token creation features are enabled or disabled.


• There are three separate switches: one for creating Asset tokens, one for creating Stablecoin tokens, and one for writing to a shared policy registry used across tokens.


• Closing a token-creation feature stops new tokens of that type from being created, but does not affect existing tokens or their ability to mint, transfer, or manage roles.


• Disabling shared-policy writes means existing blocked accounts can remain restricted, since the list administrator cannot update the list while the feature is closed.


• Token-level policy binding remains available even when registry writes are disabled, allowing token administrators to assign different policies.

How permissions are split under CAS20

CAS20 divides control into four separate roles: network activation, token role administration, policy selection, and policy-list administration. These roles can be held by the same address or spread across different ones.

Within each token, powers like minting, self-burning, seizing, and pausing are assigned to distinct roles. Seizure, which allows an authorized operator to reassign a holder's balance without their permission, is disabled by default. Even when granted, a token holder must also fail a specific exemption check called SEIZE_EXEMPT_POLICY before their balance can be seized.

Pausing transfers does not pause seizure, which has its own independent pause setting. An account's ability to make ordinary transfers is also separate from whether it can be subject to seizure.

Official source: BNB Chain documentation

The details come from BNB Chain's official Jenner release notes and the proposed BEP-702 draft standard, which outlines the CAS20 architecture including the separation of feature activation, token roles, and shared policy management.

Why this matters for BNB Chain

The CAS20 design aims to give BNB Chain more control over what types of tokens appear on its network, similar to how some other blockchains manage asset launches. For issuers, it means a two-step process: getting the technical setup ready and then waiting for governance to open the relevant feature switch.

BNB Chain is currently seeking early-access issuers for the CAS20 standard, listing both Stablecoin and Asset variants. The project's documentation also warns that because CAS20 behavior is built into the chain's core code, a defect would affect all CAS20 tokens and could require a network-wide upgrade to fix.

What is still unclear

The exact mainnet release date and time have not been announced. It is also unclear which address will hold the activation administrator role once the network goes live, how that administrator will sign changes, and which specific features will be enabled first.

What happens next

The Chapel testnet fork is scheduled for Oct. 29 at 02:30 UTC. After that, BNB Chain will move toward mainnet deployment, with separate decisions still needed on governance addresses, signing procedures, and which CAS20 features are activated.

Sources

• CryptoSlate