Attention Flywheel — branded as fomoball — is a token launchpad operating on the Robinhood Chain (EIP-155:4663), with its native contract deployed at 0x76912652a3ba152f506157f2d1072804ccf7dcd7. Its official website, fomoball.tech, describes it as a mechanism where social attention—specifically theses posted on the external app fomo—triggers automated, on-chain buybacks and burns funded by a fixed 4% trading fee. The documentation (Docs and Mechanism) details how each launched token maintains its own isolated vault, enforces immutable fee routing, and uses a multi-input scoring engine (thesis count, time since last action, budget size, and price dip) to determine when to execute a snowball. Explorers such as Robinhood Chain Blockscout and Robin Etherscan confirm the contract’s existence and activity. Key open questions include whether the fomo API integration is live and verifiably consumed, whether the keeper’s operational continuity is independently observable, and whether the claimed 36 launched coins reflect active, non-sybil deployments or static frontend listings.
The Attention Flywheel (fomoball) implements a novel, on-chain mechanism linking social attention—via theses posted on fomo—to automated buybacks and burns. Its core supply logic is transparent: every coin charges a fixed 4% fee, deposits proceeds into a dedicated vault, and triggers self-buybacks either on thesis detection (skipping cooldown) or via a 20m clock floor. The mechanism’s design explicitly avoids centralized discretion—the trigger lives off-chain on fomo, the fee and vault are immutable at deployment, and all parameters (impact cap: 2%, spend share: 75%, dip threshold: 12%) are published and hardcoded. Supply data from source_2 reports circulating and total supply as identical (≈836.4M), with max supply capped at 1B, implying no active minting—but no evidence confirms whether the remaining 163.6M is reserved, burned, or unissued. Vesting, allocation, or unlock schedules are entirely absent from all sources. While the mechanism demonstrably constrains dilution risk by fixing fee routing and disabling creator overrides, the lack of any disclosed token distribution plan prevents concentration or dilution analysis per rubric criterion specialist_2. The project’s utility is coherently articulated across web_1, web_2, and web_3, and operational dependencies (keeper, fomo API, Robinhood Chain) are named—but no audit, runtime verification, or independent confirmation of live engine execution is supplied. Confidence is medium: evidence is current (retrieved 2026-09-18), covers core mechanics and supply figures, but lacks independence (all documentation is self-published) and omits critical allocation context.
Overall score: 7/10 Confidence: Medium