> For the complete documentation index, see [llms.txt](https://docs.nomic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nomic.io/nbtc/integrating-nbtc-via-ibc.md). # Integrating nBTC via IBC IBC is a blockchain interoperability protocol used by 110+ chains. This page gives a high-level overview of how to integrate nBTC into any IBC-compatible chain. ## Prerequisites As a prerequisite, follow the instructions to configure an [IBC relayer](/network/ibc-relayer.md) to work with Nomic. IBC transactions require the relayer account to be funded with a small amount of nBTC, as IBC-related transactions are charged a fee of 1 Satoshi each. ## Creating a channel Once `hermes` is [configured for Nomic](/network/ibc-relayer.md), the next step is to create an IBC channel with Nomic. ```bash hermes create channel --a-chain --b-chain nomic-stakenet-3 --a-port transfer --b-port transfer --new-client-connection ``` Nomic currently requires both ends of the channel to use the "transfer" port. ## Relaying operator keys To ensure that nBTC is recoverable by the remote chain's validator set in the event of an Emergency Disbursal, run: ```bash nomic relay-op-keys ``` This command may be re-run anytime to refresh the operator keys of the remote chain's validator set. If an Emergency Disbursal occurs on Nomic, a portion of the Bitcoin reserves equal to the nBTC held in channels backed by the specified client will become spendable by 2/3+ of the voting power of that network's top 30 validators. ## Interchain Deposits Interchain Deposits allow the generation of Bitcoin addresses which commit to an ICS-20 token transfer packet, automatically forwarding any received funds to an address on the counterparty chain. Interchain Deposits require communication with a [Bitcoin relayer](/network/bitcoin-relayer.md). The set of relayers used by your front-end should be selected with care. After a channel has been opened between your chain and Nomic, see [`nomic-bitcoin-js`](https://www.npmjs.com/package/nomic-bitcoin) for information on generating and displaying deposit addresses. ### Withdrawals to Bitcoin nBTC may be withdrawn as Bitcoin directly from the counterparty chain. ICS-20 transfer packets support a `memo` field. Providing a memo of the form "withdraw:\" for an incoming nBTC transfer packet to Nomic will trigger a withdrawal of the Bitcoin to `` at the next checkpoint. `` may be either: 1. A Bech32 Bitcoin address. 2. A hex-encoded Bitcoin script. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nomic.io/nbtc/integrating-nbtc-via-ibc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.