Documentation
Read the machinery.
How fee-driven contraction works, what the contracts actually enforce, and how to take part.
This documents a protocol that is not yet deployed. Status labels throughout are literal — where something is described as unverified, unaudited or not deployed, that is the current state.
- Sections
- 10
- Pages
- 72
- Search
- ⌘K
Introduction
What Plouto is, why it works this way, and what is actually deployed today.
- 01What is Plouto?A fee-driven staking and supply-contraction protocol on Robinhood Chain.
- 02Why fee-driven contraction?Why rewards are funded by real revenue instead of token emissions.
- 03PLOUTO and Pons V2How the token launches, where fees originate, and what Plouto controls.
- 04Robinhood ChainNetwork parameters, RPC, explorer and how to connect.
- 05Current deployment statusWhat is deployed, what is not, and how the app reflects that.
- 06Build statusTest results, static analysis and what has actually been verified.
Core concepts
The vocabulary the rest of the documentation assumes.
- 01Revenue epochsWhat a single claim-and-route cycle is, and what it is not.
- 02The CoreThe immutable 60 / 30 / 10 split and the contract that enforces it.
- 03GravityLock-weighted stake, and exactly how a reward share is computed.
- 04Dual contractionThe two independent ways PLOUTO leaves circulation.
- 05Permanent retirementBurn versus dead address, and why Plouto reports them separately.
- 06The Plouto ReserveWhat the reserve is for and how it is governed.
Economics
Where the money comes from, where it goes, and what can go wrong.
- 01Revenue sourceThe only thing that funds Plouto: trading activity.
- 02The Pons creator-fee pathAccrual, sweep, escrow and claim — four distinct states.
- 0360 / 30 / 10 routingThe split, the dust rule, and why no admin can change it.
- 04Staker reward mathematicsThe accumulator, reward debt, and worked examples.
- 05Lock multipliersWhy 1×, 1.5× and 2.5×, and what they do to your share.
- 06Supply accountingTotal, retired, circulating, staked and liquid — defined precisely.
- 07No-emissions policyWhy no PLOUTO is ever minted as a reward.
- 08Empty-volume behaviourWhat the protocol does when nobody is trading.
- 09Risks and limitationsThe honest list, including what Plouto cannot control.
Participant guides
Step-by-step, from connecting a wallet to verifying a retirement yourself.
- 01Connect a walletAdding Robinhood Chain and connecting safely.
- 02Stake PLOUTOApprove, choose a lock, confirm, and read the receipt.
- 03Choose a lockHow to think about term length without a promised yield.
- 04Claim ETHTaking rewards without unlocking principal.
- 05Withdraw a matured positionWhat maturity means and what you receive.
- 06Verify a retirementCheck a buyback yourself on Blockscout, without trusting this site.
- 07Read protocol receiptsWhat each figure on the Core page means, precisely.
Pons V2 integration
The external system Plouto depends on, and exactly how it is used.
- 01Launch lifecycleThe four phases a Pons launch moves through.
- 02Curve phasePre-graduation trading and the bonding curve route.
- 03GraduationWhat happens at the threshold and why buybacks pause.
- 04Fee accrualWhere fees sit before Plouto can see them.
- 05SweepsThe operator dependency Plouto cannot remove.
- 06The Fee EscrowThe pull-based contract Plouto claims from.
- 07Creator-fee recipientWhy the Revenue Router must exist before the token.
- 08Why Pons buybacks are disabledA five-year vesting vault is not retirement.
- 09Post-graduation routingSettling directly against the Uniswap v4 PoolManager.
Developers
Integrate with Plouto: configuration, reads, writes, events and indexing.
- 01Network configurationChain, RPC, explorer and viem setup.
- 02Contract ABIsWhere the ABIs come from and how to regenerate them.
- 03ReadsEvery view function worth calling, with examples.
- 04WritesThe complete set of state-changing calls and who may make them.
- 05EventsEvery event the protocol emits, with signatures.
- 06Indexing revenueReconstructing the full fee history from logs.
- 07Indexing staking positionsTracking positions, Gravity and claims over time.
- 08Running the buyback keeperHow the keeper computes a defensible slippage floor.
- 09Frontend integrationResolving the protocol from the registry, not from constants.
Architecture
Each contract, what it trusts, and how a fee travels end to end.
- 01PloutoRegistryOne-time validated initialization and the address book.
- 02PloutoRevenueRouterClaiming by measured delta and splitting immutably.
- 03GravityStakingPositions, the accumulator, and the rollover rule.
- 04BuybackExecutorRoute selection, bounds, and the retirement decision.
- 05PloutoReservePropose, wait, execute — and the guardian veto.
- 06Trust boundariesWhat is trustless, what is trusted, and who holds what.
- 07The complete fee journeyOne wei, traced from a trade to a retired token.
Contract reference
Addresses, functions, events, errors, roles and immutable settings.
- 01AddressesCanonical addresses and how to verify them.
- 02FunctionsFull external surface, by contract.
- 03EventsEvent signatures and when they fire.
- 04ErrorsEvery custom error and what triggers it.
- 05RolesWho can do what, and what they still cannot do.
- 06Immutable settingsValues fixed at deployment that can never change.
Deployments and proof
What is on mainnet, verified, tested, and still missing.
Security
Threats, mitigations, emergency levers and audit status.
- 01Keeper constraintsWhat a compromised keeper can and cannot do.
- 02Slippage protectionTwo independent bounds on every buyback.
- 03Reentrancy protectionGuards, ordering and the ETH claim path.
- 04PausingWhat pausing stops, and what keeps working.
- 05Emergency withdrawalThe principal-only escape hatch and its cost.
- 06Multisig and timelockThe operational requirements code cannot enforce.
- 07Pons dependencyThe external risk with no in-protocol mitigation.
- 08Audit statusPlouto is not audited. Stated plainly.
- 09Responsible disclosureHow to report a vulnerability.