What a deployment set is
Five contracts that work together as one launchpad.
A pons launchpad is not one contract. It is five, each with a single job: a factory that creates tokens, a hook that collects trading fees, an escrow that holds those fees until someone withdraws them, a locker that permanently holds pool liquidity, and a buyback vault.
A set is one full copy of that machine. Finding six means six separate launchpads exist on chain. The documentation describes one.
The six sets
Green is the only one the documentation publishes.
| Set | Factory address | Owner | In the docs? |
|---|---|---|---|
| 1 | 0x7eD598Bc…1EC7e | pons multisig | Published |
| 2 | 0xD3C2280f…99fd7 | Wallet C | Silent |
| 3 | 0x7E1EAbd5…84dB8 | Wallet A | Silent |
| 4 | 0x050e5C22…39b39 | Wallet A | Silent |
| 5 | 0xF72c4Be7…227d1 | Wallet C | Silent |
| 6 | 0x22E95047…5ef79 | Wallet B | Silent |
Sets 3, 4, 5 and 6 all share one escrow (0xbc39B650…). Four separate launchpads, one money box.
How the wallets surfaced
This is the step people find surprising, so here it is in full.
The file gives you contract addresses only. No wallet appears anywhere in it — searching the entire pons site for these wallet addresses returns zero results.
Every contract stores the answer to owner() inside itself, and is built to hand that answer to anyone who asks. So pons tells you the address of the house. You knock, ask who owns it, and the house answers.
The question
The raw answer
0x8da5cb5b is not a secret code. Contracts do not understand words, only 4-byte codes, so owner() is hashed through an open formula. Anyone hashing the same word gets the same code, forever.
Four contracts, one answer
The three wallets
These are not contracts. They are ordinary wallets — somebody holds the seed phrase. Labels A, B and C are mine, not pons.
Wallet A
0x0815A4881f9c4073a70fdF00600EbA54c5a5baAa
Wallet B
0x84b8afFbd7728217F97c8Eb47FE4bDa07d97b8c1
Wallet C
0xfDdE5a1E3cdf791dA71e49F817d70C7cEd72cc36
This one is different. It holds 18.62 ETH waiting in the escrow that serves every launch happening today, meaning it is still a registered fee recipient on live tokens.
The money
Balances sitting in the currently active pons escrow.
What this proves, and what it does not
The most important section on this page.
Six sets exist; the docs publish one
Visible in the JavaScript file that the pons site itself loads. Anyone can open it and count.
Three ordinary wallets own the five unpublished sets
The contracts answer this themselves through owner(). It is stored state, not interpretation.
Wallet C has 18.62 ETH claimable in the live escrow
Read directly from the escrow contract that serves current launches.
That these three are the pons team
What is proven is contract ownership, not identity. Blockchain addresses carry no names. They could be internal developers, outside contractors, or people no longer involved. On-chain data alone cannot settle it.
That $TEST is a pons v2 test token
The claim on the banner at the top of this page. It does not survive checking.
About $TEST
The banner calls it a pons team token. Checked from three angles, it is not.
True: Wallet A did send the transaction that created it. Blockscout shows the creator as a factory contract, but the human behind the transaction was Wallet A.
Not true: that it has anything to do with pons or pons v2.
Not one pons v2 function. A different owner. A separate escrow. It is an unrelated launchpad, and Wallet A used it the way any ordinary user would, two months earlier.
Worth adding: Wallet A holds a zero balance in the live pons v2 escrow. There is no trace of it launching anything there.
Why publish a claim that fails?
Because if a false claim travels alongside a real one, anyone can knock down the weak part and the solid finding collapses with it. The six sets stand on their own. The banner does not.
Verify it yourself
Do not take this page's word for it. Three minutes.
In a browser: open the JS file, press Ctrl+F, search memeHook, count the hits. Then open Blockscout, paste a contract address, go to the Read contract tab, find owner, and click the arrow beside it.
Ignore the "Connect your wallet" button. That is only for functions that change data. You are only reading. Never connect a wallet just to read.
In a terminal, one command
The filename can change
If pons redeploys, 3ixguogfb526s.js may be renamed and the command above returns nothing. Get the new name from the page source of docs.ponsfamily.com/v2 and search for _next/static/immutable/chunks/.