Token Transfer Models
When an asset crosses a SupraNova route, the Token Bridge on each side either takes custody of it or changes its supply. Which action applies depends on where the asset originates, not on the route: every route applies the same models.
Every model preserves the same invariant: the amount of an asset in circulation on the destination chain can never exceed the amount held in custody on its origin chain.
Lock-Mint
An asset leaving its origin chain stays in custody on that chain:
- Lock. The user sends the asset to the Token Bridge on the origin chain. The Token Bridge deposits the asset into the vault and posts a message that records the transfer.
- Verify. A relayer delivers the message to the destination chain, and the destination chain verifies it.
- Mint. The Token Bridge on the destination chain mints the equivalent amount of the wrapped token to the recipient, less any service fee.
For example, bridging 5 ETH from Ethereum to SupraMVM locks 5 ETH, held as WETH, in the Ethereum vault, less the Token Bridge’s share of any service fee, which the Token Bridge keeps. The Token Bridge on SupraMVM mints supETH for the locked amount: the recipient’s share and any relayer reward. supETH remains fully backed by the ETH in the vault.
Guarantees.
- Full collateralization. Wrapped supply is minted only against assets locked in the vault, so it can never exceed the locked amount.
- Proof-driven minting. Nothing is minted until the message has been verified on the destination chain.
Burn-Release
Burn-Release, the exact inverse of Lock-Mint, returns an asset to its origin chain:
- Burn. The user sends the wrapped token to the Token Bridge. The Token Bridge burns the wrapped token and posts a message that records the transfer.
- Verify. A relayer delivers the message to the origin chain, and the origin chain verifies it.
- Release. The Token Bridge on the origin chain releases the equivalent amount of the original asset from the vault to the recipient, less any service fee.
For example, bridging 5 supETH from SupraMVM to Ethereum burns the 5 supETH on SupraMVM, less the Token Bridge’s share of any service fee, which the Token Bridge keeps. The Token Bridge on Ethereum releases the equivalent of the burned amount from the vault. Because Ethereum can deliver ETH in two forms, the user chooses whether to receive native ETH or WETH.
Guarantees.
- No double spending. The wrapped token is destroyed before anything is released, and a burn cannot be reversed.
- Bounded release. A vault can release only what it holds, so releases can never exceed the amount previously locked.
- Proof-driven release. Nothing is released until the burn has been verified on the origin chain.
A burn is final once it is confirmed on the source chain. The release follows on the origin chain once the burn has been verified.
Assets native to SupraMVM
The same two models apply in the opposite direction to assets that originate on SupraMVM, such as SUPRA. SupraMVM is then the origin chain, and its vault holds the collateral:
| Direction | SupraMVM | Destination chain | Model |
|---|---|---|---|
| Leaving SupraMVM | SUPRA is locked in the SupraMVM vault | The SUPRA ERC-20 token is minted | Lock-Mint |
| Returning to SupraMVM | SUPRA is released from the SupraMVM vault | The SUPRA ERC-20 token is burned | Burn-Release |
The SUPRA ERC-20 token in circulation on Ethereum can therefore never exceed the SUPRA locked in the SupraMVM vault. In the same way, supETH on SupraMVM can never exceed the ETH locked in the Ethereum vault.
SupraNova bridges SUPRA between SupraMVM and Ethereum. Between SupraMVM and SupraEVM, SUPRA moves through Supra’s native crossing instead. See Performing Cross-VM Transfers.
Related
- Supported Tokens — the assets on each route and their representation on each side
- Transfer Limits — caps on how much each vault can hold and release