Summary: Connecting Cardano to Injective via Inter-Blockchain Communication (IBC)
In the 72nd edition of the Developers Office Hour, host Darlisa welcomes Fabian Bormann, Head of Ecosystem Engineering at the Cardano Foundation, to discuss the milestone of connecting Cardano and Injective via the Inter-Blockchain Communication (IBC) protocol. The session highlights a multi-year engineering effort to build a secure, permissionless, and trust-minimized interoperability pathway.
Protocol vs. Bridge: A Paradigm Shift
Fabian Bormann emphasizes a critical conceptual distinction: IBC is not a traditional bridge, but a standardized interoperability protocol, analogous to HTTP for blockchains. Traditional bridges rely on centralized custody or multi-signature gatekeepers—such as Wormhole’s guardian network or Layer Zero’s decentralized validator networks—which pose significant security risks and single points of failure. In contrast, IBC functions as a trust-minimized, permissionless communication layer where any participant can run a relayer to deliver messages, while the security of the transfer is guaranteed cryptographically by the chains themselves.
Under the Hood: Double Light Client Architecture
To enable secure validation without requiring either blockchain to run a resource-heavy full node of the other, the team developed a double light client architecture. This includes a Tendermint light client written in Aiken that runs directly on Cardano to verify Cosmos messages, and a custom probabilistic light client that runs on the Cosmos/Injective side to verify Cardano transactions.
The Probabilistic Challenge and Ouroboros Peras
On Cosmos chains, validators collectively sign off on blocks, providing immediate state proofs. On Cardano, however, blocks are signed individually by the block-producing stake pool operator, meaning there is no native multi-party signature on L1 blocks. To prevent a single malicious operator from submitting fake blocks to the light client, the Cosmos-side client uses a probabilistic approach. It waits and aggregates block signatures over a sliding window until a secure cryptographic threshold of stake is met, validating the state change. Currently, an end-to-end transfer takes approximately 8 to 10 minutes due to this verification window. In the future, the deployment of Ouroboros Peras will allow multiple stake pool operators to sign blocks simultaneously, drastically reducing the transfer time.
Token Standards & Multihop Routing
The integration natively supports the ICS 20 standard for fungible token transfers. When bridging assets, the native token is locked on the source chain, and an equivalent voucher token is minted on the target chain. On Cardano, these bridged assets are represented as CIP-68-compliant tokens, allowing them to be automatically recognized by token metadata registries. Because Injective is connected to the broader Cosmos “Zone” topology, these voucher tokens can transitively hop across multiple independent app chains, such as Osmosis.
Roadmap and Public Goods
Now that the testnet bridge is live, the Cardano Foundation is preparing a bug bounty program to thoroughly stress-test and harden the codebase. The team is actively engaging with DeFi protocols on both networks, such as SundaeSwap v4 and Fluid Tokens. Medium-term milestones include collaborating with Cosmos Labs on the lighter IBC v2 specification, exploring the ICS 712 standard for non-fungible tokens, and investigating the creation of Merkle-tree-based epoch stake commitments. This proposed public good would commit a Merkle root of the entire stake pool operator set on-chain once per epoch, serving as a lightweight anchor of trust for light clients and on-chain voting tools.
Top Five Q&A (FAQ) about Cardano’s IBC Integration
Question 1: Why is IBC considered more secure than a traditional bridge?
Answer: Traditional bridges rely on intermediary operators, multi-signature keys, or third-party guardians to hold assets and verify transfers, creating centralized trust vectors. IBC removes these middlemen entirely. It uses cryptographically secure “light clients” on both blockchains, allowing the networks to directly verify each other’s consensus and state transitions without any trust assumptions.
Question 2: What is the role of “Kuribic” in this infrastructure?
Answer: Developed by the ecosystem engineering team, Kuribic is a specialized orchestration tool. It acts as a CLI that automates and manages all the background components required to run the IBC relayer infrastructure, translating Cardano’s native protocols into the gRPC and HTTP communication standards used by the Cosmos relayer.
Question 3: Why does a transfer from Cardano to Injective currently take 8 to 10 minutes?
Answer: In Cardano, blocks are only signed by the individual stake pool operator that produced them, rather than a collective committee. To prevent a malicious operator from feeding fake blocks to Injective, the Cosmos-side light client must wait and aggregate block signatures over a sliding window until a safe consensus threshold is reached. This security precaution currently takes about 8 to 10 minutes but will be reduced to seconds once Ouroboros Peras introduces multi-signature block finality.
Question 4: How are bridged assets represented on the Cardano blockchain?
Answer: bridged assets are managed as voucher-based tokens. When an asset is moved to Cardano, it is minted using the CIP-68 token standard. This ensures that the token’s metadata is stored securely on-chain in a standardized format, allowing Cardano wallets, explorers, and decentralized applications to natively read and display the asset’s information automatically.
Question 5: What is the proposed “epoch stake commitment” public good?
Answer: It is a proposal to commit a Merkle tree root of Cardano’s entire stake pool operator set and stake distribution on-chain once per epoch. This signed cryptographic root would act as a lightweight, public root of trust. It would allow external systems—like the IBC light client or on-chain survey applications (Tessera)—to verify a user’s voting or staking weight instantly without needing to sync a full Cardano node.
Friday, 07 August
14:00 UTC
Developers Office Hours #72 | AddEvent