How Rhythm works
Four pieces. None can be switched off once set.
Every pons launch mints the full supply into one Uniswap V3 position and hands the NFT to a locker with no withdrawal path. The position is immobile forever — that part is pons' guarantee, and Rhythm builds on it.
The locker lets a coin's deployer choose where creator fees are paid.
Rhythm points them at an immutable receiver: no owner, no upgrade path, no withdrawal
function. Assets can only leave as liquidity or two fixed protocol cuts.
increaseLiquidity is permissionless on Uniswap V3 — a contract can deepen a
position it doesn't own and can never withdraw from. The receiver claims fees, balances both
legs against the position's real tick range, and pushes them in. Anyone can trigger it.
The launcher calls the pons factory, so the launcher is recorded as
deployer — permanently, with no renounce path anywhere in pons. It sets the
redirect exactly once and has no function to change it. Verified live: the creator, a
stranger, and pons' own locker owner all fail to move it.
Where every fee goes
Followed end to end for one trade on a Rhythm coin.
Net: 1% × 70% × 70% ≈ 0.49% of every trade becomes depth nobody can remove. The receiver's own additions earn fees too, which flow back through the same loop — it compounds.
Rhythm vs plain pons
| Plain pons | With Rhythm | |
|---|---|---|
| Locked LP | Permanent, static | Permanent — and it ratchets up with volume |
| Trading fees | To the dev, forever | 70% into the locked position · 30% protocol |
| Dev fee income | ~0.7% of volume | Zero — that's the point |
| Fee redirect | Dev can move it anytime | Nobody can move it, ever |
| What buyers get | A promise | A commitment verifiable in two eth_calls |
Why a dev would do this
On a normal launch, "I'm putting fees into liquidity" is a promise — and the dev keeps the power to break it, because pons has no renounce path. Launch through Rhythm and it stops being a promise: a buyer runs two calls and sees the redirect cannot move. The benefit to the dev is precisely that they gave up an option. That's what makes the signal cost something, and therefore worth something.
The honest version
deployer and can unwire it at any time.
Those coins are labelled REVOCABLE everywhere on this site. Only a coin launched through the
Rhythm launcher is permanent.Protocol addresses
Where the 30% goes, read live from the launcher — the split and both destinations are immutable, baked in at deployment.
Reading the chain…
Verify it yourself
No claim on this site requires trusting us. For any token:
cast call $LOCKER "getLaunchedToken(address)" $TOKEN → read .deployer
# 2 — where do fees go right now?
cast call $LOCKER "feeRedirects(address)(address)" $TOKEN
If .deployer is the Rhythm launcher and the redirect is the coin's receiver, the binding is permanent — the launcher has no function that can call setFeeRedirect again. If .deployer is a wallet, it can be undone tomorrow.
Lockers: active 0x736D…7F35 · legacy 0x31ca…54B5 ·
launcher 0x7752…7134. Full source and fork tests are in the repo.