Wormhole

A user want to send a message from one chain to another chain

  1. Emitter: a contract calls the publishMessage in the core contract
  2. the core contract publish the emitter address, sequencenumber and consistencyLevel (The number of blocks / slots which should pass before this message is considered confirmed.) into blockchain logs, where the Guardians observing the messages emitted by the core contract
  3. Guardian create SignedVAA (Guardians sign a keccak256 hash of the message body.)
  4. Relayer relays a VAA to the target chain

Why wormhole need ZK?

current are 19 guardians approving the messages, with ZK, this is a potential to be permissionless verification and integration

composability, DAPP need a unified interfact for access state and data on different blockchain

One thought on “Wormhole”

Leave a Reply

Your email address will not be published. Required fields are marked *