Skip to Content

Finality

Finality determines how soon a transfer or message sent on the source chain can be relayed and accepted on the destination chain. Finality depends on the source chain, so the same rules apply to Token Bridge transfers and to Messaging.

Source chainWhen a message becomes verifiableAdditional wait
EthereumDepends on the verification strategy chosen by the receiving applicationYes, set by the strategy
SupraMVM / SupraEVMAs soon as the Supra validator committee certifies the blockNone

Messages from Ethereum: verification strategies

Ethereum blocks are not final when they are produced. Casper the Friendly Finality Gadget (Casper FFG), Ethereum’s finality mechanism, finalizes them later. The receiving side therefore chooses how deep in Ethereum’s consensus a block must be before it accepts a message from that block. hypernova_core on SupraMVM supports three verification strategies:

StrategyA message is accepted when
FinalityCasper FFG finalizes the target block.
SafeAn attested block at least n slots after the target block carries enough Sync Committee signatures.
OptimisticAn attested block after the target block carries enough Sync Committee signatures.

Each strategy accepts a message at a later point than the one before it:

The strategies trade latency for the depth of Ethereum consensus that a block has reached. Finality waits longest and gives the strongest guarantee. Safe and Optimistic accept a block before Casper FFG finality.

In every strategy, the attestation must carry the required number of Sync Committee signatures. See Ethereum Consensus Verification.

hypernova_core does not hold a strategy of its own. Each receiving application passes the strategy, and for Safe the slot distance n, when it asks hypernova_core to verify a message. Applications that receive messages from Ethereum choose their own strategy. See Receive a Message.

Token Bridge setting

The Token Bridge on SupraMVM stores its strategy in token_bridge_service and applies it to every transfer from Ethereum. Mainnet and Testnet currently use the Safe strategy with n = 15 slots, about three minutes after the target block. On Mainnet, the attestation must also carry at least 400 of the 512 Sync Committee signatures.

Read the current setting with get_verification_method_and_safety_level on token_bridge_service. The admin can switch the Token Bridge to another strategy, or change the slot distance, with update_verification_strategy_type. For the Safe strategy, the slot distance cannot be set below 2. See Roles and Permissions.

A relayer cannot change the Token Bridge’s strategy. Both entry points apply the stored strategy: execute_optimistic_or_safe aborts when the Token Bridge is set to Finality, and execute_finality aborts unless it is. See Relayers.

Messages from SupraMVM and SupraEVM

SupraMVM and SupraEVM share Supra’s consensus, and a Supra block is final once the validator committee certifies it. A message from either chain can be relayed as soon as the certificate for its block is available, with no additional waiting period. This applies to SupraMVM → Ethereum, SupraMVM → SupraEVM and SupraEVM → SupraMVM. See Supra Consensus Verification.

Effect on transfer time

A transfer takes the finality wait on the source chain, plus the time for a relayer to deliver it, plus the confirmation of the delivery transaction on the destination chain. The SupraNova application shows an Estimated Time before you confirm a transfer. To follow one in progress, see Track a Transfer.

Last updated on