What is Existing Project Claim, Product Claim, and Project Update?
Version V0.0.4
Existing Project Claim, sometimes called Product Claim in older UI copy, is the workflow for a launched or discovered project to request control of an existing TokenAnalyzer profile.
Project Update is the separate workflow for an already eligible project owner to submit updated public profile data.
Both workflows may use paid packages when enabled. Payment unlocks workflow access only. It does not approve ownership, verify a token, or improve trust.
When to use Project Claim
Use Project Claim when a token or mint already exists and TokenAnalyzer has discovered, indexed, or prepared a profile for it.
Project Claim is not the normal path for a future launch. If the token is not live yet, use Pre-Launch Registration instead.
For a launched pump.fun or similar launchpad token, start from the TokenAnalyzer Claim guide, find the mint, and open its Claim section. Check a current authority wallet first, or a historical creator wallet if authority has been revoked. If neither provides eligible owner proof, TokenAnalyzer may offer a separate Community managed / CTO request using a new operator wallet and a public project-linked social post. See the CTO steps. This is a manually reviewed profile-management path, not on-chain ownership proof or Trust verification.
Project Claim may be relevant when:
- a mint already exists;
- TokenAnalyzer shows an unclaimed or admin-prepared profile;
- the real project owner wants to manage the profile;
- the project needs to attach verified owner-controlled profile data;
- a prelaunch registration is no longer appropriate because the mint is already live or already discovered.
What the claim check looks for
TokenAnalyzer can check whether the connected wallet appears to match eligible ownership or authority evidence for the mint.
Depending on available chain data and profile state, this can include:
- existing TokenAnalyzer project-owner wallet records;
- Solana metadata update authority;
- Solana mint authority;
- Solana freeze authority;
- admin-prepared takeover eligibility;
- supporting source links and project context.
The claim readiness check is read-only. Opening the Claim tab or checking a wallet does not create a public claim, does not transfer ownership, and does not change the public profile.
What happens after a request
When an eligible wallet submits an ownership request, TokenAnalyzer may ask for:
- a wallet signature;
- contact details for admin follow-up;
- a project logo;
- website or social links;
- additional evidence if the chain signal is unclear.
Submitted claims go through admin review. A strong wallet signal can support the request, but it still does not automatically make the project safe, verified, or endorsed.
Typical update scope can include:
- logo;
- description;
- website;
- Telegram;
- X;
- Discord;
- other basic metadata reviewed by admins.
Claim or update payment does not:
- prove ownership;
- bypass admin review;
- bypass wallet proof;
- increase trust score;
- make the project safer;
- change on-chain authority facts.
For a claim, admins still review evidence such as wallet signatures, authority-wallet signals, source links, and project context before approving profile control.
For a project update, the project owner wallet must authenticate first. If the owner has an active Project Update entitlement, the form can be saved. Visibility windows for updated-project placement start after the owner successfully saves the update, not merely when payment is made.
Public community project creation is no longer the normal entry path. New projects should use Pre-Launch Registration before launch or a claim path for an already launched mint.
Important limits
Project Claim means profile-control review. It is not a safety badge.
An approved claim does not prove that:
- the token will perform well;
- liquidity is safe;
- contracts are risk-free;
- the team will act honestly in the future;
- TokenAnalyzer endorses the project.
It only means TokenAnalyzer accepted the profile-control evidence for the relevant workflow state.
Related FAQs: