Fooms is an NFT project launched on the Robinhood Chain (EIP-155 chain ID 4663), described as “the first NFT collection minted through a @fomo thesis”. Its official website, fooms.family, outlines a novel minting mechanism: users post a thesis—specifically the word “mint” followed by their wallet address—on the fomo platform while holding at least $10 of the $FOOMS token. A bot then delivers the Foom NFT to that wallet on Robinhood Chain, with no user-side gas fees or interactive mint button. The $FOOMS token contract is verified at 0x7492…4586 and also appears on Robin Etherscan. Governance occurs via thesis-based voting for token holders and NFT-based voting for Foom owners, both executed on fomo. The site reports zero Fooms minted and zero theses pending as of its static snapshot, indicating the minting phase may be inactive or paused. Key evaluation questions include: How is thesis ingestion and NFT delivery guaranteed without on-chain transaction initiation? What prevents front-running or manipulation of the off-chain thesis feed? And how does the Robinhood Chain’s current state—its validator set, finality guarantees, and tooling maturity—affect system reliability?
Fooms presents a novel thesis-driven NFT minting mechanism tied to $FOOMS token holdings and fomo social activity. The website (fooms.family) documents a four-step user journey: connect wallet, hold ≥$10 of $FOOMS, post “mint 0x…” on fomo, then receive an NFT on Robinhood Chain within ~5 minutes—gas-free and automated. Governance is also thesis-based, with two live proposals open for voting by token or NFT holders. However, the site shows zero minted Fooms, zero pending theses, and zero votes—indicating no observable execution of the core flow in the snapshot. No live transaction evidence, wallet confirmations, or explorer links showing transfers are provided. The API snapshot (source_2) reports circulating supply but offers no on-chain verification of mint events or contract interaction. Static copy describes functionality but does not demonstrate it. This absence of verifiable end-to-end execution means the MVP cannot be confirmed as operational. Per rubric hard cap, no verifiable working MVP limits the score to ≤5. Confidence is low due to total lack of observed user activity, reliance on unverified claims, and no independent corroboration across sources.
Overall score: 5/10 Confidence: Low