BNB Chain has outlined a native-asset design through its Jenner testnet release that divides control over new stablecoins and tokenized assets. The proposed BEP-702 standard introduces the CAS20 token family, while leaving existing BEP-20 tokens unaffected.
The Oct. 16 v1.8.1 release schedules Jenner for BNB Smart Chain’s Chapel testnet on Oct. 29, followed by mainnet guidance later in November. Under the proposal, the architecture separates network admission, token powers, and the holders those powers affect, implementing common token behavior directly into native chain logic.
Governance and Feature Switches
Under BEP-702, chain governance appoints an activation administrator through GovHub, the network's governance forwarding contract. This administrator operates separate feature switches that control when Asset-variant tokens, Stablecoin-variant tokens, and shared policy registries can be created or updated.
Closing a token-creation feature stops the creation of new CAS20 tokens of that variant, but it does not prevent existing tokens from minting units, transferring balances, or administering internal roles. Similarly, a shared policy registry creates a secondary dependency where list updates are gated behind feature activation, though tokens can still consult existing lists even if they cannot be updated.
Issuer Permissions and Seizures
Within individual tokens, administrative roles grant specific powers for functions such as minting, self-burning, seizure, and pausing transfers. Seizures are disabled by default, requiring specific conditions including the failure of a holder exemption rule, an active seizure role, and an unpaused seizure function before balances can be reassigned.
Transfer restrictions and seizure eligibility remain distinct. An account's ability to complete an ordinary transfer does not determine whether it is subject to administrative reassignment, and pausing ordinary transfers does not pause the separate seizure function.
