Chop is a volatility farming protocol launching on Robinhood Chain (EIP-155 chain ID 4663), where users wrap tokens into ‘log’ tokens and farm paired markets to earn $CHOP rewards. Its official website states logs are not yet open, and the $CHOP token contract is deployed at 0x4edb7e299a9c31395ac8f7a4ea01448f4eb65b06 on that chain. Native explorers include Robin Etherscan and Robinhood Chain Blockscout. According to its documentation, fees from wraps, unwraps, and trades fund $CHOP rewards—80% goes to farmers, 20% is burned—with no treasury share or team allocation from fees. The token’s total and max supply are both reported as 1 billion, with allocations split across product/marketing (15%), team (15%, vested), and liquidity pool (70%). Critical questions remain: Is the $CHOP contract verified? Are fee routing and burn mechanisms live and audited? What controls exist over the unlaunched contracts listed in docs—including the fee router, log registry, and staking contracts?
Chop presents a novel volatility farming mechanism—wrapping tokens into ‘log’ tokens, pairing them with assets like $CHOP, and distributing fee-derived rewards—but no evidence confirms a live, functional MVP. The website states ‘Logs open soon’ (chophoods.site), and the contracts page explicitly lists all core components as ‘Not deployed yet’, including the log registry, staking contracts, fee router, and $CHOP token itself (chophoods.site/docs/contracts.html). Though the $CHOP contract address is published (CoinGecko, chophoods.site/docs/chop-token.html), its deployment status is unverified; both chophoods.site/docs/chop-token.html and chophoods.site/docs/contracts.html state ‘$CHOP Not deployed yet’, contradicting any assumption of operational readiness. No on-chain activity, transaction history, or user-facing interface demonstrating wrap/farm/harvest flows is supplied. The fee model and tokenomics are thoroughly documented (chophoods.site, chophoods.site/docs/fees.html), but these remain theoretical without execution evidence. Retention, usability, and failure handling cannot be assessed where no product behavior is observable. The team’s vesting schedule and allocation are disclosed (chophoods.site/docs/chop-token.html), yet delivery capability hinges on unmet deployment milestones. Token supply data (CoinGecko) lacks verification against chain state. With zero evidence of a working core user journey—and the rubric’s hard cap triggering at score 5 for missing MVP—the project remains pre-launch. Confidence is low due to total absence of independent, current, or interactive evidence: all sources are static pages or unverified API claims, none confirm contract deployment, wallet connection, or transaction execution.
Overall score: 4/10 Confidence: Low