Glossary
| Term | Definition |
|---|---|
| Ancestry proof | A proof linking the Ethereum block that contains an event to a later block attested by the Sync Committee, through block_roots or historical_summaries. |
| Attestation | The 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. |
BcftQuorum | The Supra committee threshold used to sign Committee Authorization Certificates. |
| Burn-Release | The 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 caching | Storing a verified block’s accumulator root so that later messages from the same block need no further signature check. |
| Chain network | The 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. |
ClanMajority | The 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 Updater | A permissionless off-chain role that keeps each verifier’s record of the source chain’s consensus keys current. |
| Direction | One way across a route, such as Ethereum → SupraMVM. Each direction is verified independently. |
| Epoch tolerance | How many epochs a certifying Supra committee may lag behind the latest known committee before the verifier rejects its certificates. |
| Fast Mode | An option in the SupraNova application that asks SupraNova relayers to process a SupraMVM-originated transfer with priority. Fast Mode does not change the fee. |
| Gloas | An Ethereum upgrade that changes where the receipts root is found. Testnet already uses the Gloas proof format through the _v2 entry points. |
| Global cap | The maximum total amount of an asset a vault will hold. |
| HyperNova | The permissionless bridging protocol behind all current SupraNova routes. It verifies the consensus of the source chain on the destination chain. |
| Hyperloop | A multisig-based bridging protocol planned for chains where HyperNova cannot be used or would add high latency, such as Layer 2 chains. |
| Lock-Mint | The 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 accumulator | The structure to which Supra commits every executed transaction and every event emitted by each transaction. |
| Message-passing layer | The layer that establishes that an event occurred on the source chain. HyperNova implements it. |
| Per-request limit | The minimum and maximum amount of a single lock or release. |
| Receipt proof | A Merkle Patricia Trie proof that an Ethereum transaction succeeded and emitted the message event. |
| Relayer | A permissionless off-chain role that delivers events and their attestations from one chain to another. |
| Relayer reward | The part of the service fee paid to the relayer that delivers a message. |
| Release environment | A SupraNova release: Mainnet or Testnet. A route in the Testnet release may run on Devnet chain networks. |
| Resource account | A 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. |
| Route | A pair of chains that SupraNova connects, such as Ethereum ↔ SupraMVM. |
| Safety level | For the Safe verification strategy, the minimum number of slots between the target block and the attested block. |
| Service fee | The fee that the Token Bridge charges on the source chain. The fee is deducted from the bridged amount and includes the relayer reward. |
| Service layer | The applications, such as the Token Bridge, that send and receive messages through the message-passing layer. |
| Sync Committee | 512 Ethereum validators, sampled from the full validator set, that sign each new block header. The committee rotates every 256 epochs. |
| Token Bridge | The 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 fee | The fee that the verifier on the destination chain charges for each message. It funds Committee Updater rewards. |
| Verification strategy | For messages from Ethereum, how deep in Ethereum’s consensus a block must be before a message is accepted: Finality, Safe or Optimistic. |
| Wrapped token | A 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 limit | The 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