Proving groundSpicy testnet · live data
Watch it work before you trust it.
Every strategy below runs under published rules. The rules are committed on-chain (a manifest whose hash the registry carries), the account's NAV is attested by signed statements, and every settlement is a transaction anyone can open in the explorer. We run these on testnet with play money until the numbers have been boring for long enough. Then we will say so.
Loading strategies from the chain…
What this proves, and what it does not
- ✓The rules an operator published are the rules the runner enforces: the manifest hash on-chain must match what the runner adopts, or it refuses.
- ✓Settlement arithmetic, expiry, replay protection and authorization are enforced by ArxSettlement, not by us.
- ✓Each settlement records NAV before and after, profit, the share paid, and who paid it, permanently.
- ✕It does not prove the exchange account's balance. For exchange strategies the runner reports its sleeve equity to the oracle; the oracle signs what it is told. The chain cannot see inside Binance.
- ✕It does not prove future returns. Testnet fills come from a sandbox order book; sizes are tiny on purpose.
Verify it yourself
cast call 0x84e10FBcf5229c496d92A75c8762DB28E5245892 "getStrategy(uint256)" 1 --rpc-url https://spicy-rpc.chiliz.com
cast call 0xcaffA466b4D9D62B05CD4cad2519d8e0f0c86808 "latestHash(uint256)(bytes32)" 1 --rpc-url https://spicy-rpc.chiliz.com
cast call 0xd09222FFE0F320D3E70611Ae3aCcca9D59bdD504 "marks(uint256,address)(uint128,uint40,uint40,uint32)" 1 0xB3545D1e5Da990e99d72A67a07030a392b3DEc90 --rpc-url https://spicy-rpc.chiliz.com
curl -s "https://arxkey.com/api/performance?scope=strategies" | jq '.strategies[] | {id,name,manifest:.manifest.hashOk,shares:.performanceShares}'
MCP: arx_strategies returns the same data to agents; arx_nav_statement issues a signed statement for your own account.