IBC versus other interoperability solutions
IBC is a mature, battle-tested protocol that facilitates tens of billions of dollars in annual transfer value across chains. With a rich feature set for cross-chain interactions, a robust approach to security, no fees or in-protocol rent extraction, and a developer-first approach, IBC is a platform for flexible and scalable interoperability.
This overview explains the differences between IBC and example interoperability solutions.
Compare Blockchain Interoperability Solutions at a Glance
IBC | External validator bridges | Fee-based interoperability networks |
|---|
| Network reach | Connect any ledger or network that implements the IBC specification. Extend support as your needs grow, with implementations in Solidity, Go, and Rust. | Limited to chains integrated with the bridge’s verification network. Adding chains may require approval. | Depends on supported deployments and verification services. CCIP maintains supported routes; LayerZero requires suitable verifier support. |
| Institutional and non-ledger systems | Connect public, private, and consortium ledgers, including Hyperledger Besu and more. Integrate non-ledger systems through purpose-built clients and adapters. | Institutional connectivity depends on vendor support. | Institutional connectivity depends on vendor support. |
| Infrastructure control | Run your own infrastructure without a required third-party interoperability operator. | Third-party infrastructure and operators may be required. | Third-party infrastructure and operators may be required. |
| Security | Choose the security model that suits your needs: consensus light clients for direct verification, permissioned attestors for an agreed trust model, or custom clients built for your use case. | Trust relies on an additional verification network. | Trust relies on configured verification services. For example, LayerZero’s verifier networks or CCIP’s Chainlink committee and any additional verifiers. |
| Open source and portability | An open, neutral interoperability standard with public specifications and open-source implementations. Inspect, adapt, and build on the standard without permission from a central protocol operator. | Licensing varies. Open-source code does not remove the deployed networks’ verification dependencies. | Licensing varies. For example, portions of CCIP use Business Source License 1.1. |
| Cost | No required IBC token or in-protocol fees. Anyone can adopt and use the standard. | Service and transaction fees may apply. | Service and transaction fees may apply. LayerZero verification and execution services or CCIP may charge fees. |
| Customization | Customize across any layer: Build your own applications or light clients, and compose cross-ledger applications as your needs evolve. | Customization options vary. Verification remains tied to the bridge network. | Customize through platform-defined interfaces. Available options vary. |
External validator bridges | Fee-based interoperability networks |
|---|
| Network reach | Connect any ledger or network that implements the IBC specification. Extend support as your needs grow, with implementations in Solidity, Go, and Rust. | Limited to chains integrated with the bridge’s verification network. Adding chains may require approval. | Depends on supported deployments and verification services. CCIP maintains supported routes; LayerZero requires suitable verifier support. |
| Institutional and non-ledger systems | Connect public, private, and consortium ledgers, including Hyperledger Besu and more. Integrate non-ledger systems through purpose-built clients and adapters. | Institutional connectivity depends on vendor support. | Institutional connectivity depends on vendor support. |
| Infrastructure control | Run your own infrastructure without a required third-party interoperability operator. | Third-party infrastructure and operators may be required. | Third-party infrastructure and operators may be required. |
| Security | Choose the security model that suits your needs: consensus light clients for direct verification, permissioned attestors for an agreed trust model, or custom clients built for your use case. | Trust relies on an additional verification network. | Trust relies on configured verification services. For example, LayerZero’s verifier networks or CCIP’s Chainlink committee and any additional verifiers. |
| Open source and portability | An open, neutral interoperability standard with public specifications and open-source implementations. Inspect, adapt, and build on the standard without permission from a central protocol operator. | Licensing varies. Open-source code does not remove the deployed networks’ verification dependencies. | Licensing varies. For example, portions of CCIP use Business Source License 1.1. |
| Cost | No required IBC token or in-protocol fees. Anyone can adopt and use the standard. | Service and transaction fees may apply. | Service and transaction fees may apply. LayerZero verification and execution services or CCIP may charge fees. |
| Customization | Customize across any layer: Build your own applications or light clients, and compose cross-ledger applications as your needs evolve. | Customization options vary. Verification remains tied to the bridge network. | Customize through platform-defined interfaces. Available options vary. |
Join Leading Blockchain Companies Building with IBC
Testimonials
Crypto.com
Integrating the IBC solo machine client has been a game-changer for us. It effortlessly allowed us to mint pegged DOT and various other tokens, all without the hassle of setting up an entire blockchain.
Datachain
We have long believed that IBC will become the de facto standard for blockchain interoperability. This conviction has driven us to contribute to IBC, particularly by extending its availability to non-Cosmos blockchains, including EVMs and enterprises. Ibc-solidity is one such implementation we kickstarted. We view IBC as an indispensable technology. It is the foundation for our trust-minimized cross-chain bridge.
