Submit a Crypto Project for Review

Project teams, founders, and authorized representatives can submit a crypto project for consideration. If you are submitting on someone else’s behalf, say who you represent and include a way to verify that connection.

A useful submission makes it possible to understand what the project does and check its key claims. Send the information in one message to [contact email], using the project name as the subject. Include current details and flag anything that is still in development. Do not send passwords, seed phrases, private keys, or other credentials.

You can submit a decentralized application, protocol, wallet, game, or another crypto product. A submission is an invitation to review the project, not a promise that it will be published. We may need to ask for clarification if important details are missing or unclear.

Include enough detail for a reader to identify the project, find its official resources, and understand where it operates. A clear submission should cover:

• Project name and website: Use the current name and official site.
• What it does: Describe the product, its main use, and whether it is live or still being built.
• Chains and contracts: Name each supported blockchain and provide the relevant contract addresses. Identify which function each address serves.
• Documentation: Include user guides, technical documentation, token details, and any published risk disclosures.
• Audits: Name the auditor, identify the contracts and versions covered, and note any limitations or unresolved findings. If there is no audit, say so.
• Official social accounts: List the project’s social channels and make clear which ones are official.

Keep the information consistent across your submission and public project materials. If a feature, chain, or contract is planned rather than live, label it clearly so readers do not mistake it for an available product.

We review submitted details for clarity and consistency, and may compare them with public project materials. Reviewers can consider what the product does, which chains and contracts it uses, the quality of its documentation, available security information, and risks that could affect users. Providing complete, verifiable details helps make the review more useful; it does not remove the risks of using a crypto product.

A submission does not guarantee a listing, publication date, score, or ranking. A project may not be listed, and a published assessment may not match the score or wording a team prefers. An audit is one factor to consider, not a guarantee that contracts are safe or that a project will perform as expected.

If we need more information to assess a material point, we may contact the submitter. Make sure your contact details work and tell us if the project changes substantially while a review is being considered.

For an update or correction, email [contact email]. State the project name, identify the exact listing detail that needs attention, and explain what should change. Include supporting evidence, such as an official announcement, current documentation, or the correct contract address and chain.

If the correction concerns a security issue, a compromised account, or a contract that has been replaced, explain the potential impact and when the change took effect. Do not include confidential credentials or private keys. For a disagreement about an assessment, point to the specific claim and provide evidence that can be checked; a request does not guarantee that a score or conclusion will change.

Please send major project changes as soon as practical. Clear, verifiable updates help keep project information accurate, but corrections are still reviewed before they are applied.