Redeem xTOPAZ

Redemption burns xTOPAZ on BNB and splits its share of the aggregate backing into a new permanent veTOPAZ NFT for the recipient. It does not pay liquid TOPAZ and does not restore the original NFT that was wrapped.

Redemption is enabled on BNB. Redeem xTOPAZ checks the vault state and handles approval followed by automatic redemption simulation from one dapp confirmation. The result is a new permanent veTOPAZ NFT. BNB fork execution is recorded; mainnet redemption through this interface remains unverified. Network availability.

Bring liquid shares to BNB

Shares on a spoke must return through the xTOPAZ bridge. Withdraw any spoke voting position first, respecting its date and vote state. A source bridge confirmation does not make shares available for redemption until the BNB delivery is confirmed.

The contracts also support a composed bridge-back-and-redeem path with a liquid-share fallback. That destination action is outside the initial interface flow.

When redemption is open

Redemption requires the vault's unwrap pause to be off, the aggregate not to be voting, split permission to be available and enough backing to preserve the vault's seed. A settled rebase backlog must be drained before splitting can burn the aggregate's old ID.

The strategy's default system-vote window is Wednesday 18:00–22:00 UTC. Redemption closes when that vote is actually cast. A reset can reopen it after Thursday's first-hour distribution restriction, once the reset transaction executes. The time alone is not sufficient: read the live contract state. Entry via deposit or wrap has its own separate pause.

Review and redeem

  1. Choose how many liquid xTOPAZ shares to redeem on BNB and the recipient of the new NFT.
  2. Review the share-to-TOPAZ estimate, available backing and the permanent-lock result. Settled rebases are synchronized before final contract pricing.
  3. Review the one-time unlimited xTOPAZ approval to the vault, if needed. Confirm once in the dapp and follow the wallet prompts; redemption is simulated automatically after the approval receipt.
  4. Submit the redemption and wait for its receipt. Use the actual share burn, split and recipient custody evidence to identify the new NFT.

The interface supports saved single-hash redemption checks after reload. A historical result links the receipt-created lock; it does not establish its present owner or balance after later transactions.

Managing the resulting lock

The new NFT is a normal permanent veTOPAZ lock on BNB. Its individual BNB voting choices are again controlled by its owner, subject to the normal epoch rules. Claimable local spoke voter rewards remain keyed to their original stake IDs and are not included in redemption.

To eventually withdraw liquid TOPAZ, the owner must turn permanent mode off when permitted, then wait for the ordinary maximum-duration decaying lock to expire. Redemption and bridging do not bypass the underlying lock commitment. veTOPAZ Locks.