Public-evidence reviewsSeven beginner guides reviewedRead the safety note
plainblockclear questions before crypto decisions
Community reports

What makes a useful experience report?

A first-hand account can suggest a problem to test. It cannot prove regulation, solvency, security or the experience of all users.

guide
1

What should be included?

Name the exact product, country, approximate date, relationship and observable sequence. Separate what happened from what you think caused it.

2

What must stay out?

No recovery phrases, keys, passwords, codes, complete wallet addresses, identity documents, doxxing, threats, spam or unsupported criminal allegations.

3

How would moderation work?

If community submissions open in a future edition, they would move through email verification and a pending queue before approval or rejection. Positive and negative reports would receive the same rules; publication would be a separate recorded action.

4

Does email verification prove the story?

No. It only shows control of an inbox. Private email would not be published, and public links would use ugc and nofollow attributes.

5

What works now?

This edition does not accept community comments. There are no comment counts or community averages.