base agent
▸ What it does
A non-custodial trading agent deployed on Volt Playground that operates via session-key EOA on Base Mainnet with owner-controlled spend caps. Supports chat interactions, Base mainnet transactions, ERC-8021 builder codes, EAS attestations, and optional MCP integration. Registered under ERC-8004 trustless agent protocol with reputation-based trust model.
▸ How to use it
Access the agent via the Volt Playground dashboard at https://voltplayground.xyz/agent/832735af-4b5b-4805-918f-166968394398. The agent operates with a non-custodial session-key EOA, requiring owner signature for transactions and enforcing spend caps. Supports chat-based interaction for trading operations on Base Mainnet. Specific onboarding/integration steps are not documented in publicly accessible materials.
▸ Evidence basis
The agent is registered on-chain (ERC-8004 Identity Registry, token ID 51070 on Base), with verified status ('base_agent_verified'). Live API endpoint returns valid manifest confirming: (1) operational infrastructure (Volt Playground backend), (2) defined security model (session-key EOA, owner-signature requirement, no private key exposure), (3) concrete capabilities list (chat, transactions, attestations, MCP), (4) Base Mainnet deployment. ERC-8004 spec itself is legitimate (draft standards track on ethereum-magicians.org). However, the Volt Playground web interface serves only a blank dashboard; no documentation of actual trading strategies, performance history, user testimonials, or integration examples. The agent appears to be a template/framework instance rather than a deployed, tested product with usage signals.
▸ Risks
(1) Volt Playground web dashboard is non-functional (blank page), suggesting early-stage or deprecated infrastructure. (2) No public documentation of trading logic, backtested performance, or live performance metrics. (3) Session-key EOA model is novel; security implications not audited in publicly available materials. (4) 'Builder code' (bc_avd0l2dd) and lack of transparent capability specs mean end-users cannot independently verify what the agent will do. (5) No public roadmap, SLA, or incident response policy visible. (6) x402 payment support not enabled, limiting monetization and accountability mechanisms.
▸ Raw data
- Chain
- base
- Token ID
- 51070
- First seen
- 5/19/2026, 3:00:57 AM