zkBNB
Launch token

Trust model and addresses.

What is enforced on-chain

  • Fee splits, roots payouts, harvests, pool transfers and donation settlement are enforced by the contracts.
  • Holder-reward allocation is computed by the keeper, and only its Merkle root is on-chain. Every snapshot is published and checkable on Rings.
  • Shielded notes hide the spending graph, not the deposit transaction.

Admin powers

The admin is the owner of the contracts. On mainnet that is a Safe account, which is also the treasury listed under Addresses below. Today that Safe has a single owner key (threshold 1 of 1); adding owners and raising the threshold is planned.

The admin can: change fee shares within the bounds, set the treasury, pause a coin's roots and send its new roots share to the fixed recovery address, set the keeper, set pool deposit limits, set the launch and cause-registration fees, set the roots cap, and deactivate a cause. The FeeRouter's rootstock token and buyback contract are set once and cannot be changed afterwards. The admin can change the PancakeSwap route the FlapBuyback uses to turn BNB into ZEC; the route must start at BNB and end at ZEC, and every buyback still has its minimum-out check. It can also re-point some module links that are not locked after deployment: the Launchpad's Roots address, HolderRewards' fee sources and DonationRotator's fee router. A malicious admin could use these to freeze fee collection for Holders and Donate coins or move a Donate coin to another ring; the same goes for the $ZKBNB buyback route and the public buyback cap.

The admin cannot: take roots BNB, change a Creator or Wallet coin's payee after handover, spend or freeze pool notes, mint tokens, change the 2.00% fee, touch a dark vault (DarkPool has no admin; a DarkVault obeys only the owner key derived from the user's shielded key, nobody else), or upgrade contracts. Nothing is upgradeable.

Addresses