CryptoRank listing: project facts and funding round records

Two CryptoRank records require separate fact checks

The project profile and fundraising round are 2 distinct records to prepare. We keep their details separate so an edit to one does not silently change the other.

A project profile usually draws on the official project name, description, website, social channels, and relevant chain or product details. A round request needs its own approved facts, such as the round label, announcement date, and supporting public material where available. Your team decides what it is ready to disclose.

Our first pass compares 5 fields: proposed names, descriptions, official links, project details, and round facts. We mark discrepancies in dates, wording, and source links. We do not fill gaps by inference. A project contact resolves unclear items before the submission draft is prepared.

This service fits a team preparing a new record, a funding update, or a correction to public information. It is not a visibility placement or a substitute for maintaining a complete project record. If you are coordinating several trackers, start with listings and verification. Separate requests may be needed for CoinMarketCap, CoinGecko, or other crypto trackers.

Which evidence belongs in a CryptoRank record?

A five-field evidence check gives the project team a clear basis for approval. We compare the proposed name, description, official links, relevant project details, and round information with the sources you share.

Send public source material that directly supports each claim. An official project page or announcement can help clarify wording and dates. If a fact has no public source, mark it for the project contact to confirm and decide whether it is suitable for publication. Do not include confidential investor or commercial terms unless your team has explicitly approved disclosure.

For a round request, identify the exact round label and the announcement your team considers authoritative. For project information, share the wording currently used on official channels. If the project has changed its name or contract, include the public explanation and distinguish former details from current ones.

We return a gap list rather than smoothing over contradictions. That list records what needs a source, what needs correction, and what requires an approval decision. Teams managing related records should keep tasks distinct. Circulating supply verification and contract migration or rebranding updates are separate work items. They are not automatic parts of a CryptoRank request.

A three-checkpoint review keeps the submission traceable

Three checkpoints structure our work: source review, client approval, and submission follow-up. Each checkpoint leaves a record your team can revisit.

At checkpoint 1, we compare the proposed details with the supplied evidence and list open questions. At checkpoint 2, your designated contact confirms the wording and identifies which round details may be used publicly. At checkpoint 3, we record the version coordinated for submission and any correspondence available to us.

A single decision-maker helps keep edits consistent. Ask that person to return consolidated corrections instead of separate versions from several team members. This also makes it easier to establish which wording has final approval. Before submission coordination, check that project links work, names match the chosen sources, and round information has clearance for publication.

The submission route is confirmed for the request at the start. We do not assume that an older route still applies. The handover record can include the approved draft, source links, confirmed route, and available correspondence. If you are also seeking a CoinMarketCap community verification, plan it as a separate request with its own supporting information.

The handover records scope, approval, and follow-up

The deliverable is a traceable request pack, not a platform decision. We confirm whether the agreed scope covers a project profile, a fundraising round, or both before preparing materials.

A typical request pack includes:

• A review of supplied project facts and public sources.
• A list of missing details, conflicts, and approval decisions.
• A draft for the authorized contact to review.
• Coordination through the route confirmed for the request.
• A record of the submitted version and available follow-up.

The handover keeps 4 practical items together: the approved draft, source links, submission details, and correspondence available to the project. This gives your team a reference for later questions or a future update. It also makes clear which information came from public sources and which wording received internal approval.

Work can move to submission coordination once the project has resolved open questions and approved the draft. We agree the timeline after reviewing source readiness and your approval path. If the project also needs exchange or launchpad work, keep those scopes separate. See centralized exchange listing or launchpad listing for those distinct requests.

CryptoRank controls review and public presentation

The platform makes the final decision on whether a request is accepted and how an accepted record appears. Our work cannot determine CryptoRank’s review, categorization, display timing, or later changes to its records. We commit to the agreed preparation, submission coordination, and documented follow-up, not to a particular platform outcome.

Before approving the draft, run these 4 checks:

• Does each public claim match a source the project recognizes?
• Are round details cleared for disclosure by the authorized contact?
• Do current names and links reflect any announced project changes?
• Can one contact answer follow-up questions and confirm corrections?

If a detail remains uncertain, hold it for clarification rather than treating it as established. This avoids carrying an unresolved conflict into the submitted version. Our review makes the evidence and open decisions visible to your team; it does not replace the platform’s own evaluation.

Send us the official website, the project or round details for review, supporting public sources, and the name of your approving contact. We will assess the materials, identify open points, and return a scoped plan for the CryptoRank request.

How it works

1. 1. Share the project recordSend the official website, project links, and profile or round details for review. Name one contact who can confirm facts and approve public wording.
2. 2. Review sources and gapsWe compare proposed details with the materials you provide. You receive questions about missing, unclear, or inconsistent information.
3. 3. Approve the draftYour authorized contact confirms the final wording and which round details may be used publicly.
4. 4. Coordinate the requestWe prepare the approved information and coordinate submission through the route confirmed for the request.
5. 5. Record follow-upWe log the submitted version and available correspondence. We share the current status and flag any response that needs your input.