Contracts

What each contract does#

• Log registry. The list of logs, and which ones are verified to show in the app.
• Log contracts. One per log. Each holds its wrapped token, issues the log token and charges fees.
• Staking and rewards. Each log has a staking contract for farmed liquidity and a rewards contract that pays farmers.
• Fee router. Converts each log's remaining fee value into $CHOP for burning and farmer rewards.
• Rewards whitelist. Controls which reward tokens can be paid and whether a token's payouts are paused.
• Price helper. Supplies the time-weighted prices used when fee value is swapped for $CHOP.
• Helper. Lets the app farm and stop farming in a single transaction. It's optional; the log contracts work without it.
• $CHOP. The token farmer rewards are paid in.
• USDG. A pricing asset used to express comparable dollar values in the interface. The launch candidate supports CHOP, WETH and USDG pairings.
• Uniswap V4 Pool manager, router and keeper. The V4 pool manager is the shared settlement contract for Uniswap V4 pools; the router and keeper support V4 reward routes. Uniswap V4 has no separate factory; the pool manager fills that role.

Source code#

Chop's contracts build on earlier open-source work. Individual contract files record their license notices; the repository's NOTICE file and upstream provenance document describe that source.

Source: Chop contracts. The repository records its Peapods source provenance and individual license notices. The hardened source is on release/v1; the newer work/robinhood-eoa-handoff candidate includes audit follow-up fixes. Final source and production addresses will be recorded after deployment. Historical audits do not attest the amended candidate.