Pons V1 vs V2: What Token Creators Need to Know

What changed with Pons V2?

Pons V2 changes the launch model compared with the earlier Pons V1 architecture. For token creators, this matters because the path from token creation to open-market liquidity is different.

Instead of treating V1 and V2 as interchangeable versions of the same launch flow, creators should understand which version they are using before planning initial purchases, wallet allocations and post-launch execution.

Pons V1 launch model

Pons V1 uses a liquidity-based launch architecture associated with Uniswap V3. Token creation and initial liquidity are therefore closely connected to the pool configuration used for the launch.

Creators working with V1 should review the exact launch configuration before preparing additional wallet actions.

Pons V2 launch model

Pons V2 introduces a bonding-curve stage before graduation. Trading begins through the launch mechanism and, after the relevant graduation conditions are reached, liquidity transitions to the post-graduation market structure.

This makes the launch lifecycle itself important when planning execution because the token can move through distinct stages rather than beginning directly with the same market structure used in V1.

Bonding curve and graduation

A bonding curve determines token pricing according to the launch mechanism while the token remains in its pre-graduation stage. Graduation marks the transition from that initial launch phase to the next liquidity environment.

Creators should understand which stage their token is in before interpreting price, liquidity or execution conditions.

Pons V1 vs V2 at a glance

• V1 and V2 use different launch architectures.
• V2 introduces a bonding-curve stage and graduation process.
• The liquidity path differs between the two versions.
• Wallet and purchase planning should reflect the version being used.
• Creators should verify current Pons parameters before executing a launch.

What does this mean for bundling?

A bundling workflow coordinates wallets and intended actions, but it does not make V1 and V2 mechanically identical. The execution plan needs to reflect the launch venue and version being used.

Before preparing a multi-wallet launch, confirm the Pons version, understand the relevant launch stage and review how each intended action fits into that workflow.

Which version should a token creator use?

The answer depends on the launch mechanics and liquidity path the creator wants to use. Rather than choosing based only on the version number, compare the current Pons documentation and understand how the token moves from creation to active trading.

Because launchpad mechanics can evolve, creators should verify current parameters immediately before launching.

Plan your Pons launch with TokenBundle

TokenBundle provides a Robinhood Chain workspace for coordinating token launch execution and participating wallets.

Always verify the current Pons launch mechanics, wallet allocations and transaction details before signing any transaction.