BNB Chain Sets CAS20 Testnet With Governance Feature Controls

BNB Chain’s v1.8.1 release schedules the Jenner upgrade for the Chapel testnet on Oct. 29 at 02:30 UTC. The upgrade was published on Oct. 16 and is intended to support the next testing phase for CAS20, a proposed token standard described in draft BEP-702.

BNB Chain has provided guidance for a mainnet release in late November, but has not announced an exact time. Existing BEP-20 tokens would not be affected.

BEP-702 separates network feature access from control of an individual token and from the policies that determine which accounts may use specific functions. Governance appoints an activation administrator through GovHub, BNB Smart Chain’s governance forwarding contract. Only GovHub can replace that administrator, and only the appointed, nonzero administrator can activate or deactivate features.

The system has separate switches for creating Asset-variant tokens, creating Stablecoin-variant tokens and writing to the shared policy registry. Once a variant is enabled, its creation process does not require a separate issuer approval list. The creator supplies the initial token administrator and the instructions needed to initialize the asset.

Closing a creation switch would prevent new CAS20 tokens of that variant from launching. It would not stop an existing token from minting units under its own permissions, transferring balances or changing its roles. Installing Jenner support and opening token creation are separate requirements for an issuer preparing a launch.

The shared policy registry creates another network-level dependency after a token is created. Token administrators can select policies for specific operations, while each policy has its own administrator responsible for account membership. If registry writing is disabled, administrators cannot add or remove members or transfer control of a policy. Existing tokens can continue using the current list.

An account already blocked by a transfer policy could remain restricted while registry updates are disabled. Replacing the network activation administrator would restore control of the switch, but would not change the account’s status. The registry would have to be reopened and the list updated separately.

CAS20 assigns separate roles for minting, burning, seizure, pausing and unpausing. These permissions can be assigned to different addresses or held by one address. Network activation authority, token administration and policy-list administration remain separate permissions.

Seizure is disabled for ordinary holders by default. A seizure role alone does not make balances eligible for reassignment because the holder exemption policy protects accounts unless its conditions are met. An authorized operator must also have a sufficient balance, an unpaused seizure function and a valid destination allowed by the seizure-receiver policy.

When those conditions are met, the seizeWithMemo function can reassign eligible balances without the holder’s allowance and without changing total supply. Burning uses a separate role and destroys supply. Transfer restrictions and seizure eligibility use different checks, and pausing ordinary transfers does not pause seizure.

BNB Chain’s CAS20 page is seeking early-access issuers for its Stablecoin and Asset variants. The design places common token functions in native chain logic through stateful precompiles. BNB Chain has warned that a defect in that shared logic could affect multiple CAS20 tokens and require a hard fork to correct.