Chad Trust runs on reviews. Every project's seal, its star rating, and its reputation come straight from what real users write. That makes a review the single most valuable thing you leave behind for the next person deciding whether a project is worth their time.
The good news: writing a strong one is not hard. It just takes a few minutes of actually saying what you experienced instead of dropping a "nice project 👍" and moving on. Follow the steps below and you will write a review that gets approved, helps the community, and gives the project real signal.
What every review needs
No matter which project you are reviewing, two things are always required:
- A star rating, from 1 to 5.
- A written review, at least 100 characters.
On top of that, most projects add their own survey questions, and these change from project to project. A trading app might ask which platform you use and how experienced you are. A DeFi protocol might ask something completely different. The questions vary, but the rating and the write-up never do. Those are your review.
Step 1: Set the star rating, and mean it
Your rating is the headline. Everything else exists to explain it. Use this scale to keep it honest:
| Stars | What it means |
|---|---|
| 5 | Excellent. Does what it promises, few or no real gaps. Recommend without hesitation. |
| 4 | Strong, with one clear thing holding it back. Genuinely useful today. |
| 3 | Mixed. Real value, real problems. Proceed with eyes open. |
| 2 | Significant issues. Hard to recommend as-is. |
| 1 | Broken, misleading, or not worth touching. |
The one rule that matters: the rating has to match the words. A glowing paragraph with a 2-star rating reads as noise, and so does a harsh write-up with 5 stars. Pick the number that fits your actual experience, then let the rest of the review back it up.
Step 2: Write the review
The written review is the heart of it. The strongest ones share four traits:
- Specific. Name the features and use real details. "It works well" is weak. "Setup took under a minute and the numbers matched what I actually earned" is a review.
- First-hand. Describe what you did with it, not what the landing page claims.
- Balanced. Say what worked and what did not. A review with zero criticism is not more positive, it is less trustworthy.
- Honest about the rating. Add one sentence on why it is a 4 and not a 5. That single line does more work than everything else.
A simple structure that always works:
- One thing that stood out (the best part).
- One honest gap or friction point.
- Why the rating fits.
Here is the difference in practice:
Weak: "Good project, works well, would recommend."
Strong: "I used it for about two weeks. The standout is how fast it is to set up a position, under a minute with no hoops. The one real gap is that it doesn't show fees before you confirm, so my first action cost more than I expected. Solid overall, and I'd keep using it, which is why it's a 4 and not a 5."
Same length, completely different value. The second one could only come from someone who actually used the product.
Step 3: Answer the survey questions with substance
The per-project questions are where a lot of reviews fall apart. Two kinds show up:
Multiple-choice questions (platform, experience level, "how likely are you to recommend this, 0 to 5"). Just be accurate. These take two seconds.
Open-ended questions ("What was the most valuable part?", "What would you improve?"). This is where effort separates a real review from a farmed one. Do not answer in one word. One or two concrete sentences is enough, as long as they describe your experience and could not be copy-pasted onto any other project.
Before you submit: the checklist
Run through this and you are done:
- Star rating set, and it matches what I wrote
- Review is specific and first-hand, not generic hype
- I named at least one real gap or limitation
- Open-ended questions answered in full sentences
- No personal info (never include wallet seed phrases, private keys, or your address)
What gets a review rejected
Chad Trust reviews are manually approved, and we are strict on purpose. A weak seal helps no one. These get rejected:
- One-liners. "gm good project" is not a review.
- Farmed or duplicate submissions. Multiple accounts from one person, copy-paste answers, and shared-IP clusters get flagged and removed. Not worth the risk.
- Ratings that contradict the write-up.
- Generic hype. If your review would fit any project, it fits none.
Why the effort pays off
A good review is not charity. It is leverage:
- For airdrop campaigns, quality reviews are what qualify you. Low-effort ones get tossed, which means no reward and wasted time.
- For projects, your review is direct feedback from a real user, often more useful than any survey they could run themselves.
- For the community, the seal is only as honest as the reviews behind it. Every specific, balanced review makes Chad Trust worth something.
Two minutes of real writing beats ten seconds of filler, every time. Say what you used, what worked, what did not, and why the rating fits. That is the whole game.
Ready to leave one that counts? Browse the projects on Chad Trust and put this guide to work.