HASHCATS is an on-chain NFT project launched on the Robinhood Chain (EIP-155 chain ID 4663), where users mine 16,384 pixel-art cats via proof-of-work rather than purchasing them. Its official website, hashcats.fun, describes the cats as fully on-chain: image, traits, and palette are stored and rendered in contract storage—no reliance on IPFS or off-chain servers. The native token $HASH is minted exclusively by burning a cat, with supply decaying across epochs; its economics are governed by a Uniswap v4 pool with a custom hook that collects fees and ETH to buy back and burn $HASH. Contract deployment and network details are publicly verifiable via explorers including Robin Etherscan and Robinhood Chain Blockscout. The project’s Twitter handle @hashcats_rh serves as its primary social channel. Key evaluation questions include: Does the on-chain mining mechanic sustain engagement after token incentives fade? How does the decay schedule for $HASH rewards affect long-term user retention? And what evidence exists of active, self-sustaining demand for mined cats independent of speculative token flows?
HASHCATS positions itself as a fully on-chain, proof-of-work NFT mining system on Robinhood Chain, with $HASH tokens minted exclusively via cat burning and governed by Uniswap v4 hooks that auto-burn ETH to buy back and destroy $HASH. The project’s core thesis—that economic value accrues from verifiable, irreversible PoW effort anchored in on-chain rendering and trait generation—is asserted in the source_2 description but lacks independent verification: no audit reports, on-chain activity metrics (e.g., hash rate, mint frequency), or validator/operator identities are supplied. Governance rights are undefined: no token voting mechanism, multisig details, or upgrade controls are disclosed in the evidence. Incentives map narrowly—miners earn cats, burners earn $HASH, liquidity providers earn fees—but loss-bearing is opaque: the hook’s ETH-buyback logic is described, yet no evidence confirms its execution, slippage enforcement, or fallback behavior under volatility. The team remains anonymous; no repository, documentation, or operational history is provided. While the architecture is conceptually coherent per source_2, the absence of primary-thesis evidence (e.g., live mining logs, verified contract interaction traces, or treasury transparency) prevents validation of claimed mechanics. This gap triggers the rubric’s hard cap: low confidence and no score above 6.
Overall score: 6/10 Confidence: Low