Cardano Details IBC Light Client Design for Injective

The Cardano Foundation has detailed how Cardano’s IBC connection with Injective verifies cross-chain transfers without relying on a custodial bridge operator. During a Developer Office Hours session, Head of Ecosystem Engineering Fabian Bormann demonstrated the public test environment and outlined the remaining work before a mainnet deployment.

The session expands on the direct IBC route activated between Cardano Preprod and the Injective testnet in early August.

Developers Can Reproduce Cardano and Injective Transfers

The open-source Cardano IBC Incubator repository includes the components needed to run and validate the test route. Its Caribic command-line tool helps developers start the required services, check their status and establish the IBC clients, connection and transfer channel.

The test interface connects a Cardano wallet, such as VESPR, with a Cosmos-compatible wallet such as Keplr. Developers can then move test ADA from Cardano Preprod to the Injective testnet and complete a return transfer.

The current implementation supports ICS-20, the IBC standard for fungible token transfers. When ADA moves to Injective, the original asset is locked on Cardano and a corresponding voucher is issued on the destination network. Returning the asset burns that voucher and releases the original ADA.

The same model allows test $INJ to enter Cardano without a centralized operator holding the transferred assets. Injective implemented Cardano’s light client directly, removing the need for a separate intermediary chain between the two ecosystems.

Two Light Clients Verify Cross-Chain Messages

Bormann distinguished IBC from a conventional bridge. Relayers transport packets between networks, but they do not decide whether a transfer is valid. Each receiving chain verifies the other network through its own light client.

Cardano uses a Tendermint light client written in Aiken to verify state and messages originating from Injective. Injective uses a probabilistic Cardano light client that follows a sequence of Cardano blocks and measures the stake associated with their producers.

A single Cardano block is signed by the stake pool that produced it. The light client therefore waits for additional blocks and accumulates enough stake-backed evidence before treating the original transaction as settled.

Bormann estimated that a complete transfer currently takes approximately eight to ten minutes, including the Cardano settlement window and the IBC messages required to confirm the transfer.

Ouroboros Peras could eventually shorten that process by allowing the light client to collect broader stake pool confirmation more quickly. Peras, however, is not part of Cardano’s current production infrastructure.

Mainnet Path Includes Security and DeFi Testing

The connection remains limited to test environments. Caribic documentation states that Injective mainnet operation has not yet been implemented, while the available workflow connects Cardano Preprod or Preview with the public Injective testnet.

Bormann listed additional ecosystem testing, a possible bug bounty and integrations with DeFi protocols among the next steps. He also said the team has discussed potential use cases with FluidTokens. Further work includes improving how IBC assets and their metadata appear in wallets and blockchain explorers.

Bormann said the project underwent an audit by Anastasia Labs in 2025. The test route still requires operational improvements, including reliable light client updates and recovery procedures after extended interruptions.

Cardano’s IBC implementation has progressed from feasibility research into a reproducible cross-chain testing environment. Developers can now run the direct route, inspect how transfers are verified and move test assets in both directions. Production ADA and INJ will remain outside the system until the security, continuity and application integration work supports a separate mainnet deployment.