Skip to Content
SupraNova (Bridge)Cross-Chain Message Flow

Cross-Chain Message Flow

Every SupraNova message passes through four stages: post, relay, verify and consume. This holds for Token Bridge transfers and for messages that applications send through Messaging.

The source chain’s consensus determines how a message is proven. The destination chain runs a separate verifier for each source chain it accepts messages from, so the source and destination together determine which verifier checks it. This page follows each stage for each kind of hop.

Supported Networks lists the routes that messages can travel on. Token Transfer Models describes what the Token Bridge does with a transfer on each side: lock, burn, mint or release.

  1. Post. An application calls postMessage on the Hypernova contract on Ethereum, with a payload and the destination chain ID. Hypernova emits a MessagePosted log that records the caller, a message ID, the destination and the payload. The TokenBridge posts this way from sendTokens and sendNative, after it has locked or burned the asset.
  2. Relay. A relayer observes the log. It waits until the Ethereum Sync Committee attests a later block, as the receiving application’s verification strategy requires. See Finality. The relayer then assembles the proof bundle: the Sync Committee signature, an ancestry proof and a receipt proof. See Ethereum Consensus Verification.
  3. Verify. The relayer submits the log and proof bundle to the receiving application’s entry point on SupraMVM, which passes them to hypernova_core. The verifier checks the Sync Committee signature against the committee keys it holds, the ancestry and receipt proofs, the event signature and the address of the emitting contract.
  4. Consume. hypernova_core does not check who posted the message, which chain it is addressed to, or whether it has been processed before. The receiving application checks all three. For a transfer, token_bridge_service checks that the message is addressed to SupraMVM, that the registered Ethereum TokenBridge sent it, and that it has not been processed before. token_bridge_service then mints the wrapped token, or releases the original from the SupraMVM token vault, and pays any configured relayer reward in the same transaction.

Who relays a message

Relaying is permissionless, and the destination chain verifies every submission. SupraNova’s relayers deliver Token Bridge transfers only. Relayers that an application runs or arranges deliver its messages, through the application’s own entry points. See Relay a Message.

  • Architecture — the layers behind these stages
  • Finality — when each message can be relayed
  • Relayers — what a relayer must do, and the Token Bridge’s entry points
Last updated on