Launching on Pons V2.
Tokens launch on Robinhood Chain through the Pons V2 contracts, in a single transaction signed by your wallet. SNEAKS prepares and checks that transaction before you sign it.
Your walletsigns one transaction
Pons V2creates the token and its curve
Token livetrading on its curve
SNEAKSverifies and lists it
with a dev buy, the tokens go straight to your wallet
One transaction
- Without a dev buy, your wallet calls the Pons V2 factory directly and sends the launch fee.
- With a dev buy, your wallet calls Pons' launch-and-buy router, which creates the token and buys it in the same transaction. It sends the launch fee plus the dev buy, and the tokens go to your wallet.
Checked before you sign
- 1
Read the factory
SNEAKS reads whether launches are enabled, the current launch fee and the maximum trading fee from the Pons factory.
- 2
Simulate
The launch is simulated from your address to learn the address of the token's curve, which goes into its website link.
- 3
Simulate again
A second simulation with the final details surfaces any error before your wallet opens.
Token details
Pons writes the token details on chain and rejects anything over its byte limits. SNEAKS keeps the form comfortably inside them.
| Field | SNEAKS form | Pons limit |
|---|---|---|
| Name | 32 characters | 64 bytes |
| Ticker | 2 to 10 letters or digits | 16 bytes |
| Description | 500 characters | 2048 bytes |
| Image link | Set by SNEAKS after upload | 512 bytes |
| X and Telegram | Handle or community name | 256 bytes each |
| Website | Set by SNEAKS | 256 bytes |
How a launch gets listed
- The transaction receipt must show a successful Pons V2 launch.
- The factory must report the SNEAKS treasury as the token's fee recipient. Launches with another recipient aren't listed.
- The paired sneaker is read from the token's website link.
Something unclear or missing? Tell SNEAKS on X.