BNB Chain's new Jenner testnet is changing how asset power is distributed on the network. The release splits control across four distinct roles, separating the creation of CAS20 tokens from the powers held by issuers — a move that redraws the lines of who can do what with a token after it's been minted.
The testnet went live with the four-role structure as its central design choice, and it touches everything from token deployment to compliance list management. Here's how the pieces fit together.
What the four roles actually do
The Jenner testnet carves asset authority into four separate functions. CAS20 token creation is one of them, and it no longer sits with the issuer. That split matters because creating a token and controlling it afterward used to be part of the same bundle of permissions.
Admins keep control of the key under the new structure. That's the anchor of the model as described: whatever else shifts between roles, the admin role holds the key. The other roles cover the remaining powers that used to be lumped together, though the testnet release doesn't collapse them into a single authority.
For anyone who has deployed a token on BNB Chain before, the change means a different mental map. The person or contract that creates a CAS20 token isn't automatically the one who can issue it. Those are separate seats at the table now.
Why splitting creation from issuance matters
Separating CAS20 creation from issuer powers is the kind of change that shows up in operational workflows more than in headlines. Teams that assumed one key could handle both jobs will need to think about who holds which role — and whether the same entity should hold more than one.
The testnet release doesn't spell out every consequence, but the structure itself is the signal. Asset control on BNB Chain is being modularized, and the Jenner testnet is where that design gets tested before anything moves further.
Compliance lists still wait on another switch
Shared compliance lists would depend on another network switch, according to the release details. That means the four-role split on Jenner doesn't by itself deliver a shared compliance list capability. It's a separate step, tied to a different network change that hasn't happened yet as part of this testnet release.
For issuers watching the testnet, that's a boundary worth marking. The role separation is here; the shared compliance list piece is still gated behind another switch.
What testnet users should watch
The Jenner testnet is where the four-role structure gets exercised, and the immediate question for developers is how the admin key control interacts with the other three roles in practice. The release describes the roles as distinct, with admins retaining the key, but the testnet period is when teams find out how the separation behaves under real deployment patterns.
There's no announced timeline in the facts for when the shared compliance list switch might arrive, or how the four-role model will be evaluated before any mainnet decision. For now, the Jenner testnet is the place to watch — and the admin key is the piece that stays put while everything else moves around it.
