AI Trading Blueprint
AI Trading lets a user create a trading bot as a Tangle service instance.
The blueprint defines the bot lifecycle, vault contracts, risk policy, metadata, and operator runtime. Operators run the bot sandboxes and APIs. The Arena app is the user surface for creating bots, watching paper/live execution, managing vaults, and inspecting risk state.
Source repo: https://github.com/tangle-network/ai-trading-blueprint
What happens when a user activates a bot
- The user chooses a blueprint mode and creates a service request.
- The selected operator approves the request.
- The operator provisions a bot sandbox and records bot state.
- The bot starts in paper mode by default in the operator install path.
- The Arena reads operator APIs for bot roster, provisions, vault state, logs, and execution history.
- Risk policy decides whether a trade can move from signal to execution.
The chain is the service and settlement spine. The operator API is the live product API.
Modes
| Mode | Blueprint ID in current Base Sepolia notes | Service shape |
|---|---|---|
| Cloud fleet | 13 | One operator process can host many bots. |
| Dedicated instance | 14 | One bot per service instance. |
| TEE instance | 15 | Dedicated bot with confidential runtime selection. |
Do not copy these IDs blindly to another network. Read the deployed manifest or metadata for the target chain.
What the bot controls
| Area | Examples |
|---|---|
| Strategy | Prompt, strategy pack, runtime config, tick cadence, learning state. |
| Venues | Hyperliquid, Uniswap, Aave, GMX, Morpho, Vertex, Polymarket, Aerodrome, and execution helpers. |
| Vault policy | Allowed assets, position size, borrowed-exposure cap, total exposure, drawdown, and stop-loss distance. |
| Trust mode | Per-trade validation, envelope validation, or self-operated mode. |
| Execution state | Paper fills, live fills, open positions, fees, impact, gas, and PnL. |
The same strategy config is meant to drive backtesting, paper trading, and live execution. Treat that as a safety requirement, not a marketing line.
Validation trust
| Trust level | What happens |
|---|---|
PerTrade | Each trade needs validator EIP-712 signatures before execution. Higher latency, stronger external check. |
Envelope | A depositor pre-approves a policy envelope. Trades inside that envelope execute immediately. |
SelfOperated | A trusted/self-hosted operator uses local policy. The envelope still bounds execution. |
On-chain guards live in contracts such as PolicyEngine, TradeValidator, vault contracts, and fee distribution. Operator-side checks are not a substitute for the vault policy.
What to read next
| Page | Use it for |
|---|---|
| Operator Requirements | VPS sizing, install flow, service IDs, ports, env, admission, and upgrade rules. |
| Runtime and Risk | Paper mode, agent keys, runtime backend, risk gates, and validation trust. |
| Dapp Integration | Arena iframe metadata, operator discovery, protocol state, and live operator reads. |
Sources used
This page is grounded in the repo README.md, OPERATORS.md, docs/runbook.md, metadata/blueprint-metadata.json, settings.env.example, Arena operator discovery code, and the trading runtime/risk contract docs.