Submit a Project
Project teams, builders, and community members can submit a crypto project for consideration. A submission helps with review, but does not guarantee a listing or a particular score.
Who can submit a crypto project?
Project founders, team members, developers, and community members can submit a crypto project for consideration. The person submitting should provide accurate information and, where possible, a contact who can answer questions about the project.
A submission is most useful when it comes from someone with direct knowledge of the project, but a community member can also send publicly verifiable details. Make clear whether you represent the project or are submitting on its behalf. Do not include private keys, seed phrases, passwords, or other confidential account information.
Send the submission to [contact email]. Include the project name in the subject line and organize the information so that each detail is easy to check. If a project has changed its name, website, or contracts, explain what changed and when. Clear, current details help prevent outdated or incorrect information from being associated with a project.
What information should a project submission include?
Include enough information to identify the project and check its public claims. A useful submission includes:
- Project name and official website.
- A short description of what the product does and who it is for.
- Supported blockchains, also called chains, and the project’s contract addresses on each one.
- Documentation, such as user guides, technical explanations, or developer resources.
- Audit details, including the auditor and the scope of any security review, if available.
- Official social media accounts and other channels the team uses to publish updates.
- A project contact for follow-up questions.
A smart contract is code that runs on a blockchain. Contract addresses should be matched to the correct chain; the same project can use different addresses on different chains. If the project has no audit or does not publish certain details, say so rather than implying that they exist. Never send passwords, seed phrases, or private keys.
How are project submissions reviewed?
Submissions are reviewed for clarity, relevance, and whether key details can be checked against public project materials. Review may include comparing the submitted name, website, supported chains, and contract addresses with project documentation and official communication. Audit claims should be assessed in context: an audit covers a stated scope and does not guarantee that a product is safe.
If important information is missing or unclear, the reviewer may need to ask for clarification. Providing documentation and working contact details can make it easier to resolve questions. A submission may also be declined if the project cannot be assessed with enough confidence or does not fit the site’s coverage.
A review is not a security certification, legal opinion, or endorsement. Crypto products can change after a review, and users should check current contract details and risks before interacting with any project.
Does submitting a project guarantee a listing or score?
No. Sending a project for review does not guarantee that it will receive a listing, and it does not guarantee any score or rating. A submission is a request for consideration, not a paid placement or a promise of a favorable assessment.
Whether a project is covered depends on the review and the information available to assess it. A project may not be included if key details cannot be checked, if the product falls outside the site’s coverage, or if the reviewer cannot reach a reasonable assessment. Providing complete information can support the review, but it cannot determine its outcome.
Scores, where used, are assessments rather than assurances of safety, returns, or future performance. They can reflect risks and limitations as well as useful features. Users should make their own checks, including verifying contract addresses on the relevant chain and understanding what permissions an app requests.
How can a project request a correction?
Send correction requests to [contact email]. Include the project name, the page or detail that needs changing, the corrected information, and evidence that supports the change. For contract updates, specify the blockchain and the old and new contract addresses so the change can be checked precisely.
If the correction concerns a project name, website, documentation, audit, or social account, provide the official source that verifies the update. Explain when the change took effect if timing matters. A correction request does not automatically change a listing; details may be checked before an update is made.
For security-sensitive information, do not email secret credentials or access keys. If a report involves a vulnerability or a risk to users, describe the issue without sharing information that could expose accounts or make an exploit easier. The project team should also use its own security-reporting channel when one is available.
Frequently asked questions
Who can submit a crypto project?
Project founders, team members, developers, and community members may submit a project for consideration. Include accurate details and, if possible, a contact who can answer follow-up questions.
What information should I include in a project submission?
Include the project name, official website, supported chains, contract addresses, documentation, audit information, and official social accounts. Explain what the project does and flag any details that may be difficult to verify publicly.
Does submitting a project guarantee a listing or score?
No. A submission is a request for review, not a promise that the project will be covered. It also does not guarantee a particular rating or score.
How can a project request a correction?
Send the project name, the details that need changing, and evidence supporting the correction to [contact email]. For contract or security-related changes, include the relevant chain and contract address.