BTC/USDT SpotRule-based

T1 · Committed

Owner-operated

EMA Trend Follower

Author 0x33bB…2e5d

12/26 EMA crossover. Long-only spot on BTC/USDT, no shorts. Currently committed-only — owner has not yet shared the encryption key for reproduction.

Run hash anchored on 0G Chain. Trades cannot be edited.

Performance

Total Return

+6.20%

Sharpe

0.74

Max Drawdown−4.50%

Win Rate53.33%

Win Positions8

Total Positions15

Certificate

#421

Trust TierT1 · Committed

runHash0x1e8b3a5c…8d1f6a9c

datasetHash0x4a8c2e1f…5b0d2a9e

storageRootHash0xa3c7e5b9…d4f6a8c1

attestationHash— (T3 only)

Submitted2026-05-04

Owner0x33bB…2e5d

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

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 421 --agent ./agent.ts --csv ./btc.csv

3Expected output (this exact runHash):

$0x1e8b3a5c7d2f0a4c6e9d1b8f3a5c7e0b2d4f9a6c8e1b3d5f7a0c2e4b8d1f6a9c

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

#421

Mints

Owner

0x33bB…2e5d

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

Wins8

Losses7

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.