Launching a log

Any project can have a log for its token. The creator chooses the ERC-20 token used as its pool pair.

What the pool needs#

Wrapping needs only the project's token. The pool needs both the log token and the selected paired token, in equal value.

Setting the starting price#

Self-serve creation at Launch a log opens after deployment review. You choose the wrapped ERC-20 and its paired token; CHOP is the default pair and rewards always remain in CHOP. The current release supports Volatile fees: 1% wrap/unwrap and 0.5% buy/sell. Browser initial seeding is unavailable. Funded launch logs use the team's reviewed atomic creation and seeding flow. The registry owner verifies the log, its fee oracle matures, then the creator or authorized operator publishes it.

The first liquidity added sets the starting price. A new pool is seeded with a small amount first, checked against market prices, then topped up.

Paired assets and rewards#

The paired token is fixed when the log is created. Farmers use that token when adding liquidity. Farmer rewards are paid in $CHOP, regardless of the selected pair. The launch candidate supports CHOP, WETH and USDG pairings. A non-CHOP pair requires a governance-approved V4 route into CHOP. A dedicated keeper converts those proceeds with explicit price limits; supported routes must be reviewed against the actual launch pools and hooks.

Seeded liquidity#

Seeded positions are staked and earn farmer rewards like any other. The lock terms will be confirmed before launch.

To fill before launch: lock length and any seed-grant terms.