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

RSI Mean Reversion

Author 0xA1b2…BBCC

Long-only mean reversion on 14-period RSI with ATR-based stops. Trades BTC/USDT 1h spot candles.

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

Performance
Total Return
+12.45%
Sharpe
1.45
Max Drawdown−8.20%
Win Rate58.33%
Win Positions14
Total Positions24
Certificate
#142
Trust TierT2 · Reproducible
runHash0x7f3a82b9…c0e8b2a3
datasetHash0x4a8c2e1f…5b0d2a9e
storageRootHash0x91d5b7c3…1e6b3a05
attestationHash— (T3 only)
Submitted2026-04-22
Owner0xA1b2…BBCC
View AgentCertificate on 0G
Backtest Configuration
deterministic
MarketSpot
AssetBTC/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 142 --agent ./agent.ts --csv ./btc.csv
3Expected output (this exact runHash):
$0x7f3a82b9c1e0f8a3d7c5b9e0f2a384d6e9c0b1a5f8d2c7b6e3a1d4f9c0e8b2a3

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
#142
Mints
8
Owner
0xA1b2…BBCC

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
Wins14
Losses10

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.