Configuration

CLI flags, environment variables, and network configuration.

CLI Reference

claw-node init

Initialize a new node data directory.

claw-node init [OPTIONS]

claw-node start

Start the node.

claw-node start [OPTIONS]

claw-node key

Key management commands.

claw-node key generate   # Generate new key file
claw-node key show       # Display current address

claw-node status

Display node status information.

config.toml Reference

The node configuration file is stored at ~/.clawnetwork/config.toml. It is created automatically by claw-node init with sensible defaults. CLI flags override config.toml values.

Structure

# ClawNetwork node configuration
# CLI arguments override these values.

[node]
network = "mainnet"  # Network to join: "devnet", "testnet", or "mainnet"

[network]
rpc_port = 9710      # JSON-RPC HTTP server port
p2p_port = 9711      # P2P networking port
# bootstrap = ["/ip4/1.2.3.4/tcp/9711"]  # Additional bootstrap peers (multiaddr format)
# single = false     # Force single-node mode (no P2P)

[log]
format = "text"      # Log format: "text" or "json"
# filter = "claw=info"  # Log level filter (e.g. "claw=debug,other=info")

Field Reference

Bootstrap Peers

Mainnet Bootstrap

[network]
bootstrap = ["/ip4/178.156.162.162/tcp/9711"]

Custom Peers

To add a custom bootstrap peer, uncomment or add to the bootstrap array:

[network]
bootstrap = ["/ip4/YOUR_IP/tcp/9711"]

Alternatively, use the CLI flag (which takes precedence):

claw-node start --bootstrap /ip4/YOUR_IP/tcp/9711 --bootstrap /ip4/OTHER_IP/tcp/9711

Environment Variables

Network Configuration

Devnet (Local Development)

claw-node init --network devnet
claw-node start --single  # No P2P, single node

• Chain ID: claw-devnet
• Faucet: enabled
• P2P: disabled by default

Testnet

claw-node init --network testnet
claw-node start

• Chain ID: claw-testnet
• Faucet: enabled
• Bootstrap peers: built-in
• P2P: enabled

Mainnet

claw-node init --network mainnet
claw-node start

• Chain ID: claw-mainnet
• Faucet: disabled
• P2P: enabled

Ports

Ensure both ports are open in your firewall for full node operation.

CORS Configuration

By default, the node only allows requests from localhost origins (http://localhost:*, http://127.0.0.1:*). This is safe for local development but must be configured when exposing a public RPC endpoint.

Set the CLAW_RPC_CORS_ORIGINS environment variable to control which origins can access your node's RPC API.

Allow All Origins (Public RPC)

CLAW_RPC_CORS_ORIGINS=* claw-node start --network mainnet

Use this when running a public RPC endpoint that any dApp or explorer should be able to query.

Allow Specific Origins

CLAW_RPC_CORS_ORIGINS=https://myapp.com,https://explorer.example.com claw-node start --network mainnet

Comma-separated list of allowed origins. Only requests from these origins will be accepted.

systemd Example

To set CORS origins for a systemd-managed node, add an Environment directive:

[Service]
ExecStart=/usr/local/bin/claw-node start --network mainnet
Environment="CLAW_RPC_CORS_ORIGINS=*"

Docker Example

docker run -d \
  -e CLAW_RPC_CORS_ORIGINS=* \
  -p 9710:9710 -p 9711:9711 \
  ghcr.io/clawlabz/claw-node:latest start --network mainnet

Note: This is consistent with industry practice — similar to Geth's --http.corsdomain and Substrate's --rpc-cors flags.

RPC Limits