> ## Documentation Index
> Fetch the complete documentation index at: https://cts-docs.cosmos.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Interop

> Connect an existing ledger to other DLT networks through IBC.

Interop connects an existing ledger to other DLT networks through
Inter-Blockchain Communication. IBC is a messaging protocol, and Interop is
available standalone without adopting the rest of the Cosmos Tokenization Suite (CTS).

## Who it is for

Interop is for institutions already running their own ledger, whether a private
chain or a platform such as Canton. These institutions need to reach other
networks and counterparties without replacing their existing ledger.

An institution that wants to issue tokenized deposits from scratch should start
with [Issuance](/cts-issuance/overview), which includes interoperability.

## Why IBC

The two chains verify each other directly: no intermediary holds the asset, and
no third party requires review by a risk function.

IBC has processed over 100 billion dollars in cross-ledger transfers across five
years in production, with no protocol-level loss of funds. It is governed under
the Linux Foundation Decentralized Trust rather than by any vendor.

See [Inter-Blockchain Communication](/ibc/overview) for the full explanation,
including [track record and governance](/ibc/overview#track-record-and-governance).

## What the existing ledger must run

CTS's Interop deployment supports an existing ledger running either a
Cosmos stack or an Ethereum Virtual Machine stack. The IBC contracts and the
verification layer deploy onto that ledger, and the institution's contracts and
applications remain its own.

IBC itself is broader: the protocol supports any common smart contracting
platform, including EVM, SVM, Cosmos modules, and WASM. A ledger outside the two supported stacks is scoped individually. Contact
[sales@cosmoslabs.io](mailto:sales@cosmoslabs.io).

## Verification and who runs it

An IBC connection verifies every message on chain before acting on it, through
one of two pluggable models: consensus light clients that verify the counterparty
chain's own consensus, or a first-party attestor oracle signed by the
institution's own hardware security modules. Neither model introduces a
third-party oracle network. See
[Verification Models](/cts-interop/verification-models).

The attestors and relayers are run either by Cosmos as a managed service or by
the bank on premises. The relayer is untrusted in both arrangements.

## Networks

Interop is generic to the underlying technology. Assets are supported across any
EVM network and non-EVM networks reached through network connectors.

| Network          | Notes                                                           |
| ---------------- | --------------------------------------------------------------- |
| Ethereum         | Mainnet                                                         |
| EVM L2s          | Arbitrum, Optimism, Polygon zkEVM, Base, and other EVM networks |
| Avalanche        |                                                                 |
| Solana           | Non-EVM                                                         |
| Ripple           | XRP Ledger and the XRPL EVM sidechain                           |
| Hedera           | Non-EVM                                                         |
| Hyperledger Besu | Private and consortium deployments                              |
| Cosmos chains    | Native IBC, no additional connector required                    |

Consortium networks including Canton, Cari, Agora, and Progmat are supported.
Private chains are also supported, including Kinexys and another institution's
own deployment of CTS. See
[Connecting Networks](/ibc/connecting-networks).

Adding a network does not change the bank's ledger, core integration, or custody
arrangement.

<Card title="IBC documentation" icon="external-link" href="https://docs.cosmos.network/ibc/latest/intro">
  Protocol documentation for IBC, including light clients, connections, channels,
  and application development.
</Card>

<Note>
  This page is a placeholder. The standalone Interop product contents, existing
  ledger requirements, and deployment model still need to be documented.
</Note>

## Related solutions

* [Issuance](/cts-issuance/overview)
* [Settlement](/cts-settlement/overview)