conceptualv0.1 · skeleton docs
Wormhole transport
What WORMHOOK uses Wormhole for, and what it assumes about it.
What Wormhole provides
- Message passing. The router posts a message through Wormhole Core on Solana.
- Attestation. The guardian network observes the message and signs it. A quorum of 13 of 19 guardian signatures makes a VAA (Verified Action Approval).
- Verification on EVM. The gateway asks the Wormhole Core contract on its chain to verify the VAA's signatures.
WORMHOOK defines what is inside the message (a HookCall, or a HookReceipt on the way back) and what happens when it arrives.
Messages
| Direction | Emitter | Payload |
|---|---|---|
| Solana → EVM | WormHookRouter's emitter | HookCall + payload |
| EVM → Solana | WormHookGateway's emitter on that chain | HookReceipt |
Each side registers the other side's emitter. A VAA from any other emitter is rejected (WH-301).
Identifiers you'll see
VAA ID = <emitter chain>/<emitter address>/<sequence>
example = 1/2420596797…dbbe4672/24214 (chain 1 = Solana)The explorer links each execution to its outbound VAA and, once returned, its receipt VAA.
Delivery
Delivery uses Wormhole's current Executor-compatible pattern: the source transaction requests delivery and pays a quoted fee, and an executor submits the VAA to the destination. WORMHOOK does not use the deprecated legacy relayer contracts. See Executor model.
Finality and consistency
| Leg | Planned consistency | Why |
|---|---|---|
| Solana → EVM | finalized | Adds ~13s, but the call can't be rolled back after the hook has run. |
| EVM → Solana (receipt) | per destination, TBD | Ethereum finality is ~13–15 minutes; L2 settings differ. This is a latency/safety trade-off to settle in phase 2. |