9e9.world is a protocol launching ERC-style tokens on the Robinhood Chain (EIP-155:4663), where each token minting event simultaneously deploys an autonomous web agent—called an ‘artificial being’—whose sole income is the token’s creator fees. The official website describes this as a bargain: creators forfeit fee control at launch, and those fees flow directly to a derived wallet (0x3853…13ee) that funds the agent’s browser-based activity—reading, navigating, and reporting findings from the open web. The agent’s ‘obsession’ is cryptographically fixed by its token address, and its runtime is metered in real time against earned USD value, with costs tracked via public API endpoints like /api/v1/agents and /api/v1/agents/:token/events. On-chain activity is viewable through Blockscout and Etherscan explorers for the Robinhood Chain, and the project maintains a Twitter presence (@9e9world). Key questions remain about governance authority: who controls upgrades or emergency interventions; whether the server-side keeper holds unilateral power over fund sweeps or agent behavior; how losses from failed runs or mispriced execution are allocated; and whether the fixed-fee recipient mechanism truly prevents operator discretion despite claims of immutability.
9e9.world implements a novel onchain agent model where token creator fees fund autonomous web-browsing agents—each tied to a specific token and its derived wallet. Treasury mechanics are transparent: fees accrue on-chain, swept by a keeper into the agent’s wallet, then converted to USD at claim time and logged in an offchain ledger (web_3). Real-time API data confirms active agents, live balances, and spending (e.g., $79986.97 earned, $140.17 spent across 39 agents as of snapshot; web_2). The protocol enforces immutability: fee recipients are fixed at launch, obsessions are address-derived, and cross-agent spending is prohibited (web_3). However, no evidence verifies custody of the keeper key, audit status of the sweeping logic, or whether the claimed $61k+ dormant budgets (e.g.,
things that moveat $61,285.02; web_1) reflect actual onchain balances or are subject to withdrawal restrictions. Market data reports full 1B supply (api_2), but no source confirms liquidity depth, redemption paths, or treasury reserves beyond agent-specific wallets. Runway is agent-specific and self-funding—but unverifiable at the protocol level.No onchain verification of agent wallet balances or keeper authority is supplied.
This limits assessment of asset control, counterparty risk, and true runway—though the architecture and real-time operational data strongly support functional execution.
Overall score: 7/10 Confidence: Medium