# The CROPS Guide: Review requests

**URL:** <https://forum.l2beat.com/t/the-crops-guide-review-requests/461>\
**Category:** Methodology & Framework\
**Created:** [November 4, 2026, 6:25am UTC](https://forum.l2beat.com/t/the-crops-guide-review-requests/461 "2026-11-04T06:25:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![adi](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@adi](https://forum.l2beat.com/u/adi)\
**Post date:** [November 4, 2026, 6:25am UTC](https://forum.l2beat.com/t/the-crops-guide-review-requests/461/1 "2026-11-04T06:25:48Z")

</div>

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

1. Create a new topic in the **Listing Requests** category of the forum.
2. Title it `[CROPS review request] Project Name`.
3. 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)

1. Project name
2. What does it do? A few sentences is enough.
3. Links to the website, documentation and source code repository
4. 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.

1. **Permissionless access:** Can anyone use it without needing permission?
2. **Exit without the team:** If the team, the frontend and every operator disappeared, could users still withdraw their funds?
3. **License:** Which license is the code released under?
4. **Verified contracts:** Are all deployed contracts verified against the published source code? If not, please verify them before you submit.
5. **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.
6. **Self-hosting:** Can anyone build and run the interface locally?
7. **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?

8. **Audits:** Which audits have been done? For each one, please link to the report.
9. **Anything else:** Is there anything else you’d like us to know?