BlueprintsAI TradingOperator Requirements

Operator Requirements

Trading operators run one of three binaries and expose an operator API that the Arena discovers from on-chain registration.

Operator Shapes

Blueprint IDBinaryShape
13trading-blueprintCloud fleet; many bots per operator instance.
14trading-instance-blueprintOne bot per service instance.
15trading-tee-instance-blueprintTEE instance; requires TEE hardware.

Host Requirements

ResourceMinimumRecommended
CPU2 vCPU4 vCPU
RAM4 GB8 GB
Disk40 GB SSD80 GB SSD
OSUbuntu 22.04 or 24.04Ubuntu 24.04
Archx86_64x86_64
RuntimeDocker 24+Docker 24+ with sidecar image pre-pulled
NetworkPublic IPv4, inbound 22 and 443Public IPv4, TLS, low-latency RPC

The public sidecar image is multi-GB and bots accumulate state, so disk sizing should include image cache, bot workspaces, logs, and chain metadata.

Required Service Configuration

VariablePurpose
SERVICE_IDExisting service instance. The binary exits if unset.
BLUEPRINT_IDBlueprint variant being served.
CHAIN_IDBase Sepolia is 84532.
HTTP_RPC_URL, WS_RPC_URLChain reads, writes, and event watching.
BLUEPRINT_STATE_DIRPersistent operator state.
OPERATOR_PRIVATE_KEYOperator signer.
VAULT_FACTORY, TRADE_VALIDATOR, POLICY_ENGINE, FEE_DISTRIBUTOR, ASSET_TOKEN_ADDRESSTrading contract addresses.

Ports and Discovery

PortPurpose
9200Operator API default.
9100Trading API default.
443TLS public endpoint used by Arena discovery.

Operators register their public API URL on-chain. The Arena reads that registration and calls the operator API for bot state, pricing, and service-instance controls.