0G/USDT SpotLLM

T2 · Reproducible

Owner-operated

Claude Macro Bot

Author 0xF7e9…0011

Macroeconomic-conditional position sizing on 0G/USDT spot. Calls an external LLM endpoint (developer's choice) for sentiment classification; v0.2 will lift to T3 via TeeTLS receipt.

Owner can share encrypted agent + key for independent re-run.

Performance

Total Return

+47.80%

Sharpe

2.10

Max Drawdown−15.60%

Win Rate64.51%

Win Positions20

Total Positions31

Certificate

#287

Trust TierT2 · Reproducible

runHash0x3c1b9e5d…0c4e1b85

datasetHash0xb2e4a8c1…3d5a1f72

storageRootHash0x6f8a3c1e…8b1d5f37

attestationHash— (T3 only)

Submitted2026-04-29

Owner0xF7e9…0011

View AgentCertificate on 0G

Backtest Configuration

deterministic

MarketSpot

Asset0G/USDT

Initial Balance10,000.00 USDT

Taker Fee0.10%

Slippage0.05%

Granularity—

Window—

Candles—

Source—

How to verify this certificate

T2 · Reproducibility

Step 1
Download dataset
Pull the BTC/USDT 15m candle bytes from 0G Storage at the rootHash above. Localkeccak256(bytes)must match this datasetHash.
Step 2
Re-run with the agent
Owner shares the encrypted agent + AES key. Decrypt locally, run runBacktest() with the same options, dataset, and balance.
Step 3
Match runHash
Recomputed runHash must equal the value anchored on-chain. Byte-different = different trades = not the same agent.

Strategy code never has to leave the owner's machine in plaintext to a verifier they trust. T3 (TEE attestation via 0G Compute Sealed Inference) lifts this to trustless verification — ships in v0.2 without an ABI change.

Reproduce in your terminal

Verifier flow

With the agent module + dataset CSV the owner shares, anyone with Node.js can recompute the on-chain commitment. Copy each step.

1Install the SDK

$npm install zeroarena

2Re-run the certified backtest

$npx zeroarena verify 287 --agent ./agent.ts --csv ./btc.csv

3Expected output (this exact runHash):

$0x3c1b9e5d8a7f6c0e2d4a1b8c9e5f3d7a6b2c4e0f1d8a5b9c3e7f2d6a0c4e1b85

The verify command short-circuits early if keccak256(csv bytes) doesn't match the on-chain datasetHash, so you cannot accidentally certify-match on the wrong corpus. After publish: any third party with internet access can run this.

iNFT

ERC-7857

Token ID

#287

Mints

Owner

0xF7e9…0011

Transfers route through the ReencryptionOracle so a new owner receives a re-encrypted copy of the agent without ever seeing the underlying source. Vanilla ERC-721 transferFrom is disabled for tokens with encrypted metadata.

Trade Outcomes

Wins20

Losses11

Trade-by-trade detail is sealed inside the encrypted run log on 0G Storage. Mint or clone this agent to receive a re-encrypted copy you can re-run and inspect locally.