Gc v2

.cargo/config.toml

@@ -0,0 +1,2 @@
+[env]
+ZKM_IMM_WRAP_VK = "1"

.claude/commands/bridge-out.md

@@ -25,11 +25,11 @@ Initiate Bridge Out via the `bridge-out` binary (payInvoice quote -> swap initia
 
 3. Check if the `bridge-out` binary exists at `./bin/bridge-out`. If not, run the install script to download it:
    ```bash
-   .claude/commands/install-bitvm2.sh install
+   .claude/commands/install-bitvm.sh install
    ```
    To upgrade to the latest version:
    ```bash
-   .claude/commands/install-bitvm2.sh upgrade
+   .claude/commands/install-bitvm.sh upgrade
    ```
    The script auto-detects the platform (x86_64-linux / aarch64-macos), downloads from GitHub Releases,
    verifies the sha256 checksum, and installs all binaries to `./bin/`.

.claude/commands/challenge.md

@@ -31,7 +31,7 @@ Use the `/run-challenger-node` skill to start one, or see `deployment/README.md`
 
 5. Check if the `challenge` binary exists at `./bin/challenge`. If not, run:
    ```bash
-   .claude/commands/install-bitvm2.sh install
+   .claude/commands/install-bitvm.sh install
    ```
 
 6. Run the command using the pre-built binary:

.claude/commands/install-bitvm2.sh → .claude/commands/install-bitvm.sh

@@ -1,10 +1,10 @@
 #!/usr/bin/env bash
 set -euo pipefail
 
-REPO="GOATNetwork/bitvm2-node"
+REPO="GOATNetwork/bitvm-node"
 API_URL="https://api.github.com/repos/${REPO}/releases"
 INSTALL_DIR="./bin"
-VERSION_FILE=".bitvm2-version"
+VERSION_FILE=".bitvm-version"
 
 usage() {
     cat <<EOF
@@ -71,7 +71,7 @@ do_install() {
     local platform
     platform="$(detect_platform)"
 
-    local tarball="bitvm2-node-${version}-${platform}.tar.gz"
+    local tarball="bitvm-node-${version}-${platform}.tar.gz"
     local base_url="https://github.com/${REPO}/releases/download/${version}"
     local url="${base_url}/${tarball}"
     local sha_url="${url}.sha256"

.claude/commands/pegin-request.md

@@ -27,11 +27,11 @@ Send a pegin request to GoatChain via the `pegin-request` binary.
 
 3. Check if the `pegin-request` binary exists at `./bin/pegin-request`. If not, run the install script to download it:
    ```bash
-   .claude/commands/install-bitvm2.sh install
+   .claude/commands/install-bitvm.sh install
    ```
    To upgrade to the latest version:
    ```bash
-   .claude/commands/install-bitvm2.sh upgrade
+   .claude/commands/install-bitvm.sh upgrade
    ```
    The script auto-detects the platform (x86_64-linux / aarch64-macos), downloads from GitHub Releases, verifies the sha256 checksum, and installs all binaries to `./bin/`.
 

.claude/commands/pegout.md

@@ -41,7 +41,7 @@ Use the `/run-operator-node` skill to start one, or see `deployment/README.md` (
 
 4. Check if the `pegout` binary exists at `./bin/pegout`. If not, run:
    ```bash
-   .claude/commands/install-bitvm2.sh install
+   .claude/commands/install-bitvm.sh install
    ```
 
 5. Run the command using the pre-built binary:

.claude/commands/rpc-health-monitor.md

@@ -84,12 +84,12 @@ Monitor goat-node RPC health by polling graph or instance status counts, node on
 ```bash
 # testnet4 public RPC
 python3 ./.claude/commands/rpc-health-monitor.py \
-  --base-url https://bitvm2-api-testnet4.goat.network \
+  --base-url https://bitvm3-api-testnet4.goat.network \
   --once
 
 # override proof-builder lag thresholds and chain RPC sources
 python3 ./.claude/commands/rpc-health-monitor.py \
-   --base-url https://bitvm2-api-testnet4.goat.network \
+   --base-url https://bitvm3-api-testnet4.goat.network \
    --header-chain-height-url https://mempool.space/testnet4 \
    --state-chain-rpc-url https://rpc.testnet3.goat.network \
    --header-chain-lag-alert-blocks 30 \

.claude/commands/run-challenger-node.md

@@ -1,4 +1,4 @@
-Run a BitVM2 Challenger node locally.
+Run a BitVM Challenger node locally.
 
 The Challenger verifies operator operations and submits challenges if necessary.
 
@@ -8,11 +8,11 @@ The Challenger verifies operator operations and submits challenges if necessary.
    - **network**: Which network? `testnet4` or `regtest`
    - **rpc_addr**: RPC listen address. Default: `127.0.0.1:8906`
    - **p2p_port**: P2P listen port. Default: `8449` (testnet4) or `8450` (regtest)
-   - **db_path**: SQLite database path. Default: `sqlite:$PWD/bitvm2-node.db`
+   - **db_path**: SQLite database path. Default: `sqlite:$PWD/bitvm-node.db`
 
 2. Ensure the `.env` file exists in the working directory. Template configs are at:
-   - **testnet4**: `deployment/testnet4/bitvm2-nodes/challenge_0/.env.challenge_0`
-   - **regtest**: `deployment/regtest/bitvm2-nodes/challenge_0/.env.challenge_0`
+   - **testnet4**: `deployment/testnet4/bitvm-noded/challenge_0/.env.challenge_0`
+   - **regtest**: `deployment/regtest/bitvm-noded/challenge_0/.env.challenge_0`
 
    The user **must** fill in these required secrets:
    - `BITVM_SECRET` - Node BTC key (hex or `seed:...`)
@@ -21,23 +21,23 @@ The Challenger verifies operator operations and submits challenges if necessary.
 
    Copy the template if needed:
    ```bash
-   cp deployment/<network>/bitvm2-nodes/challenge_0/.env.challenge_0 .env
+   cp deployment/<network>/bitvm-noded/challenge_0/.env.challenge_0 .env
    ```
 
-3. Check if the `bitvm2-noded` binary exists at `./bin/bitvm2-noded`. If not, run:
+3. Check if the `bitvm-noded` binary exists at `./bin/bitvm-noded`. If not, run:
    ```bash
-   .claude/commands/install-bitvm2.sh install
+   .claude/commands/install-bitvm.sh install
    ```
 
 4. Start the challenger node:
 
 ```bash
-./bin/bitvm2-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES"
+./bin/bitvm-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES"
 ```
 
 To run in the background:
 ```bash
-nohup ./bin/bitvm2-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES" >challenger_$(date +'%Y%m%d').log 2>&1 &
+nohup ./bin/bitvm-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES" >challenger_$(date +'%Y%m%d').log 2>&1 &
 ```
 
 5. Verify the node is running:
@@ -49,9 +49,9 @@ Should return `Hello, World!`.
 ### Example (testnet4)
 
 ```bash
-cp deployment/testnet4/bitvm2-nodes/challenge_0/.env.challenge_0 .env
+cp deployment/testnet4/bitvm-noded/challenge_0/.env.challenge_0 .env
 # Edit .env to fill in BITVM_SECRET, GOAT_ADDRESS, PEER_KEY
-./bin/bitvm2-noded --rpc-addr 127.0.0.1:8906 --db-path sqlite:$PWD/bitvm2-node.db --p2p-port 8449 --bootnodes /ip4/34.215.238.232/tcp/8445/p2p/12D3KooWCrPTAmhFdC5DBGgkxZvJi6iuSeiDWKRL87isrt4iMHXv
+./bin/bitvm-noded --rpc-addr 127.0.0.1:8906 --db-path sqlite:$PWD/bitvm-node.db --p2p-port 8449 --bootnodes /ip4/34.215.238.232/tcp/8445/p2p/12D3KooWCrPTAmhFdC5DBGgkxZvJi6iuSeiDWKRL87isrt4iMHXv
 ```
 
 For full deployment documentation, see `deployment/README.md` (section **Challenger**).

.claude/commands/run-operator-node.md

@@ -1,4 +1,4 @@
-Run a BitVM2 Operator node locally.
+Run a BitVM Operator node locally.
 
 The Operator manages bridge operations, kickoff processing, and pegout (Gateway.initWithdraw).
 
@@ -8,11 +8,11 @@ The Operator manages bridge operations, kickoff processing, and pegout (Gateway.
    - **network**: Which network? `testnet4` or `regtest`
    - **rpc_addr**: RPC listen address. Default: `127.0.0.1:8902`
    - **p2p_port**: P2P listen port. Default: `8445` (testnet4) or `8446` (regtest)
-   - **db_path**: SQLite database path. Default: `sqlite:$PWD/bitvm2-node.db`
+   - **db_path**: SQLite database path. Default: `sqlite:$PWD/bitvm-node.db`
 
 2. Ensure the `.env` file exists in the working directory. Template configs are at:
-   - **testnet4**: `deployment/testnet4/bitvm2-nodes/operator_0/.env.operator_0`
-   - **regtest**: `deployment/regtest/bitvm2-nodes/operator_0/.env.operator_0`
+   - **testnet4**: `deployment/testnet4/bitvm-noded/operator_0/.env.operator_0`
+   - **regtest**: `deployment/regtest/bitvm-noded/operator_0/.env.operator_0`
 
    The user **must** fill in these required secrets:
    - `BITVM_SECRET` - Operator BTC private key (hex)
@@ -24,23 +24,23 @@ The Operator manages bridge operations, kickoff processing, and pegout (Gateway.
 
    Copy the template if needed:
    ```bash
-   cp deployment/<network>/bitvm2-nodes/operator_0/.env.operator_0 .env
+   cp deployment/<network>/bitvm-noded/operator_0/.env.operator_0 .env
    ```
 
-3. Check if the `bitvm2-noded` binary exists at `./bin/bitvm2-noded`. If not, run:
+3. Check if the `bitvm-noded` binary exists at `./bin/bitvm-noded`. If not, run:
    ```bash
-   .claude/commands/install-bitvm2.sh install
+   .claude/commands/install-bitvm.sh install
    ```
 
 4. Start the operator node:
 
 ```bash
-./bin/bitvm2-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES"
+./bin/bitvm-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES"
 ```
 
 To run in the background:
 ```bash
-nohup ./bin/bitvm2-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES" >operator_$(date +'%Y%m%d').log 2>&1 &
+nohup ./bin/bitvm-noded --rpc-addr <rpc_addr> --db-path <db_path> --p2p-port <p2p_port> --bootnodes "$BOOTNODES" >operator_$(date +'%Y%m%d').log 2>&1 &
 ```
 
 5. Verify the node is running:
@@ -52,9 +52,9 @@ Should return `Hello, World!`.
 ### Example (testnet4)
 
 ```bash
-cp deployment/testnet4/bitvm2-nodes/operator_0/.env.operator_0 .env
+cp deployment/testnet4/bitvm-noded/operator_0/.env.operator_0 .env
 # Edit .env to fill in BITVM_SECRET, GOAT_ADDRESS, PEER_KEY, GOAT_PRIVATE_KEY
-./bin/bitvm2-noded --rpc-addr 127.0.0.1:8902 --db-path sqlite:$PWD/bitvm2-node.db --p2p-port 8445 --bootnodes /ip4/34.215.238.232/tcp/8445/p2p/12D3KooWCrPTAmhFdC5DBGgkxZvJi6iuSeiDWKRL87isrt4iMHXv
+./bin/bitvm-noded --rpc-addr 127.0.0.1:8902 --db-path sqlite:$PWD/bitvm-node.db --p2p-port 8445 --bootnodes /ip4/34.215.238.232/tcp/8445/p2p/12D3KooWCrPTAmhFdC5DBGgkxZvJi6iuSeiDWKRL87isrt4iMHXv
 ```
 
 For full deployment documentation, see `deployment/README.md` (section **Operator**).

.claude/commands/upgrade.md

@@ -1,19 +1,19 @@
-Upgrade or install bitvm2-node binaries via `install-bitvm2.sh`.
+Upgrade or install bitvm-node binaries via `install-bitvm.sh`.
 
 ## Instructions
 
 1. Check the currently installed version:
    ```bash
-   .claude/commands/install-bitvm2.sh version
+   .claude/commands/install-bitvm.sh version
    ```
 
 2. If $ARGUMENTS contains a target version (e.g. `v0.3.2`), use that version. Otherwise, upgrade to the latest release.
 
 3. Run the upgrade:
    ```bash
-   .claude/commands/install-bitvm2.sh upgrade $ARGUMENTS
+   .claude/commands/install-bitvm.sh upgrade $ARGUMENTS
    ```
 
-4. If the script is missing or not executable, inform the user that `.claude/commands/install-bitvm2.sh` is required and offer to check if it exists.
+4. If the script is missing or not executable, inform the user that `.claude/commands/install-bitvm.sh` is required and offer to check if it exists.
 
 5. Report the result to the user: what version was installed before, what version is installed now, and list the installed binaries.

.env.template

@@ -1,18 +1,18 @@
 RUST_LOG=debug
 
 # required
-ACTOR=Challenger
+ACTOR=Verifier
 
 # required
-GOAT_GATEWAY_CONTRACT_ADDRESS=0xc3c2D73FB80cbc10DD85B6896e639D47ebd21B01
+GOAT_GATEWAY_CONTRACT_ADDRESS=
 
 # required
 GOAT_CHAIN_URL=https://rpc.testnet3.goat.network
 
 # required
 PEER_KEY=
 
-# required, operator and challenger should setup its BTC private key, committee can setup a seed string.
+# required, operator and verifier should setup its BTC private key, committee can setup a seed string.
 BITVM_SECRET=
 
 # optional, for relayer only
@@ -22,7 +22,7 @@ GOAT_PRIVATE_KEY=
 GOAT_ADDRESS=
 
 # protocol name
-PROTO_NAME=bitvm2t3
+PROTO_NAME=bitvmt3
 
 # setup bootnodes, separate multiple nodes by comma ",".
 BOOTNODES=