How the Launch Transparency Score works

The eight checks

1. Tokenomics published. Is the allocation of the supply published by the project?
2. Unlock schedule published. Are vesting and unlock terms for team and investors published?
3. Float at TGE disclosed. Is the circulating supply at TGE disclosed?
4. Market maker disclosed. Has the project named its market maker or disclosed the arrangement?
5. Listing venues announced. Has the project officially announced where the token trades?
6. Team or entity named. Are team members or a legal entity named on official pages?
7. Audit report public. Is an audit report for the core contracts public, with the auditor named?
8. No unresolved incidents. Is the project free of unresolved exploits, lawsuits or regulator actions?

Rules

• A check passes only when an official source proves it: the project's own site, docs, blog or posts, or the auditor's own report page. A disclosure the project itself files on a third-party transparency platform, such as a Blockworks Token Transparency filing or a MiCA white paper, counts as official. Aggregators are used to find pages, never as the proof.
• "Not published" means we could not find it on official pages on the date checked. It is not an accusation.
• Before a token lists, "Listing venues announced" stays unpassed until the project announces venues.
• Projects months away from launch usually score low, because tokenomics and venues are not published yet. A low score early on is normal; it rises as the project publishes.
• Incidents are reported neutrally. Allegations are labelled as allegations, and outcomes are stated where they exist.
• Every profile shows the date it was checked. We recheck weekly and log changes publicly.
• Nobody can pay for a score, a placement or an inclusion. Buying any TGE Index service never changes a score.
• Projects can send corrections with an official link. Corrections are free.