Operators

Operators are service providers who stake assets to run blueprint services. Staking gives customers and developers an enforceable security boundary (exposure + slashing) around off-chain work.

Joining as an Operator

This page covers operator onboarding for Tangle v2. You need to:

1. Register with the staking contract (self-stake).
2. Register for each blueprint you intend to operate.
3. Run the Blueprint Manager to execute jobs.

• Next: Blueprint Manager

Step 1: Install the CLI and prepare a keystore

Install cargo-tangle and create/import an ECDSA key:

• CLI installation
• Key management

Step 2: Register as a staking operator

Use the CLI to stake and register in MultiAssetDelegation (amount is in wei of the configured bond asset):

cargo tangle operator register \
  --http-rpc-url https://... \
  --ws-rpc-url wss://... \
  --keystore-path ./keystore \
  --tangle-contract 0x... \
  --restaking-contract 0x... \
  --status-registry-contract 0x... \
  --amount <STAKE_AMOUNT_WEI>

The CLI flag name is --restaking-contract for compatibility; it refers to the staking contract.

The stake amount must meet the minimum configured for the enabled asset. Contract addresses are listed on Network Parameters.

Step 3: Register for a blueprint

Register your operator in the core protocol for a specific blueprint ID:

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 123 \
  --rpc-endpoint "https://operator.example.com" \
  --registration-inputs ./registration.tlv

• Repeat this step for each blueprint you want to serve.
• --rpc-endpoint is optional and publishes your operator RPC address.
• --registration-inputs is required only if the blueprint expects extra registration payloads.

Step 4: Run the Blueprint Manager

Start the runtime that watches for service activations and executes jobs:

• Blueprint Manager setup