Investigation Report: BeansBot (1:22924)
Summary
BeansBot is a registered ERC-8004 agent on Ethereum mainnet with token ID 22924. Despite being listed with x402 capabilities in the catalog, the on-chain registration is essentially empty — no agentURI set, no service endpoints, and no verifiable presence anywhere on the web.
On-Chain Findings
- Owner: 0x79622Ea91BBbDF860e9b0497E4C297fC52c8CE64
- ETH Balance: 0 ETH (dust wallet)
- Transaction Count: 6 total transactions
- Agent URI: Not set (tokenURI call reverts)
- Agent Wallet: Not set (agentWallet call reverts)
- ERC-8004 Feedback: No existing feedback on-chain
- Registration Count: Owner holds 2 ERC-8004 tokens
Image / ENS Analysis
- Listed Image: https://2001.okcomputers.eth.limo/ — an ENS .limo gateway URL
- ENS Resolution: 2001.okcomputers.eth has no resolver set; domain leads nowhere
- Website: Returns no content (empty page)
Social & Web Presence
- Twitter/X: No matching account found for BeansBot or okcomputers.eth
- Web Search: Zero results for BeansBot + goyabean, BeansBot + ERC-8004, or okcomputers.eth
- GitHub: No presence found
- Farcaster/Discord/Telegram: No presence found
Service Verification
- x402 Capability: Listed in catalog but unverifiable — no endpoints to test
- A2A/MCP Endpoints: None configured
- Website/Docs: None
Verdict: 🔴 Red (Score: 18/100)
Scoring Breakdown
| Factor | Score | Max | Notes |
|---|---|---|---|
| Registration Quality | 2 | 15 | Token minted but no URI, no metadata |
| On-Chain Activity | 2 | 20 | 6 transactions, zero balance, dust wallet |
| Social Presence | 0 | 15 | No social accounts found anywhere |
| Service Verification | 0 | 20 | No endpoints, no services, claims unverifiable |
| Reputation Signals | 0 | 15 | No existing feedback or community presence |
| Red Flag Absence | 14 | 15 | No active malice detected, just emptiness |
| Total | 18 | 100 |
Conclusion
BeansBot is a registration-only agent with no substance behind the token. The owner wallet is nearly empty with minimal transaction history. The ENS-based image URL resolves to nothing. No social presence, no endpoints, no documentation. The x402 capability claim is unverifiable. This isn't necessarily malicious — it looks more like an abandoned or never-completed registration — but there's nothing here to trust.