SWARM ENGINE is a token analysis tool accessible at swarmengine.tech, described as a free, read-only service that maps token holders into ‘real hands’ by clustering wallets linked via shared funders, bundled buys, or transfers. It supports multiple chains—including Robinhood Chain (EIP-155 chain ID 4663), Solana, BNB Chain, Ethereum, and Base—and displays results via interactive bubble maps. Its native token, $SWARM, resides on the Robinhood Chain at contract address 0x72bfcf23b089403a1056fd9719c577966b941f57, with identical explorer links also pointing to robin.etherscan.io. The project’s GitHub repository (moltcagent-rgb/swarm) and Twitter handle (@SWARM_ENGINE) are publicly listed. According to source_2, SWARM employs AI agents and a rules-based ‘Judge’ to generate risk signals (OK/CAUTION/AVOID) and offers priority scanning via a Holder Pass tied to $SWARM holdings. Key evaluation questions include: Does the claimed wallet-clustering logic operate transparently and reproducibly? Is the Robinhood Chain integration independently verifiable beyond self-reported labels? And how is the $SWARM token’s fixed 1B supply validated on-chain?
SWARM ENGINE presents itself as a read-only, multi-chain token analytics tool that clusters wallet holdings into ‘swarms’ to reveal real ownership concentration. Its core thesis—that agents can reliably infer economic control from on-chain funding patterns—is asserted in the source_2 description but lacks verifiable documentation, methodology disclosure, or third-party validation in the supplied evidence. No technical whitepaper, audit report, or operational transparency (e.g., agent logic, clustering thresholds, false-positive rates) is present. The $SWARM token on Robinhood Chain grants a ‘Holder Pass’ with higher scan limits, implying utility—but no treasury, revenue model, or tokenomics beyond fixed supply (1B total) is substantiated.
Incentive-map:
moltcagent-rgb/swarm) → No public identity, track record, or accountability mechanism.Governance is entirely opaque: no decision rights, upgrade procedures, or fallback mechanisms are described. The absence of documentation URLs, API specs, or even functional screenshots—combined with static, identical metadata across all web pages—limits verification. Confidence is low because the primary thesis rests on unverified claims, and no independent source corroborates functionality, accuracy, or operational integrity.
Overall score: 5/10 Confidence: Low