Token Guard
Review a supported mint’s token controls and available concentration data.
Currently decode the entire Pump lifecycle, verify migration, or certify LP burns.
A launch moves through curve state, trading, and migration. Separate the token, the quote asset, and the eventual pool.
Curve reserves and actual balances are different concepts.
Completion and migration are distinct observations.
Current configurations and fee modes must be checked.
A Pump launch is a technical process, not a security endorsement. The useful questions are which mint you are tracking, what state it is in, and which public accounts support the claim.
This reference explains Pump mechanics. It does not announce a GudTek token, price, launch date, or allocation. Check the holder network for the deployment’s configured mint and access status.
Walk through the flow. Each step gives you one practical question to investigate.
Creation associates a token with a bonding-curve account. Public documentation describes global configuration, per-coin state, and version-dependent fields.
Conceptual flow, not a live transaction trace. Use the sources below for implementation details.
Start from the mint and published program references. A similar ticker, suffix, or pool name does not establish authenticity.
Look for Published mint + program IDs + derived account relationsCheck the current curve or pool configuration, quote asset, and applicable fee mode. This guide deliberately does not hardcode a price or graduation target.
Look for Current account layout + official IDL and fee documentationDistinguish the documented migration mechanism from verification of a specific token’s liquidity or LP-token disposition.
Look for Migration transaction + canonical pool accountsPublic protocol documentation and IDLs, not a full implementation source-code audit.
Resolving its default branch and pinning one commit.
Read-only · No account connection · No code executionReview a supported mint’s token controls and available concentration data.
Currently decode the entire Pump lifecycle, verify migration, or certify LP burns.
Map the public documentation and IDL repository as reference material.
Treat documentation as the deployed program’s complete implementation.
We’ll prefill the target. You review the scope before anything runs.
Live launches require verified holder access.Has the GudTek launch mint been officially published?
Which account proves the present curve or migration state?
Which wallets are owner addresses, pools, or program-derived accounts?
Does a claimed holder privilege match GudTek’s actual access rule?