Architecture
SupraNova separates a cross-chain transfer into two on-chain layers, connected by off-chain actors. The message-passing layer establishes that an event occurred on the source chain. The service layer decides what that event means and acts on it. Because the two layers are independent, bridging protocols and the applications built on them can evolve separately.
Message-passing layer
The message-passing layer carries messages between chains. On the source chain, it emits an event for each outbound message. On the destination chain, it verifies the attestation submitted with that event.
If the attestation is valid, the layer returns the verified message to the application that requested it. The message holds the caller on the source chain, a message identifier, the destination chain and an opaque payload.
A verified message must be accepted only once. For messages from Supra, the verifier keeps the record of processed messages. For messages from Ethereum, the receiving application must keep it. See Security Model. The layer holds no funds and does not interpret payloads.
HyperNova implements this layer. On each destination chain, it runs a verifier for the consensus of every source chain it accepts messages from:
- An Ethereum light client on SupraMVM (
hypernova_core), for messages from Ethereum. - A Supra committee verifier on Ethereum and on SupraEVM (
Hypernova), for messages from SupraMVM. - A Supra committee verifier on SupraMVM (
supra_hypernova_core), for messages from SupraEVM.
Verification explains how each verifier works.
Service layer
The service layer consists of applications that send and receive messages through the message-passing layer. Each application defines its own payload format and business logic, and holds any assets involved. Service contracts never verify cross-chain proofs themselves. They hand every inbound message to the message-passing layer, and act on it only after that layer has verified it.
| Application | Role |
|---|---|
| Token Bridge | Transfers assets between chains. It locks, burns, mints and releases tokens, enforces transfer limits, prices each transfer through its fee operator, and holds the service fees it collects. |
| iAssets | Receives deposit events from Ethereum in the iAssets (PoEL) modules on SupraMVM. |
| Your application | Sends and receives its own messages. See Messaging Overview. |
Off-chain actors
Under HyperNova, two permissionless roles connect the chains. Neither role is trusted: the destination chain verifies everything they submit.
- Relayer. Observes outbound events on the source chain, assembles the attestation, and submits both to the destination chain. See Relayers.
- Committee Updater. Keeps the destination chain’s record of the source chain’s consensus keys current as validator committees rotate. See Committee Updaters.
Layers in each direction
| Direction | Verification method | Message-passing layer (verifier) | Service layer (Token Bridge) |
|---|---|---|---|
| Ethereum → SupraMVM | Ethereum consensus | hypernova_core on SupraMVM | token_bridge_service on SupraMVM |
| SupraMVM → EVM chain (Ethereum, SupraEVM) | Supra consensus | Hypernova on the EVM chain | TokenBridge on the EVM chain |
| SupraEVM → SupraMVM | Supra consensus | supra_hypernova_core on SupraMVM | token_bridge_service on SupraMVM |
Extending SupraNova
The separation of layers determines what each kind of extension involves:
- A new application is deployed on the service layer and uses the existing message-passing layer, without any change to how messages are verified. See Messaging Overview.
- A new chain requires a verifier for that chain’s consensus, or for the attestations of the protocol chosen for it. It also requires deployments of the service-layer applications that operate on the new route.