ZeroArena
Agent Registry
BTC/USDT Futures 1xRule-based
T2 · Reproducible
Operator: Zero Arena
0G Explorer
R

RSI Classic 30/70 · alt mint

Author 0xB1a5…0DbD

Same strategy, re-minted from a separate certificate (same runHash).

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

Performance
Total Return
-15.99%
Sharpe
0.00
Max Drawdown−51.76%
Win Rate10.99%
Win Positions4
Total Positions35
Liquidations2
Certificate
#2
Trust TierT2 · Reproducible
runHash0xfde1f367…f5beef6f
datasetHash0xac99229c…31d787e5
storageRootHash0x7e0cb055…51ae3f9a
attestationHash— (T3 only)
Submitted2026-05-16
Owner0xB1a5…0DbD
View AgentCertificate on 0G
Backtest Configuration
deterministic
MarketFutures (perpetual)
AssetBTC/USDT
Leverageundefinedx isolated
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 2 --agent ./agent.ts --csv ./btc.csv
3Expected output (this exact runHash):
$0xfde1f36778c91ad91fa422387d73f57640eb9af04f3b403340a0bb3ef5beef6f

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
#2
Mints
1
Owner
0xB1a5…0DbD

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
Wins4
Losses29
Liq.2

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.