Fudarake (ticker: $FUDA) is a virtual trading card shop built on the Robinhood Chain (EIP-155 chain ID 4663), as stated on its official website and corroborated by two independent API sources. Its native token contract is deployed at 0x268aea4a2c22a879d591e0feddc50a7539f287b7, viewable on the Robinhood Chain Blockscout explorer. The project describes itself as culturally inspired by Japanese aesthetics and Akihabara, aiming to build a community treasury through card sales and evolve into a long-term brand—not just a speculative token—per a source-reported description. Social presence includes Telegram (t.me/Fudarake_com) and X (x.com/Fudarake). Notably, the website provides only metadata-level content (title and brief description), with no functional shop interface or product documentation visible in the static snapshot. The token’s circulating supply is reported as zero, while total and max supply are both 1 billion $FUDA. Key evaluation questions remain: Has any card shop functionality shipped? Is the treasury mechanism operational or merely conceptual? Who comprises the team, and what prior delivery evidence exists? How is the Robinhood Chain’s security and decentralization validated?
Fudarake claims to be a TCG card shop on Robinhood Chain, with stated goals of community treasury building and ecosystem growth. However, no on-chain activity is verifiable: the token contract on Robinhood Chain (via Blockscout) shows zero circulating supply (source_2), and no transaction volume, transfers, or holder data appear in the supplied evidence. The website contains only static metadata—no shop interface, card listings, or functional dApp links (fudarake.com). Social channels (Twitter, Telegram, X) are referenced but not audited; no follower counts, message volume, or engagement metrics are provided. There is no documentation, repository, or audit evidence. The project’s core thesis—that it functions as an active virtual card shop—is unsupported by any measurement of usage, economic throughput, or user interaction. Supply data is self-reported and stale (last updated 2026-09-10), and no treasury, fee collection, or revenue mechanism is evidenced. Without verified activity windows, unique user signals, or distinguishable organic usage, specialist criteria 1–3 cannot be satisfied. Complementary areas—product usability, team traction, token financials, and technical controls—are all unverifiable due to missing documentation, code, or operational artifacts.
Overall score: 4/10 Confidence: Low