Cross-chain messaging protocol

Token bridges move value; messaging protocols move information, and token transfers become one use case among many. A contract on the source chain emits a message, an off-chain network observes it and attests to it, and a contract on the destination verifies that attestation and executes the instruction. Governance votes, oracle updates, cross-chain lending positions and omnichain tokens all run on this plumbing.

The main differences between protocols lie in who attests. LayerZero lets each application choose its set of verifier networks, Wormhole relies on a fixed set of guardian nodes, Axelar on its own proof-of-stake chain, Chainlink CCIP on oracle networks with an extra risk layer, and IBC on light clients. Hyperlane lets apps define their own security modules.

The verification layer is a single point of failure for every app that trusts it, and some of the largest hacks in crypto history hit bridges built on messaging protocols. Configuration matters as much as the protocol: an app that uses a weak verifier setup can be exploited even if the protocol itself is sound.