Documented on the ponsfamily GitHub.
On 23 July, ponsdotdev committed a file to the official Pons repository titled “Add Snop ($SNOP) protocol reference test token”. It described snop as a mirror test token and listed the wallet that would deploy it.
“The name is ‘pons’ spelled backwards, representing a bidirectional check of protocol behavior.” — the deployer, block 17,661,055
The receipts.
Doc committed. ponsdotdev publishes the dev wallet address.
That wallet calls launchToken(). snop is created, liquidity seeded and locked in the same tx.
Deployer buys, then dumps the entire bag back into the pool nine seconds later. 0.0555 ETH in, 0.0703 out.
Final sell. Deployer balance hits zero and stays there.
Doc deleted — 24 seconds after the last sell. It existed for exactly one commit.
Deployer holds nothing. Liquidity stays locked. The contract runs unattended.
No allocation. No presale. No unlocks.
Every token in circulation was bought out of the pool at market.
- Total supply
- 1,000,000,00018 decimals
- Team allocation
- 0none, ever
- Deployer holds
- 0exited 24 Jul
- Liquidity
- LockedNFT held by the Pons locker
| What | Address |
|---|---|
| Token | 0xc4CB8A0167c77e36194F6aFFb6B71D931Fab62C0 |
| Uniswap v3 pair | 0x1E1779d5Cf272a54Ce27Df5c9Eb718Ed5649D125 |
| Pons launch factory | 0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feB |
| Liquidity locker | 0x736d76699c26d0d966744cae304c000d471f7f35 |
| Deployer (empty) | 0x698d3e165c1ea84aa23ea02ca8a91f574e4c70eb |