Skip to Content

Glossary

TermDefinition
Ancestry proofA proof linking the Ethereum block that contains an event to a later block attested by the Sync Committee, through block_roots or historical_summaries.
AttestationThe evidence a relayer submits with an event so the destination chain can verify it. Under HyperNova, the attestation is a proof of the source chain’s consensus.
BcftQuorumThe Supra committee threshold used to sign Committee Authorization Certificates.
Burn-ReleaseThe model for an asset returning to its origin chain: the Token Bridge burns the wrapped token, and the vault on the origin chain releases the original asset.
Certificate cachingStoring a verified block’s accumulator root so that later messages from the same block need no further signature check.
Chain networkThe blockchain network a route runs on, such as Ethereum Mainnet, Sepolia or SupraEVM Devnet. A chain network is not the same as a release environment.
ClanMajorityThe Supra committee threshold used to sign Transactions Inclusion Certificates.
Committee Authorization Certificate (CAC)A certificate, signed by the current Supra committee, that authorizes the next committee.
Committee UpdaterA permissionless off-chain role that keeps each verifier’s record of the source chain’s consensus keys current.
DirectionOne way across a route, such as Ethereum → SupraMVM. Each direction is verified independently.
Epoch toleranceHow many epochs a certifying Supra committee may lag behind the latest known committee before the verifier rejects its certificates.
Fast ModeAn option in the SupraNova application that asks SupraNova relayers to process a SupraMVM-originated transfer with priority. Fast Mode does not change the fee.
GloasAn Ethereum upgrade that changes where the receipts root is found. Testnet already uses the Gloas proof format through the _v2 entry points.
Global capThe maximum total amount of an asset a vault will hold.
HyperNovaThe permissionless bridging protocol behind all current SupraNova routes. It verifies the consensus of the source chain on the destination chain.
HyperloopA multisig-based bridging protocol planned for chains where HyperNova cannot be used or would add high latency, such as Layer 2 chains.
Lock-MintThe model for an asset leaving its origin chain: the vault on the origin chain locks the asset, and the Token Bridge mints a wrapped token on the destination chain.
Merkle accumulatorThe structure to which Supra commits every executed transaction and every event emitted by each transaction.
Message-passing layerThe layer that establishes that an event occurred on the source chain. HyperNova implements it.
Per-request limitThe minimum and maximum amount of a single lock or release.
Receipt proofA Merkle Patricia Trie proof that an Ethereum transaction succeeded and emitted the message event.
RelayerA permissionless off-chain role that delivers events and their attestations from one chain to another.
Relayer rewardThe part of the service fee paid to the relayer that delivers a message.
Release environmentA SupraNova release: Mainnet or Testnet. A route in the Testnet release may run on Devnet chain networks.
Resource accountA SupraMVM account that a Move module controls. Most SupraNova modules keep their state in it; hypernova_core keeps its light-client state under the package address.
RouteA pair of chains that SupraNova connects, such as Ethereum ↔ SupraMVM.
Safety levelFor the Safe verification strategy, the minimum number of slots between the target block and the attested block.
Service feeThe fee that the Token Bridge charges on the source chain. The fee is deducted from the bridged amount and includes the relayer reward.
Service layerThe applications, such as the Token Bridge, that send and receive messages through the message-passing layer.
Sync Committee512 Ethereum validators, sampled from the full validator set, that sign each new block header. The committee rotates every 256 epochs.
Token BridgeThe service-layer application that transfers assets between chains.
Transactions Inclusion Certificate (TIC)The Supra committee’s ClanMajority signature over a block’s accumulator roots, block height, chain ID and epoch.
Verification feeThe fee that the verifier on the destination chain charges for each message. It funds Committee Updater rewards.
Verification strategyFor messages from Ethereum, how deep in Ethereum’s consensus a block must be before a message is accepted: Finality, Safe or Optimistic.
Wrapped tokenA token that the Token Bridge issues to represent an asset from another chain, such as supETH on SupraMVM or the SUPRA ERC-20 token on Ethereum. The Token Bridge mints it on delivery and burns it when it is sent.
Wrapped-token limitThe minimum and maximum amount of a single send of a wrapped token. It takes the place of the vault’s lock limit, because wrapped tokens are burned when sent. token_bridge_service on SupraMVM and the TokenBridge on SupraEVM Devnet enforce it.
Last updated on