Pons (PONS)

What Pons is

Pons, which its own documentation styles in lowercase as pons, is a token launch protocol on Robinhood Chain. Its documentation defines it as "a noncustodial token launch and trading interface on Robinhood Chain," and states plainly that "pons never takes custody of tokens or funds" (source: pons documentation, read September 2026). Every action is a transaction signed by the user's own wallet.

The chain it runs on is identified by chain ID 4663. In version 1, launched tokens trade against wrapped ether in live liquidity pools. Version 2 changed the shape of a launch entirely.

How it works

Version 2 replaces the launch-day liquidity pool with a curve. The documentation describes the sequence: "a creator deploys a token, the public buys it from a bonding curve, and once the curve is bought out the launch graduates into a Uniswap v4 pool whose liquidity is locked permanently."

The reason for the change is stated in the documentation and is worth reading closely. "A launch no longer starts life as a pool. It starts on a curve that holds the entire supply, and the pool is created only at graduation, seeded from what the curve collected. That removes the launch-day liquidity problem: there is nothing to snipe before the curve opens, and no separate migration step for a creator to get wrong."

The lifecycle has four fixed steps, and the documentation emphasizes that "there is no path where a creator decides to do something different halfway through." At creation, the creator sets a name, symbol, image, description and links, pays a launch fee, and the entire supply is minted straight to the bonding curve. The documentation draws the consequence: "no one, including the creator, is holding a bag of tokens set aside before trading opens."

During the curve phase, anyone can buy or sell, and a holder "can always sell back to the curve." At graduation the curve closes and what it collected builds the pool. Nothing is required of a holder when the switch happens, and the tokens in a wallet are the same before and after.

Anti-sniping is enforced by a decaying tax rather than by a delay. The documentation states that "buys in the first 5 seconds of a launch pay a decaying snipe tax, starting at 99% and halving repeatedly to zero," and instructs integrators to read currentSnipeTaxBps(recipient) on the curve before quoting a buy. A bot buying in the first moments surrenders almost the entire purchase.

Launches do not have to be priced in ether. The documentation says a launch "can be paired against another token, and when it is, that token becomes the currency of the whole launch," used for buying, selling and creator payouts alike.

Supply and tokenomics

The documentation covers the launch protocol rather than a PONS token supply, and the parameters it does publish are contract-level rather than economic.

Two operational facts in the documentation matter for anyone integrating or interpreting a launch. Public launching is closed, so a create flow must check canLaunch(address) on the factory first. And the curve has no quote function at all, so a price must be computed from reserves, the fee in basis points, the creator tax and the sellable supply.

The documentation also warns about identity in a way most launchpads do not: "token names and symbols are not unique. Contract addresses are canonical." Two launches can share a name, and only the address distinguishes them.

RampAtlas could not source a supply figure, allocation or utility for the PONS token itself from the protocol documentation, which describes the launch platform rather than a platform token. Those figures are recorded here as unpublished.

History

pons version 1 launched tokens directly into liquidity pools paired against wrapped ether, with a separate liquidity locker contract. That design carried the two problems the documentation names: tokens could be sniped before ordinary buyers reached the pool, and the creator had to perform a migration step correctly.

Version 2's curve-first design removes both. Because the curve holds the entire supply from the moment of creation, there is no pre-existing pool to front-run, and because graduation is executed by the protocol rather than by the creator, there is no migration to get wrong.

The version 2 contract set shows how much of the lifecycle is now automated: a factory, a hook, a fee escrow, a buyback vault, a launch locker, a router, a deployer, a graduation executor and a graduation guard. The documentation warns that this stack evolves, and that "a token launched before it settles through the hook and escrow it was created against," so integrators should resolve a token's stack from the factory that launched it rather than assuming the current one.

Risks and what to watch

Token identity is a practical hazard. Names and symbols are not unique on pons, so buying by name rather than by contract address is how people end up holding the wrong token. Verify the address on a block explorer before transacting.

Chain concentration is a structural dependency. pons runs on one network, and its liquidity, its users and its contracts are all there. The protocol's fortunes track that chain's.

Curve microstructure is unforgiving. Prices move sharply along a bonding curve, fees come off the input on buys and the output on sells, and there is no quote function to lean on, so a poorly constructed trade can suffer severe price impact.

Post-graduation liquidity is locked but not deep. A permanently locked pool cannot be withdrawn by a creator, and it can still be thin enough that ordinary size moves the price substantially.

Smart contract risk spans a large surface: factory, hook, escrow, buyback vault, locker, router and graduation contracts, plus each launched token. The documentation lists audits, and reading them is the right starting point.

Frequently asked questions

What is pons?

A noncustodial token launch and trading protocol on Robinhood Chain. Creators launch tokens onto a bonding curve, and the curve graduates into a permanently locked Uniswap v4 pool once it sells out.

What is graduation?

The point at which a launch's bonding curve sells out and its collected proceeds seed a Uniswap v4 pool. The documentation notes it is not a guarantee of quality, liquidity or future performance.

How does pons stop snipers?

Buys in the first five seconds pay a tax starting at 99% and halving repeatedly to zero. Because the curve holds the entire supply from creation, there is also no pre-existing pool to front-run.

Can a creator pull liquidity on pons?

Not from a graduated launch. The documentation states the Uniswap v4 pool's liquidity is locked permanently, and that the entire supply is minted to the curve at creation rather than held by the creator.

Where can you buy Pons?

See where to buy Pons for the venues serving your jurisdiction, and Exchanges to compare fees and kyc requirements.