A deployment consists of Committee, Operator, Verifier and Watchtower nodes, with Committee nodes optionally acting as Relayers. The node guide describes their roles, and the transaction graph shows their Bitcoin claim and dispute paths.
Run from the repository root:
source ~/.zkm-toolchain/env
cargo build -r -p bitvm-noded --bin bitvm-noded
./target/release/bitvm-noded --help- Select the intended Bitcoin and GOAT networks and deployed bridge contracts.
- Register each participant's identity for its role and fund the required Bitcoin and GOAT accounts.
- Choose the proof service and peer network shared by the participants.
- Give each node isolated persistent state and distinct listening addresses.
- Start the nodes and confirm they are ready before initiating bridge activity.
All participants must agree on the graph parameters, Verifier slot count, and proof programs used for new graphs. Existing finalized graphs retain the values committed when they were created.
Run nodes under a supervisor so interrupted processes restart. Retain their persistent state across restarts. Monitor readiness, chain progress, peers, and failed work with the operator tools.
Keep operational monitoring on a private network. Follow the Proof Builder guide for proof coordination and recovery. Use the localnet to test changes before a live deployment.