PONS INU ENGINE
Pons Inu.
Built to
bake.
An independent inu for the Pons community.
Trading fees feed the engine. Let it bake.
big PIE energy.
01 / THE RECIPE
One pool.
Let it bake.
Trading fees feed three jobs: deepen PIE/PONS liquidity, buy and burn PIE, and keep the engine running. Real trading supplies the ingredients.
- 01
Collect
Claim this position’s trading fees and PIE creator fees credited by Pons.
THE INGREDIENTS - 02
Slice
Split newly earned fees into liquidity, PIE burns and a capped operating reserve.
GIVE EACH SLICE A JOB - 03
Bake
Buy and burn PIE. Add liquidity to the same permanent position. Small, guarded swaps do the work.
MORE DEPTH. LESS SUPPLY. - 04
Show the work
Track liquidity additions, actual PIE burns and ETH reserved for operations onchain.
PUBLIC RECEIPTS
Proposed recipe: 70% liquidity · 25% PIE burns · up to 5% operations. Final split and ETH reserve cap are not set.
When the reserve fills, its unused allocation goes to liquidity. The engine follows fixed contract rules; a keeper triggers eligible cycles. The AI is the character today.
02 / OPEN THE HOOD
Good dogs
keep receipts.
The contract has been tested on a local Robinhood fork. The mainnet engine, token and seed position have not been deployed.
- Completed cycles
- —
- PONS LP fees collected
- —
- PIE LP fees collected
- —
- Pons creator fees · ETH
- —
- PIE burned · total
- —
- PIE bought for burns
- —
- Operating reserve · ETH
- —
- Keeper payments · ETH
- —
No mainnet cycles yet. Transactions will appear here after the engine is funded and running.
Burns include PIE fees burned directly and PIE bought with the burn budget. Engine swaps can recycle some of its own fees; collected totals are not all new external income. Operating payments are owner-approved, not measured gas refunds. These figures do not measure holder profit.
03 / THE PONS CONNECTION
Pons is
the starting point.
PIE can launch on Pons against ETH. The engine’s separate PIE/PONS pool is then seeded with purchased PIE and funded PONS.
Direct PONS launch pairing was disabled at the last onchain check. An existing PONS market does not fund PIE’s new pool.
How Pons launches workPONS / WETH
The engine’s ETH conversion route uses this existing PONS market on Robinhood Chain.
- PONS price
- —
- Pool liquidity
- —
- 24h volume
- —
PONS/WETH data from DEX Screener. These are not PIE token or engine figures.
SMALL ENGINE. CLEAR RULES.
Know what’s under the hood.
Who controls the liquidity?
The engine contract owns one full-range PIE/PONS position. Seed assets, liquidity funds and the LP NFT are permanently committed: there is no liquidity withdrawal, NFT transfer or upgrade function. Burn funds can only follow their burn route. The owner can pay the configured keeper only from the accounted operating reserve. The owner can set a keeper, pause compounding and transfer administration through two steps. Pausing does not unlock capital. A contract fault could strand funds.
What keeps a cycle in bounds?
A cycle requires 30 minutes of price history and at least five minutes since the last cycle. Price checks can defer it for longer. Spot prices must stay within 50 ticks (about 0.5%) of their time-weighted average. Swaps are capped at 0.1% of the relevant pool’s input-token balance, with a further 0.5% output tolerance after pool fees. These checks reduce execution risk; they cannot eliminate manipulation.
Where do the fees go?
The proposed split is 70% permanent liquidity, 25% PIE burns and up to 5% operations. Burn share and the native ETH reserve cap are fixed at deployment; reserve overflow goes to liquidity. Only collected fees are split, never seed capital. PIE fees allocated to burns are burned directly; other burn funds buy PIE first. The secondary pool fee is 0.3%, and the engine earns its own position’s share. Pons creator credits depend on upstream sweeps. There are no holder payouts or builder splits.
What is ready today?
The engine contract, unsigned launch tools, keeper runner and this chain dashboard are implemented. The V2 candidate adds verified supply burns, separate fee budgets and capped operating payments. Those paths and Pons graduation have been tested against real contracts on a local fork. No mainnet launch or funding has occurred, and the code has not received an independent audit. An owner, seed budget, final fee recipe, reviewed starting price and funded keeper are still needed.
PONS INU. PONDERING THE NEXT PIE.
Made for
the Pons pack.
An independent community coin with an onchain job: turn collected trading fees into liquidity, PIE burns and the next cycle.
Good dog. Public receipts. Let it bake.