PLOUTO and Pons V2
PLOUTO does not have its own AMM, its own bonding curve or its own fee switch. It launches on Pons V2, an existing launch protocol on Robinhood Chain, and inherits that system's market structure.
Understanding which parts belong to Pons and which belong to Plouto is the single most useful thing to get straight.
Division of responsibility
- Pons controls
The token contract, the bonding curve, graduation into a Uniswap v4 pool, the fee schedule, when fees are swept, and the escrow that holds them.
- Plouto controls
Which address receives the creator-fee share, when that share is claimed, how it is split, how buybacks are executed and bounded, how staking works, and how the reserve is governed.
Plouto cannot change the Pons fee rate, cannot force a sweep, and cannot alter the token contract. Those are external dependencies, listed as risks in Pons dependency.
What Plouto configures at launch
| Parameter | Value | Why |
|---|---|---|
pairToken | address(0) | Native ETH quote, so revenue arrives as ETH rather than a wrapped asset. |
creatorFeeRecipient | The Revenue Router | This is why the protocol must be deployed before the token exists. |
creatorTaxBps | 0 | Plouto takes its share of the standard Pons fee and adds no extra tax on top. |
buybackEnabled | false | Pons's own buyback vests into a five-year vault rather than retiring supply. |
That last row is deliberate and important enough to have its own page.
The ordering problem
Pons wants a creatorFeeRecipient address at the moment the token is created, and that address has to be a contract that already exists. So the sequence is:
- Deploy
PloutoRegistry,GravityStaking,BuybackExecutor,PloutoReserve,PloutoRevenueRouter. - Hand the Revenue Router address to Pons as the creator-fee recipient.
- Launch PLOUTO.
- Register the resulting token and curve in the Registry — once, permanently.
Between steps 1 and 4 the protocol exists but has no token. The application handles this explicitly rather than pretending: every token action is disabled and the interface states that the launch is pending. See creator-fee recipient.
Fees do not arrive automatically
The most common misunderstanding about this integration: Pons does not push fees. They accrue inside the curve or the pool hook, must be swept into the Pons Fee Escrow, and must then be pulled by the recipient.
That means there are four genuinely different states a fee can be in, and Plouto tracks all four separately. The Pons creator-fee path walks through each one.
Verified addresses
Every Pons address this protocol integrates with was confirmed to have deployed bytecode and cross-checked against the factory's own getters. The list lives in contract addresses, and the checks re-run in the fork test suite and in the launch preparation script.