Robinhood Chain contract evidence

PonsLauncherToken is a contract label, not a unique token.

Multiple assets can use the same implementation name. The exact contract address is the identity. Check the creator, verified source, active controls, and real liquidity before treating any Pons launchpad token as understood.

NetworkRobinhood Chain · ID 4663
Published factory0xA5aA...1feB
Contract patternFixed-supply ERC-20 launch

What PonsLauncherToken means

The public Pons contract repository describes `PonsLauncherToken.sol` as the token implementation spawned by its launch factory. The repository says a launch can deploy a fixed-supply ERC-20, create a one-sided Uniswap V3 position, lock the position NFT, and apply temporary early-buy limits.

Important: implementation design is not address-specific proof. A token still needs to match the expected factory, deployed bytecode, pool, locker, and current control state.

Check the actual launch in six steps

1

Confirm chain and address

Use Robinhood Chain ID 4663 and the complete token address. Do not search by contract label alone.

2

Trace the creator

Compare the creation transaction and factory with the published Pons factory evidence. A lookalike deployment can reuse a name.

3

Match verified source

Check whether explorer source and compiler metadata match the public implementation. Verification helps inspection; it is not an endorsement.

4

Read live restrictions

Identify whether same-block, wallet-cap, or cumulative-buy limits are active and when they expire.

5

Inspect the V3 position

Confirm the actual pool, fee tier, range, paired asset, position NFT holder, and whether withdrawal authority exists.

6

Verify token-specific claims

Compare name, symbol, socials, website, supply, and project claims with the contract address and onchain metadata.

Primary evidence

What this evidence does not prove

A standard launch path does not prove demand, honest promotion, sufficient exit liquidity, permanent liquidity access, or future price performance. It also does not make every token created by a factory equivalent. Address-specific state and current pool evidence still matter.

Frequently asked questions

Why do many tokens show PonsLauncherToken?

It is the shared implementation name used by tokens created through the launchpad pattern. The individual token address, metadata, and pool distinguish one launch from another.

Is the published factory enough?

No. It is a strong provenance check, but you still need to inspect the exact creation transaction, bytecode, controls, and liquidity position.

Does locked V3 liquidity mean I can sell?

Not necessarily. Range, depth, paired-asset balance, token restrictions, fees, and route conditions all affect whether a practical sell path exists.