Cross-chain integration | RP1 Documentation

Integrate IBC, InstaWrap, light clients, proof relayers, and threshold-controlled withdrawals.

Cross-chain integration is a family of explicit adapters, not one universal bridge API.

IBC

Use IBC/ICS-20 for Cosmos-connected assets when a configured channel and counterparty are healthy. Discover the channel, port, denom trace, timeout, and acknowledgement before building a transfer UI. A packet relay or source-chain transaction can remain pending after the user has signed.

InstaWrap

For supported EVM, Bitcoin, and Solana flows, use the InstaWrap queries and messages for vault addresses, supported chains/assets, deposits, instant-credit state, withdrawals, and proof/relayer status. Keep source transaction confirmations separate from RP1 credit and final withdrawal state.

Relayer boundary

The relayer observes origin-chain events, builds or transports proofs, submits RP1 transactions, and may collect threshold signatures. It does not replace chain-side proof verification. A service should expose relayer health and retry state without treating “relayer accepted” as “asset settled.”

Recovery checklist

Persist source transaction hash, RP1 transaction hash, recipient, amount, denom, and connector.
Re-query by identity after reconnecting.
Surface pending, confirmed, completed, and failed separately.
Require exact destination and amount matching before crediting a user ledger.
Define an operator path for proof rejection, stale light-client state, and timeout.

Read cross-chain settlement, InstaWrap, and light clients.