We Traced a Real Pons Launch Transaction End-to-End

The transaction

Before integrating against Pons's launchAndBuy function, we cross-checked our understanding three separate ways: Pons's own official documentation, the open-source contract repository, and a real, successful launchAndBuy transaction traced on Robinhood Chain's Blockscout explorer. All three agreed on the call's shape.

That transaction sent 0.0025 ETH in total for a 0.002 ETH quoteIn - a difference of 0.0005 ETH, which matches Pons's documented launch fee exactly. It's a small detail, but it's the kind of arithmetic that's easy to get subtly wrong if you only read a docs page and never check it against a call that actually executed.

What the call actually contains

A launchAndBuy call bundles the token's metadata and economics (name, symbol, description, socials, creator fee recipient, creator tax, whether buyback is enabled) together with the launch mechanics themselves: which launch config to use, which asset the curve is quoted in, how much to buy atomically as part of the launch, a minimum-tokens-out slippage guard, the recipient of that first buy, and the snipe-tax exemption list for other wallets buying in the same transaction.

All of that lands in a single atomic transaction - the token is created and the first buy (or buys, via the exemption list) execute in the same block, which is the entire mechanical basis for what a Pons bundle actually is.

Why trace a real transaction instead of trusting docs alone

Documentation can drift from deployed contract behavior - a parameter gets renamed, a default changes, an edge case isn't mentioned. Tracing a real, successful transaction and decoding its actual calldata is a way to catch that drift before it costs a user a failed or mispriced launch, rather than after.

This is also why TokenBundle reads several values live from the chain immediately before building a real launch call - the launch fee, the launch config's supply and thresholds - rather than hardcoding anything we've previously observed, since Pons's factory owner can change these over time.

FAQ

• Can I verify this transaction myself? Yes - it's public on Robinhood Chain's Blockscout explorer at robinhoodchain.blockscout.com, searchable by its transaction hash.
• Does the launch fee ever change? It can - Pons's factory owner can update it, which is why TokenBundle reads launchFee() live rather than relying on a fixed value.
• What happens to the snipe-tax exemption list in this same call? It's passed as part of the same transaction, so every exempted wallet's buy executes atomically alongside the launch itself - see our explainer on how that exemption list works.