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 minting system on Robinhood Chain (EIP-155:4663), with $HASH token economics tightly coupled to cat mining and burning. The project claims deep technical integration with Uniswap v4 via a custom hook that collects fees and executes ETH-for-$HASH buybacks — a material ecosystem dependency. However, no evidence confirms this hook is deployed, verified, or actively functioning: the supplied explorer URLs show only token and contract pages, not verified source code or transaction history demonstrating hook execution (hashcats.fun, CoinGecko). Similarly, while robinhoodchain.blockscout.com lists the token, it does not verify on-chain rendering logic or PoW difficulty retargeting mechanics described in CoinGecko.
Claim: Uniswap v4 hook enforces automated buybacks and burns. Support: CoinGecko describes the hook’s design but provides no on-chain proof of deployment, verification status, or executed swaps — only stated intent.
Claim: Cats are rendered on-chain without IPFS or servers. Support: hashcats.fun states image, traits, and palette “live in contract storage” and are “drawn by an on-chain renderer”, but static metadata extraction cannot confirm runtime behavior or storage layout.
Announcements and architectural descriptions dominate the evidence; demonstrated integrations remain unverified. The project shows coherent design and self-consistent tokenomics (e.g., circulating supply matches total supply per CoinGecko), but ecosystem partnerships lack independent validation beyond claimed links.
Overall score: 7/10 Confidence: Medium