PASTE THE CA.
CHECK THE CLAIMS.
Launched somewhere else? Bring the contract to GENNY. See available market and token risk signals, share the scan, then plan what your team will lock.
SCAN THE DEV.
FOLLOW THE RECEIPTS.
Check the wallet behind a launch before you buy. Start with a dev wallet, or use a token mint to find its reported creator.
The wallet has a history.
Find the pattern.
A reported creator is a starting point, not proof of who controls a project.
Created tokens, graduation rate, and lifetime peaks require an authorized history feed. Do not read missing data as a clean record.
RESEARCH ON GMGN ↗- How many launches did this wallet create, and how many graduated?
- Did prior tokens hold value after their peaks?
- Did the creator sell early or move supply to related wallets?
These are investigation prompts, not automated findings. One wallet may be only part of the team.
Review the live checks
GENNY summarizes attributed provider data. These checks are not a smart contract audit or a guarantee that a token can be sold later.
GO DEEPER.
KNOW WHAT CHANGED.
Explore the signals behind a token, with source links and a check time for every available finding. Pro access is planned for verified $GENNY holders.
PUT TEAM TOKENS
ON THE CLOCK.
Connect the dev wallet, declare the amount and unlock schedule, then execute a real lock when a supported locking contract is integrated. The contract address, transaction, balance and withdrawal powers must all be checked before GENNY can issue a secured lock receipt.
Connect your wallet to view its address. Project ownership remains unverified.
Wallet connection reads an address only. It does not prove who deployed the token or lock any supply.
WHAT MUST BE PROVEN.
- Correct chain and token contract.
- Team token balance and actual lock transaction.
- Unlock schedule and who can change it.
- Ongoing checks when permissions or balances change.