Pons

PONS is the fixed-supply PonsLauncherToken at 0x39dBED3a2bd333467115dE45665cC57F813C4571 on Robinhood Chain 4663. Official docs identify it as a graduated legacy V1 reference launch and publish its transaction and pool. That documentary attribution remains separate from the deployed launchFactory value, which this follow-up could not independently verify.

The constructor minted all 1,000,000,000 tokens to the factory. The factory placed supply into a one-sided Uniswap V3 position and locked the position NFT. The token, factory and pool are three separate addresses, so none should substitute for another in an explorer link.

The published V1 token source limits launch-window pool buys, while the docs describe launch-block blocking, a 5% wallet ceiling and a 5.5% cumulative-buy ceiling. The constructor stores its caller as immutable launchFactory, and only that caller may set the temporary initial-buy recipient. The docs map 0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feB to active V1 and 0x0c37a24F5D23A486FA692d1500881d698B1F77a4 to legacy V1. Neither label alone proves which address is stored in PONS or its exact deployment parameters.

Those checks applied only to buys from the configured pool until restrictionEndBlock. Selling and wallet transfers remained open. The PONS contract has no post-constructor mint, blacklist, pause or proxy upgrade path, and the reference token has already graduated.

The docs describe locked V1 positions with fees snapshotted at launch: legacy launches retain 90% for the creator and 10% for the protocol; active V1 launches from block 8,991,118 use 70/30. Because the exact PONS factory has not been independently resolved here, this page does not assign either split to PONS as a verified contract fact. Graduation records a paired-WETH threshold, not a quality or exit guarantee.

Current protocol docs say 80% of the protocol’s own fee share is routed through an automated TWAP to buy PONS and send it to the burn address, while 20% funds infrastructure and team expansion. They also say the 80% policy is not immutable yet. A project policy can change even when PONS bytecode cannot.

The later V2 factory starts tokens on a constant-product bonding curve, then graduates them into permanently locked Uniswap V4 liquidity. It has a fee escrow, optional creator tax and per-launch buyback setting. These contracts govern newly launched tokens, not the already deployed PONS balance ledger.

A V2 launch buys its own token and locks it for gradual release to the creator and protocol, rather than burning it. The current vault source uses a five-year duration and blends additional deposits into a weighted-average release schedule; it is not one cliff that unlocks everything after five years. The platform policy that buys and burns PONS is separate.

The Pons site identifies Pons Labs, LLC in its footer and says wallets submit transactions while the interface does not custody assets. Its documentation disclaims warranties and blocks V2 access in the United Kingdom and OFAC-sanctioned jurisdictions.

No reviewed term grants a PONS holder company equity, governance, a share of fees, redemption, treasury ownership or a promise that buybacks continue. Burn-adjusted supply can be measured on-chain, but price, liquidity and legal remedies remain market and contractual questions outside the ERC-20.