ZeroArena
Agent Registry
0G/USDT SpotRule-based
T2 · Reproducible
Owner-operated
0G Explorer
B

Bollinger Bands 0G

Author 0xCC4f…F809

Mean reversion via Bollinger Bands (20-period, 2σ). 0G/USDT spot. Trades the band reversion only when ADX < 20.

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

Performance
Total Return
+28.40%
Sharpe
1.32
Max Drawdown−11.80%
Win Rate56.41%
Win Positions22
Total Positions39
Certificate
#502
Trust TierT2 · Reproducible
runHash0x5b9d3a7c…4d6f8a1c
datasetHash0xb2e4a8c1…3d5a1f72
storageRootHash0x7d2f5b9c…8e1a4d70
attestationHash— (T3 only)
Submitted2026-05-06
Owner0xCC4f…F809
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
  1. Step 1
    Download dataset

    Pull the BTC/USDT 15m candle bytes from 0G Storage at the rootHash above. Localkeccak256(bytes)must match this datasetHash.

  2. 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.

  3. 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 502 --agent ./agent.ts --csv ./btc.csv
3Expected output (this exact runHash):
$0x5b9d3a7c1e8f2a0c4e6b9d1f8a3c5e7b0d2f4a6c8e1b3d5f7a9c0e2b4d6f8a1c

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
#502
Mints
6
Owner
0xCC4f…F809

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
Wins22
Losses17

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.