Multichain emissions
Topaz's expansion keeps the existing TOPAZ emission engine on BNB. Spoke LP incentives are funded from a system gauge's share of those emissions, converted into xTOPAZ and delivered to local gauges.
Live multichain system. This guide describes the deployed hub and spoke settlement design. A live network does not imply a nonzero budget in every epoch: gauges receive the amounts actually finalized, delivered and funded. Network availability · Contract addresses.
Follow one week's emissions
| Step | What happens |
|---|---|
| BNB issuance | The existing Minter issues weekly TOPAZ under the existing schedule. |
| System-gauge allocation | The aggregate permanent lock votes for the system pool; the system gauge receives its vote-weighted share. |
| Hub settlement | The coordinator claims that allocation, synchronizes the vault rebase and reads canonical and per-spoke share supply. |
| Budget calculation | Each enabled spoke receives a share budget proportional to its tracked xTOPAZ supply. |
| Backing and mint | All claimed TOPAZ is permanently locked; only the allocated spoke budgets are minted as new xTOPAZ. |
| Delivery | Each budget travels through LayerZero to that spoke's receiver. |
| Local distribution | The local Voter allocates received xTOPAZ to its gauges according to local voting weights. |
The system gauge credits its allocation immediately to its strategy; it is a special accounting gauge, not an ordinary user LP farming pool. Local user gauges stream the rewards they actually receive.
How a chain's budget is calculated
After synchronizing settled rebases, let A be aggregate locked TOPAZ, S canonical xTOPAZ supply, B the TOPAZ received by the strategy, and C the hub adapter's tracked supply for a spoke:
potential budget shares = floor(B × S / A)
spoke budget = floor(potential budget shares × C / S)
new shares minted = sum of enabled spoke budgets
This uses total shares attributed to the spoke, not only shares staked for voting. Liquid user shares and undistributed xTOPAZ already on that spoke are included. Local staking then determines how votes are allocated within that spoke; it does not directly set the chain's share of the hub budget.
The unassigned portion grows backing
The portion corresponding to shares on BNB is locked without matching new shares. That can raise TOPAZ per xTOPAZ for holders on every chain. BNB shares include wallets, pools, the vault's seed and budgets still held by the coordinator before delivery.
Rebases also grow backing without increasing holder balances. Do not count that growth as an extra liquid reward or combine it with an LP Emissions APR without explaining the asset, denominator and period. xTOPAZ explained · Rate Definitions.
Thursday is a boundary, not a delivery guarantee
Epochs turn at Thursday 00:00 UTC. Finalization, messaging and local distribution each need their transactions to execute. A missing delivery, paused receiver or missing local votes can delay gauge funding even after the epoch changes.
If a spoke has no vote weight, its received budget waits in the receiver rather than being sent into a Voter with no allocations. If a week is not finalized, a later finalization can settle accumulated system-gauge rewards using its then-current supply snapshot. Older finalized budgets remain individually sendable; delivery can be partial and is limited by token precision.
For an accurate status, distinguish calculated, sent, received, notified and claimable amounts. A chain budget is not automatically a user's claimable balance, and a quoted rate does not promise next week's return.
One schedule, separate decisions
The expansion does not introduce a new TOPAZ minter on each chain or multiply the original emission schedule by the number of networks. BNB veTOPAZ votes determine the system gauge's allocation alongside other BNB gauges. xTOPAZ supply distribution determines spoke budgets. Staked xTOPAZ votes then choose local gauge allocations.
The Minter schedule and its governance remain documented at TOPAZ & Emissions and Protocol Governance.