Every scenario below builds real VAA bytes and verifies them with the same math the Base contract runs — signature recovery (ecrecover), 13-of-19 quorum, registered-emitter, payload codec, and replay checks mirror WormholeOutcomeReceiver.sol check-for-check, in order, and the failing check's actual Solidity error name is shown. Signatures come from the dev guardian set (19 publicly re-derivable keys standing in for Wormhole's guardian network, since this build's Solana leg is simulated) — the verification cryptography itself is real secp256k1. Registered emitter on Base: 0x58512d54…336f60 ↗
Deriving dev guardian keys and signing scenario VAAs in your browser…
A relayer can delay an outcome, but it cannot change one. A proof uploader can submit arbitrary bytes, but the Solana adapter emits only after TxLINE's canonical verifier returns true. Base accepts only a valid Wormhole VAA from the registered emitter. Fixture: 982341.