Pons volume botthat readslike a crowd,not a script.
Scoped to a single launchpad. Paste your Pons token contract, set the window, and real buy and sell orders start landing in the live pool on Robinhood Chain. You sign once and you're done.
Thousands of rotating maker wallets, timing drawn from a shaped distribution, order sizes that never repeat. Every fill lands in your token's own Uniswap V3 pool on Robinhood Chain, and at the end you get a receipt you can read yourself rather than a dashboard number you have to take on faith.
The line is the volume actually routed into your pool as the window runs, climbing to the figure you were quoted. The desk prices the run exactly the same way.
A Pons volume bot, and nothing else.
A Pons launch (ponsfamily.com) deploys the token and its Uniswap V3 pool in one transaction, paired against WETH with a 1% pool fee and liquidity locked from the first block. There is no bonding curve and no migration. Strata Maker exists to put visible, paced trading activity into that pool for the launches that deserve to be seen.
Only Pons pairs
The desk resolves your contract against Robinhood Chain and refuses anything that was not minted on Pons. Scoping it to one launchpad is what lets venue resolution and pacing be tuned instead of generalised.
One pool, start to finish
Every Pons token trades in its own locked Uniswap V3 pool against WETH from the block it launches. Graduation happens when the paired principal reaches 4.2 ETH, and trading carries on in the same pool. Nothing migrates, so the router never has to guess where your liquidity went.
Visibility, not demand
Routed volume moves a pair up screeners, trending lists and the charts people actually look at. It does not manufacture buyers, and this desk will never tell you otherwise.
Four constraints the tape has to satisfy.
Pushing trades through a pool is trivial. Making the record read like ordinary demand isn't, and it's a scheduling problem long before it's a trading one. Everything below exists because a tape that repeats itself gets spotted in about thirty seconds by anyone who bothers to look.
Jittered pacing
SchedulerGaps between fills come from a shaped distribution instead of a fixed cadence, and the scheduler resamples after every confirmation, which means no window of the tape ever settles into a rhythm you could set a metronome to.
Disposable wallets
FleetUp to 8,000 funded maker addresses rotate through a run. Each one touches the pair a handful of times and then retires, so an address never shows up in a later campaign.
Uneven sizing
AllocatorOrder sizes follow a heavy-tailed draw with the occasional outlier, because that's what real books look like. Flat repeating clip sizes are the clearest fingerprint a script leaves behind, and they're also the easiest thing in the world to avoid.
Settled, then reconciled
LedgerThe router places nothing until your fee transfer has confirmed. At the close of the window the delivered figure is checked against Blockscout, and a shortfall is returned to the paying address without a support ticket.
What a reader actually sees.
Left, a naive bot on a fixed interval with a fixed clip. Right, the same target volume routed through the pacer. The totals are identical; the record isn't, and the record is the only part anyone reads.
Fixed cadence
DetectableIdentical gaps, identical clips, a flat buy ratio. Every print is the same height and the pattern repeats on a period anyone can measure with a ruler.
Strata Maker pacer
PacedClustered bursts, quiet stretches, the occasional outsized print, and a buy ratio that drifts inside the band you set instead of parking on one number and staying there.
One percent. The ladder does the rest.
The fee is a flat 1% of routed volume, paid once before anything starts. Larger targets earn delivered volume on top of what you paid for, applied automatically at the tier you cross.
Minimum run is 10 ETH of volume. The bonus is delivered volume, not a discount on the fee.
Configure, pay, watch. One surface.
There's no account and no dashboard tree to learn. The desk resolves your contract straight from the chain, prices the run while you drag the sliders, and takes a single transfer when you're ready.
Resolved on chain
Name, symbol, supply and the pool address come straight off the contract, so nothing here depends on a third-party index being awake when you need it.
One signature
You sign a single transfer for the fee. There are no approvals, no spending allowance and no contract call against your token, which is the whole reason this can't drain anything.
Readable receipts
The transaction hash is yours the moment you sign, and every fill that follows sits on Blockscout under the pair you gave us.
Asked before the first run.
Pons is the launchpad this desk serves. A launch deploys the token and its Uniswap V3 pool in a single transaction: fixed supply of 1,000,000,000, paired against WETH, 1% pool fee, liquidity locked automatically. It graduates once 4.2 ETH of principal is paired in that pool, and trading continues in the same pool afterwards. This desk is scoped to those pools on purpose: sizing, pacing and depth checks are tuned for how they actually behave rather than generalised across a dozen launchpads. A token minted somewhere else is turned away instead of served badly.
No. The only thing that leaves your wallet is the fee transfer you sign yourself. We fund and operate the maker wallets on our side, your treasury never gets approved for spending, and nobody from this desk will ever ask you for a key or a seed phrase. If someone does, it isn't us.
At the close of the window we reconcile the delivered figure against Blockscout. If it lands below what you contracted for, the difference goes back to the address that paid, and you don't have to open a ticket to trigger it.
That's the constraint the whole system is designed around: sizes come from a heavy-tailed draw, gaps get resampled after every fill, wallets retire for good, and the buy ratio drifts inside your band rather than sitting on a flat number. What it can't do is invent demand, and nothing here pretends otherwise.
The one your token was born with. Each Pons launch has exactly one Uniswap V3 pool paired against WETH, and the router reads its address straight off the token contract. There is no venue to choose and no second pool to split across, which is why sizing can be tuned to the depth actually sitting in front of the price.
Yes. For the first blocks after a Pons launch, each wallet may hold at most 5% of supply and buy at most 5.5%, and only the creator can buy on the launch block itself. The fleet sizes every order to stay inside those limits until the restriction window closes, so a run started on launch day never trips the protection rules.
Neither. The desk never asks for a key, never requests an allowance and never calls a function on your token. If a page or a message claiming to be us asks for any of that, it isn't us.
Your chart is quiet.
That is a solvable problem.
Paste a contract, set the window, sign once. The desk prices the run before you commit to anything.
Open the desk