Independent public-evidence reviewNo personal financial advice
Candid LedgerPut the evidence on the record.

Control memorandum

Wallet methodology

Trace user control from key creation to recovery and signing.

Publication gate

Each file must carry ten distinct claim chains and at least four declared decision scenarios; identity, control and exit fields record their evidence and limitations beside the conclusion.

  1. 01

    Key generation and control

    Establish where keys are created, who can access them, whether remote services participate and which product version was examined.

    Evidence: Technical documentation, code or release records where available, and controlled device-level observations
    Completion gate: Control claims are tied to a specific application, platform and version.
    Open
  2. 02

    Recovery and backup

    Map every supported recovery route, the information each route requires and which loss states are irreversible.

    Evidence: Official recovery documentation and safe tests using disposable accounts with no real assets
    Completion gate: The report distinguishes provider-assisted recovery from user-held recovery material.
    Open
  3. 03

    Signing and permission safety

    Examine what the interface shows before approval, how permissions are reviewed or revoked and which transaction details may remain opaque.

    Evidence: Versioned interface tests, protocol documentation and clearly scoped security research
    Completion gate: Signing observations identify network, transaction type, version and known blind spots.
    Open
  4. 04

    Code, audits and release provenance

    Trace official distribution, update signing, public source coverage and the scope and age of security assessments without treating an audit as a guarantee.

    Evidence: Official stores, signed releases, repositories, audit reports and remediation records
    Completion gate: Provenance is verified and each audit is described by date, scope and limitations.
    Open
  5. 05

    Networks, privacy and support

    Record supported networks, default data flows, optional telemetry, third-party infrastructure and the practical support boundary.

    Evidence: Network documentation, privacy disclosures, controlled traffic observations and support policies
    Completion gate: Claims do not overstate anonymity, compatibility or the provider's ability to reverse transactions.
    Open