omnichain interoperability
Omnichain interoperability is the ambition of a single, unified messaging fabric that connects every chain to every other, so that a developer writes one integration and can reach the whole multi-chain world rather than building a separate bridge per pair. Instead of n-squared point-to-point bridges, you get one protocol that any application can use to send tokens or arbitrary messages anywhere it is deployed. LayerZero is the best-known example; Wormhole, Axelar, Hyperlane, and Chainlink CCIP pursue overlapping visions.
The hard part is doing this securely across chains whose consensus you cannot cheaply verify on-chain. LayerZero's approach separates the roles of verifying a message and delivering it: in its v2 design, configurable Decentralized Verifier Networks (DVNs) attest that a source-chain event occurred, while executors deliver and trigger the message on the destination. An application chooses which DVNs it trusts, so security is configurable rather than fixed — its strength depends entirely on the honesty and independence of the chosen verifiers, and a default or lazy configuration can be weak.
It is important to be honest about what omnichain protocols are: most are externally-verified messaging systems, not trustless light-client bridges. They buy enormous reach and developer convenience — one interface to all chains — at the cost of trusting their verifier set rather than the underlying chains' consensus. The frontier is shrinking that gap, with zk light clients and native verification being folded in as DVN options so applications can dial trust up toward true trust-minimization. Omnichain is a goal and a product category, not yet a synonym for trustless.
Do not read 'omnichain' as 'trustless'. Reaching every chain through one protocol almost always means trusting that protocol's verifier set, which is usually weaker than the consensus of the chains it connects. Reach and trust-minimization are different axes.