Running a collator or full-node will allow you to sync and verify the integrity of the interBTC bridge. To get started, follow this guide.
At the end of this document you will have:
- Connected to a network
- Synced a local full-node
- Registered as a collator
?> Please note that there are limited slots for registering as a collator.
The following instructions have been tested on Linux.
Checkout the standard hardware requirements on the Polkadot Wiki.
Create a local directory to store persistent data:
mkdir -p dataSyncing the embedded relay chain can take a number of days. Polkashots hosts database snapshots of Kusama and Polkadot which can be downloaded in minutes. Follow the relevant guide and extract the snapshot to the data directory.
Map the directory into a local volume used by the docker container.
docker run \
--network host \
--volume ${PWD}/data:/data \
interlayhq/interbtc:1.24.0 \
--base-path=/data \
--chain=kintsugi \
--execution=wasm \
--wasm-execution=compiled \
--unsafe-ws-external \
--rpc-methods=unsafe \
--pruning=archive \
-- \
--rpc-cors=all \
--no-telemetry \
--execution=wasm \
--wasm-execution=compiled \
--database=rocksdb \
--pruning=1000docker run \
--network host \
--volume ${PWD}/data:/data \
interlayhq/interbtc:1.24.0-hotfix \
--base-path=/data \
--chain=interlay \
--execution=wasm \
--wasm-execution=compiled \
--unsafe-ws-external \
--rpc-methods=unsafe \
--pruning=archive \
-- \
--rpc-cors=all \
--no-telemetry \
--execution=wasm \
--wasm-execution=compiled \
--database=rocksdb \
--pruning=1000Download the pre-built binary:
wget https://github.com/interlay/interbtc/releases/download/1.24.0/interbtc-parachain
chmod +x interbtc-parachainwget https://github.com/interlay/interbtc/releases/download/1.24.0-hotfix/interbtc-parachain
chmod +x interbtc-parachainBuild the parachain from source, this is necessary if we do not host builds compatible with your architecture.
We typically aim to support the latest version of nightly, check the README for the most up-to-date build instructions.
curl https://sh.rustup.rs -sSf | sh?> This step will take some time depending on your hardware.
Clone the parachain code, checkout the appropriate release and build the node:
git clone git@github.com:interlay/interbtc.git
cd interbtcgit checkout 1.24.0
cargo build --releasegit checkout 1.24.0-hotfix
cargo build --releaseMove the binary into your $PATH and run the parachain full-node:
interbtc-parachain \
--base-path=${PWD}/data \
--chain=kintsugi \
--execution=wasm \
--wasm-execution=compiled \
--unsafe-ws-external \
--rpc-methods=unsafe \
--pruning=archive \
-- \
--rpc-cors=all \
--no-telemetry \
--execution=wasm \
--wasm-execution=compiled \
--database=rocksdb \
--pruning=1000interbtc-parachain \
--base-path=${PWD}/data \
--chain=interlay \
--execution=wasm \
--wasm-execution=compiled \
--unsafe-ws-external \
--rpc-methods=unsafe \
--pruning=archive \
-- \
--rpc-cors=all \
--no-telemetry \
--execution=wasm \
--wasm-execution=compiled \
--database=rocksdb \
--pruning=1000To contribute to the decentralization of the network, users may register their full-node as a collator candidate.
See: Staking
Note the account that you used to stake.
Connect to your local node and use the author_rotateKeys RPC request to create new keys in your node's keystore:
Use the setKeys extrinsic (example) to associate your collator node with the controller account (that you used to stake):
In this example we used the URI //Alice which is a well-known testing account ONLY - do not use this in production. Generate a secure (sr25519) secret seed using a tool such as subkey or polkadot-js instead.
Submit the registerAsCandidate extrinsic (example) with the staked account to start collating:
In most cases, breaking changes to on-chain logic will be handled via the forkless runtime upgrades. However, this will not cover updates to the RPC tooling which will require that you terminate, download and restart your node.


