wormhole

Call publishMessage() on the Core Bridge contract with your payload, a nonce, and a consistency level, paying the dynamic messageFee(). Then fetch the signed VAA from the Wormholescan API and submit it to the destination chain's Core Bridge for verification via parseAndVerifyVM.

NTT burns tokens on the source chain and mints canonical tokens on the destination, preserving full decimal precision and requiring token contract ownership. The Token Bridge locks tokens and mints wrapped representations, truncating amounts to 8 decimals, and works with third-party tokens.

Wormhole uses its own chain ID scheme separate from EVM chain IDs. Ethereum is Wormhole ID 2 (not 1), Arbitrum is 23 (not 42161), and Optimism is 24 (not 10). Using EVM chain IDs routes messages to the wrong chain or causes reverts.

With consistencyLevel 15 on Ethereum, Guardians wait for 15 block confirmations before signing, taking roughly 13-15 minutes total. Also verify the transaction succeeded and that you query the correct emitter address, which is the calling contract, not your EOA.

Yes, Wormhole Queries let Guardians execute eth_call on a remote chain and return a signed response without spending gas on the target chain. Supported query types include EthCallQueryRequest, timestamp-based reads, and finality-guaranteed reads.

If shouldQueue is true, the transfer enters a queue and completes automatically when the rate limit window replenishes. If shouldQueue is false, the transfer reverts with RateLimitExceeded. Both inbound and outbound limits are configurable per peer chain.