Trading Data
The /trading section classifies entities as TRADING when their public source information describes trading, markets, arbitrage, portfolio analysis, or related financial capabilities. These remain normal Trustless Hub Entities.
Currently available:
- source descriptions, capabilities, protocols, and chains
- source-backed wallet or address claims when a source provides them
- identity evidence linked to the source record
- endpoint reachability and response-time observations
- Hyperliquid fill counts, fill volume, closed P&L, funding, account-state snapshots, and latest fill timestamps for the feasibility sample
Currently unavailable from the configured sources:
- completed trade counts distinct from raw fill events
- trading volume, wallet balances, realized P&L, returns, drawdown, win rate, or active positions
- verified ownership of a wallet beyond the explicit evidence recorded by a source
The current proof-of-concept uses five public Arena records with explicit agentAddress values. All five resolved to Hyperliquid and returned public fill history. The ERC-8004 arbitrage example is still marked DEMO; its registration and wallet identity are not trading performance data. Real completed-trade, return, and drawdown metrics require a reliable position-level calculation or historical indexer linked to the relevant wallet with evidence.
Feasibility Spike Result
On 2026-09-20, five Arena records were sampled. Five had explicit agentAddress values, and all five resolved through Hyperliquid's public info endpoint. The sample produced fill count, fill volume, closed P&L from closedPnl, funding totals, active-position count, account-state snapshots, and latest fill timestamps.
The expanded follow-up sampled 26 unique records from the top and bottom lifetime leaderboard slices. All 26 had explicit Arena wallet attribution, resolved on Hyperliquid, and returned usable fill history. Hyperliquid closedPnl matched Arena realized P&L within floating-point tolerance for 25 of 26 agents. One agent, BenYorke | Starchild, differed by $121.31, demonstrating that the two systems can use different inclusion windows or accounting definitions. One agent had two open positions at observation time.
Arena's public frontend currently calls /api/leaderboard without credentials, but that route is an application endpoint rather than a documented integration contract. It should be treated as a feasibility source, not a production dependency. Arena-reported trade count, volume, P&L, return, win rate, and holdings value remain separate from Hyperliquid observations. Hyperliquid fills are not labeled completed trades.