Tangle CLI Blueprint Commands

CLI source (GitHub): https://github.com/tangle-network/blueprint/tree/v2/cli

This page covers the cargo-tangle CLI surface for creating and operating blueprints on Tangle’s EVM protocol.

Note: the CLI still uses the legacy flag name --restaking-contract. It refers to the staking contract (MultiAssetDelegation).

For the full command surface, use:

cargo tangle --help
cargo tangle blueprint --help

Create a Blueprint

cargo tangle blueprint create --name <blueprint-name>

Generate Registration Inputs (Optional)

If you want to generate registration inputs without sending a transaction (for review or CI):

cargo tangle blueprint preregister \
  --http-rpc-url https://... \
  --ws-rpc-url wss://... \
  --tangle-contract 0x... \
  --restaking-contract 0x... \
  --status-registry-contract 0x... \
  --settings-file ./settings.env

Register as an Operator for a Blueprint

cargo tangle blueprint register \
  --http-rpc-url https://... \
  --ws-rpc-url wss://... \
  --keystore-path ./keystore \
  --tangle-contract 0x... \
  --restaking-contract 0x... \
  --status-registry-contract 0x... \
  --blueprint-id <id> \
  --rpc-endpoint "https://operator.example.com"

Service Lifecycle

The cargo tangle blueprint service namespace mirrors key service lifecycle actions:

service request (request/approve flow)
service approve / service reject
service join / service leave (dynamic services)
service list / service requests

Examples and flags are subject to change; prefer --help output for your installed CLI build:

cargo tangle blueprint service --help
cargo tangle blueprint service request --help

Example (operator approval flow):

cargo tangle blueprint service requests \
  --http-rpc-url "$RPC_URL" \
  --tangle-contract "$TANGLE_CONTRACT"
 
cargo tangle blueprint service approve \
  --http-rpc-url "$RPC_URL" \
  --tangle-contract "$TANGLE_CONTRACT" \
  --restaking-contract "$RESTAKING_CONTRACT" \
  --status-registry-contract "$STATUS_REGISTRY_CONTRACT" \
  --request-id 42

Run the Operator Runtime

Run the blueprint manager/runner against a deployment:

cargo tangle blueprint run \
  --protocol tangle-evm \
  --http-rpc-url https://... \
  --ws-rpc-url wss://... \
  --keystore-path ./keystore \
  --settings-file ./settings.env

For local validation only, you can spawn a single service without on-chain transactions:

cargo tangle blueprint service spawn \
  --http-rpc-url https://... \
  --ws-rpc-url wss://... \
  --tangle-contract 0x... \
  --restaking-contract 0x... \
  --status-registry-contract 0x... \
  --blueprint-id <id> \
  --service-id <id> \
  --dry-run

Jobs (Submit + Watch)

cargo tangle blueprint jobs --help

Next Reading

Quickstart Debugging Blueprints