Swarmonic pons

A console for pons on Robinhood Chain

Every number about a token is already on the chain. This console derives it.

Swarmonic reads a pons token the way the contracts state it — the pool's sqrtPriceX96, the paired WETH against the graduation threshold, the snapshotted creator split — and does the arithmetic in exact rationals rather than floats.

It holds no key and sends nothing. You paste the values in, or read them yourself.

CA 0x3Fb8D2b240037F71f737b36acED2Cb30e7814cAd

On Robinhood Chain. Check the address against the pons token page before you trade anything — names and tickers can be copied.

—

the engine The mark above is doing what this page does: summing terms exactly. Every figure and every result on this page is computed the same way — in rationals, never in floats.

01 — the chain

Not a bonding curve.
A locked pool from block one.

pons is a launchpad on Robinhood Chain. Creating a launch deploys the token and its trading pool in a single transaction, and the pool's liquidity is locked automatically.

Every token trades against WETH in its own Uniswap V3 pool, quoted against WETH only. There is no bonding curve and no migration later — buys and sells happen in that same pool from the moment it launches, and continue in it after graduation.

What that means for the arithmetic. There is no curve formula to model and no migration to anticipate. The price is the pool's slot0, and everything downstream — market cap, impact, graduation — is a rational function of it.

02 — the launch

Six things happen.
Three of them you control.

Every stage below is a fact from the pons protocol documentation. The rail advances on its own; point at it and it waits for you.

03 — the protection window

Two blocks of limits.
Then it is over.

the launch block

Only the creator's initial buy can execute. Nothing else gets in on that block.

the rest of the window

Each wallet may hold at most 5% of supply and buy at most 5.5% of supply.

never restricted

Selling and wallet-to-wallet transfers are unrestricted throughout. All limits end when the window closes.

Read the caps as amounts, not just percentages

With a fixed supply of one billion tokens the caps are five million held and five and a half million bought per wallet. On a thin pool that is a large position — the caps limit concentration, they do not make a launch safe.

04 — the instruments

Paste the onchain value.
Get the exact answer.

Five calculators. Each field names the call that produces it, and each result shows the working rather than only the answer. The arithmetic is rational — no float touches the result.

Why exact arithmetic, here of all places

A V3 pool states its price as sqrtPriceX96, a uint160. Turning that into a double throws away everything past the 53rd bit, and the price is the square of that number, so the error is doubled before it reaches your market cap. For a dashboard that is fine — the two paths agree to about fifteen significant figures. For a trade it is the difference between the number you were quoted and the number the pool holds.

05 — the same arithmetic, drawn

Four figures that
compute themselves.

Nothing below is a picture of a calculation — it is the calculation, running at your frame rate on the same exact rationals the instruments use. Point at any of them and the numbers underneath track what is on screen.

01

The invariant

A pool holds x·y = L². The price is the slope of the tangent where you are standing, so a buy does not move a "price" — it walks you along the curve. Every step is computed from the same formula the instrument uses.

—

02

The cost of size

Price impact against trade size on a fresh launch, sampled ninety times across a single WETH. It is not a line. The first tenth of an ETH costs a few percent; the last costs multiples of the pool.

—

03

The threshold

Paired WETH climbing to the graduation line — and continuing past it, because crossing the threshold changes nothing about the pool. There is no migration to draw.

—

04

The split

Where a trading fee actually goes. The creator keeps the larger share, snapshotted per token at launch; most of the protocol's share is spent buying PONS and burning it.

1% pool fee · creator 70 / protocol 30 · buyback 80% of the protocol side

06 — fees, buybacks and burns

The split is snapshotted.
It never changes after launch.

The two creator splits pons has used.
factorycreatorprotocolfrom block
Active70%30%8,991,118
Legacy90%10%8,600,612

Which split a token gets

It is fixed when the token launches and read back from the locker via tokenProtocolFeeShares(token). Do not assume 70/30 — a token from the legacy factory keeps 90/10 forever.

07 — the reference

Every address, every call,
in one place.

Transcribed from the pons documentation. Deployed contracts are immutable; new versions ship as new factory and locker addresses, so resolve the locker from the factory rather than hardcoding it.

pons contract addresses on Robinhood Chain.
contractaddressnote

onchain events — the authoritative source

Topic hashes for the two events that matter.
eventtopic0

Index the factory's TokenLaunched, register each emitted pool, then index its Swap events. There is no migration event.

what the token says about itself

Reads served directly by the launch token.
readreturns

Every launch token is self-describing onchain — metadata and the canonical pool address come from the token itself, with no off-chain source required.

from the factory

Factory reads.

from the locker

Locker reads.

09 — the engine, verified

It proves before it speaks.

The instruments above price a pool with exact rationals. Here is that discipline pointed at mathematics you can check by hand — five claims about the harmonic series, re-derived in your browser's own integer arithmetic on every load. No floating point decides any of them. Every row is recomputed, not remembered. Not one line of it is about pons, and that is the point: this is the method, and you can audit it.

qed :: boot prover running

recomputing…

10 — the solver

Ask it something.
It answers with a proof.

The prover above settles five fixed claims. This is the same machinery pointed at whatever you type: a harmonic number to thirty digits, or the exact point at which the series passes a threshold — each returned with the interval it was decided on, how wide that interval is, and which engine produced it. It has nothing to do with pons. It is here because it is the arithmetic this console is built on, and because you can check it.

the harmonic number n up to 19 digits
the first crossing T up to 100
every crossing to 20, computed in this tab
The smallest number of terms needed for the harmonic sum to exceed each threshold, computed live.
thresholdsmallest nH(n)enginetime

computing…

08 — honest scope

Independent, and it says so.

Read this before you rely on anything above

Swarmonic is an independent console. It is not affiliated with, endorsed by, or operated by Pons Labs, LLC, and it implies no partnership or official status. The protocol facts are transcribed from docs.ponsfamily.com and belong to them; check them against the app before you act on anything.

This page holds no key, signs nothing, and makes zero network requests. The calculators run entirely in your browser on values you paste in — they cannot read the chain for you, and they do not try. Nothing here is investment advice, and nothing here is a statement about any token's quality or safety.

Tokens launched through pons are user-created and experimental. Prices move quickly, liquidity can be thin, and similar names and images can represent unrelated tokens. Review the token address, creator, liquidity and transaction preview before signing anything.