Public-evidence reviewsSeven beginner guides reviewedRead the safety note
plainblockclear questions before crypto decisions
User-controlled keys

How we check a wallet

Follow the key and the signing path.

Publication gate

Ten practical responsibility answers and four decision journeys are the minimum; identity, control and exit fields record their evidence and limitations beside the conclusion.

  1. 1

    Name the exact app

    Platform, version and recovery type matter.

    Evidence to add: Official app, platform, version, network and release records
    Complete when: The exact software and research period are fixed.
    Standard
  2. 2

    Protect the recovery route

    Understand who can restore or take control.

    Evidence to add: Technical documents and safe observations of key creation and storage
    Complete when: Who can access keys and which services participate are supported.
    Standard
  3. 3

    Read before signing

    Permissions and routes can be irreversible.

    Evidence to add: Disposable-account signing and recovery checks with no real assets
    Complete when: Warnings, permissions, recovery dependencies and irreversible failures are explicit.
    Standard
  4. 4

    Verify the update

    Repository, binary and official channel differ.

    Evidence to add: Official distribution, repository, signed release, audit and remediation records
    Complete when: Software origin and each audit's date, scope and limits are clear.
    Standard