Chop is a volatility-farming protocol on Robinhood Chain (EIP-155:4663), where users wrap tokens into ‘log’ tokens, pair them with assets like $CHOP or USDG, and earn rewards from fees generated by wrapping, unwrapping, and trading. Its official website (choplogs.app) describes the core flow: wrap → farm → harvest, with fee revenue converted to $CHOP, 20% burned and 80% distributed to liquidity providers. The native $CHOP token contract is verified at 0x100765a16f42636bd84ee1e86bc5107b84bcdba3 on Blockscout and Etherscan. Documentation (docs/chop-token, docs/contracts, docs/fees) details fee splits (e.g., 1% for volatile wraps), contract roles (fee router, log registry, Uniswap V4 integrations), and vesting (15% team, 15% product, 70% liquidity). No on-chain circulating supply is reported, and no audit status, source code repository, or historical usage metrics are publicly disclosed. Key evaluation questions remain: Does the protocol retain users after $CHOP rewards diminish? How is log-token price drift arbitrated in practice? What safeguards exist against partner fee manipulation or fee-route centralization?
Chop presents a volatility-farming mechanism where users wrap tokens into ‘log’ tokens, pair them with $CHOP in liquidity pools, and earn rewards funded by wrap/unwrap/trade fees. The fee flow is transparently described: 15% burned as log tokens, remaining value converted to $CHOP, then 20% of that $CHOP burned and 80% distributed to farmers — unless no liquidity is staked, in which case 100% is burned (choplogs.app, choplogs.app/docs/fees). Contracts are live on Robinhood Chain (eip155:4663), with the $CHOP token address consistently reported across choplogs.app, choplogs.app/docs/chop-token, choplogs.app/docs/contracts, and CoinGecko. However, critical gaps undermine verifiability: no audit reports, no source code repository links, no on-chain verification of minting permissions or upgradeability (choplogs.app/docs/chop-token), and no evidence of the claimed Uniswap V4 market or Bankr launch (choplogs.app/docs/chop-token, choplogs.app/docs/contracts). The API snapshot (CoinGecko) reports total supply as ~100B but circulating supply as 0 — a material inconsistency with no explanation. No evidence confirms whether the team’s 15% allocation is locked or if liquidity is secured. These omissions prevent validation of the core thesis — that Chop delivers sustainable, trust-minimized fee-driven rewards — triggering the rubric’s low-confidence cap. Without primary-thesis evidence, score cannot exceed 6.
Overall score: 5/10 Confidence: Low