Public-evidence reviewsSeven beginner guides reviewedRead the safety note
plainblockclear questions before crypto decisions
How we check

Start with responsibility, then ask for proof.

The method changes when the product changes. The honesty rule does not.

1

Name the exact product

Write down the product, country or market, version, responsible party and research dates.

2

Build a ten-question responsibility map

Separate scope, control, security, law, cost, access, operation, privacy, support and change into ten answers a beginner can act on.

3

Match evidence to each question

Choose the primary record, binding document or safe observation that could support the answer.

4

Run repeatable checks

Record the country, account, version, device, asset, amount, time, steps, saved output and limits without exposing credentials or putting real assets at unnecessary risk.

5

Challenge the draft

Check contradictions and conflicts, seek a relevant reply and require an accountable second review for material conclusions.

6

Publish limits beside answers

Only supported, dated conclusions can leave draft, and every material change needs a correction or update record.

For company-controlled accountsHow we check exchangesCompany, custody, cost and exit →For user-controlled keysHow we check walletsKeys, signing, recovery and software →