Documentation

How it works.

Everything you need to know before launching a token with its own automated fee engine.

What is PonsV2?

PonsV2 is a token launchpad built on Pons. You launch a token from your own wallet, choose what should happen with its trading fees, and PonsV2 executes that strategy automatically: every 5 minutes it claims the token's fees and runs the engine you picked.

Four strategies are available: lock the fees as liquidity, buy the token back and burn it, pay the fees to stakers, or pay them to every holder. The choice is locked in at launch and shown on the token page, so every buyer knows exactly where the fees go.

The four strategies

01

Locked Liquidity

Fees buy the token and lock both sides into the pool forever. The pool only gets deeper, and nobody can ever pull it.

02

Buyback & Burn

Fees buy the token back from the market and send it to the burn address. Supply shrinks with every cycle.

03

Staking Rewards

Holders stake their tokens and earn the trading fees. Every cycle pays out ETH pro-rata to everyone staked.

04

Holder Rewards

Fees are paid straight to everyone holding the token, proportional to their balance. Just hold and receive ETH.

Launching a token

01

Fill in the details

Upload an image (stored on IPFS), choose a name and symbol, write a description and optionally add social links.

02

Pick a fee strategy

Choose what every trading fee should do: liquidity, buyback & burn, staking rewards or holder rewards. This choice is permanent and public.

03

Fund the vault

PonsV2 creates a fresh wallet just for your token: the vault. It claims fees and runs your strategy, and it pays its own gas, so it needs a small amount of ETH first. Send at least 0.001 ETH on Robinhood Chain to the address shown. The page checks the balance automatically.

04

Sign the launch

Your wallet signs one transaction and pays the launch fee. Your address is the deployer of the token on-chain. The vault address is baked into the launch as the fee receiver, so all trading fees flow to it from the very first trade.

05

Done, it runs itself

Your token gets its own page with live stats, a cycle countdown and a log of every action. The first cycle runs about 5 minutes after launch.

The cycle

Every 5 minutes, each token claims its fees and runs its strategy. The exact steps depend on the strategy:

01

Liquidity

Swap half the fees for the token, then lock both sides into the launch position forever. The deeper pool means less slippage and no rug, ever.

02

Buyback & burn

Swap all the fees for the token, then send everything to the dead address. Supply shrinks permanently with every cycle.

03

Staking rewards

Convert all fees to ETH and pay it out pro-rata to everyone who has staked, straight to their wallets. Payouts run once the pot reaches 0.0005 ETH.

04

Holder rewards

Convert all fees to ETH, snapshot the holder list, and pay every holder their share. Just hold the token and receive ETH.

If there are no fees to claim, the cycle simply waits and tries again 5 minutes later. Every step is logged and shown live on the token page, with links to the transactions on Blockscout.

Isolated vaults

Every token gets its own vault: a unique wallet generated at launch, used for nothing else. Its private key is encrypted with AES-256-GCM before it is stored, and it is only ever decrypted server-side at the moment a cycle runs.

Because vaults are one-per-token, fees almost never mix. Token A's fees run token A's strategy. Always.

10% of every claim is sent to the official PonsV2 token's vault. So every token launched on the platform also feeds the main token's engine.

Timing and countdowns

The 5-minute interval is per token, counted from that token's last cycle, not from a global clock. A token launched at 18:03 cycles at 18:08, 18:13 and so on, while one launched at 18:05 cycles at 18:10, 18:15. That is why every token shows its own countdown.

Contracts

FAQ

Do I need to sign anything after launch?+

No. Your wallet signs exactly one transaction: the launch. Everything after that (claiming, swapping, burning, distributing) is signed by the token's own vault wallet on the server, automatically.

Who launches the token on-chain?+

You do. The deployer of your token is your own connected wallet, not a shared PonsV2 wallet. PonsV2 only inserts the vault address as the fee receiver.

Can I change the fee strategy later?+

No. The strategy is chosen at launch and locked in. That is the point: buyers can trust that what the token page says is what the fees will always do.

Can fees from one token be used for another token?+

Almost never. Every token has its own vault, and 90% of its fees only ever run its own strategy. The remaining 10% goes to the official PonsV2 token's vault. That is the only cross-token flow, and it is the same for everyone.

Why does the vault need funding before launch?+

The vault pays gas for its own transactions. It starts empty, so it needs a small amount of ETH to pay for its first claim. After that, every cycle leaves a small gas reserve behind, so it keeps running on its own.

What happens if there are no fees to claim?+

The cycle logs "Waiting for fees" and tries again 5 minutes later. Nothing is lost; fees keep accumulating in the pool until they are claimed.

How does staking work without a staking contract?+

You transfer tokens to the token's isolated vault, and the deposit is verified on-chain from the transaction. Unstaking is authorized with a wallet signature and paid back from the vault immediately. Rewards arrive in your wallet as plain ETH every cycle, no claiming.

How are holder rewards distributed?+

Every cycle the vault converts its fees to ETH, takes a live holder snapshot from the chain explorer, and sends every holder their share, proportional to balance. Pool, vault and burn addresses are excluded.

Can the burned supply come back?+

No. Buyback & burn tokens are sent to the dead address (0x...dEaD). Nobody holds that key. The supply reduction is permanent and verifiable on-chain.

Ready to launch?

Launch a token

One transaction. Your rules, forever.

Docs · PonsV2