Sealed RL Bot (v0.2 preview)
Custom reinforcement-learning policy. v0.2 preview running inside 0G Compute Sealed Inference enclave — the engine produced a TEE quote that this certificate carries alongside runHash.
Run signed inside 0G Compute Sealed Inference enclave (v0.2).
- Step 1Download dataset
Pull the BTC/USDT 15m candle bytes from 0G Storage at the rootHash above. Local
keccak256(bytes)must match this datasetHash. - Step 2Re-run with the agent
Owner shares the encrypted agent + AES key. Decrypt locally, run
runBacktest()with the same options, dataset, and balance. - Step 3Match runHash
Recomputed
runHashmust 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.
With the agent module + dataset CSV the owner shares, anyone with Node.js can recompute the on-chain commitment. Copy each step.
npm install zeroarenanpx zeroarena verify 99 --agent ./agent.ts --csv ./btc.csv0x8e2c5b9a1d7f3a0c6e4b8d2f1a3c5e7b9d0f4a6c2e8b1d5f3a7c9e0b6d2f4a8cThe 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.
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-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.