The CROPS Guide is a curated list of projects that meet the CROPS values: censorship resistance, open source, privacy and security. If you think a project belongs on the list, you can ask our research team to review it.
Note: We only review protocols that are already live on mainnet.
How to submit
- Create a new topic in the Listing Requests category of the forum.
- Title it
[CROPS review request] Project Name. - Copy the questions below into the post, answer the ones that apply, and publish.
What happens next
A review can take a couple of days after your request is posted. When it’s done, we’ll get back to you with our conclusion. If a project rates red on any property, we may stop the review there and not assess the rest.
Questions
The basics (required)
- Project name
- What does it do? A few sentences is enough.
- Links to the website, documentation and source code repository
- Which chain(s) is it deployed on, and at which contract address(es)?
The details (optional, but helpful)
We can find this information ourselves from the sources you provide, but your answers make the review faster.
- Permissionless access: Can anyone use it without needing permission?
- Exit without the team: If the team, the frontend and every operator disappeared, could users still withdraw their funds?
- License: Which license is the code released under?
- Verified contracts: Are all deployed contracts verified against the published source code? If not, please verify them before you submit.
- Reproducible builds: If the project uses a ZK, TEE or Wasm program, can its hash be reproduced from the source code? Please link to the source.
- Self-hosting: Can anyone build and run the interface locally?
- Privacy: Does the project make any privacy claims? If so:
- What exactly is hidden?
- Can anyone deanonymize a user?
- Is privacy on by default, or opt-in?
- Audits: Which audits have been done? For each one, please link to the report.
- Anything else: Is there anything else you’d like us to know?