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

Operator ledger

Exchange methodology

Trace responsibility from legal entity to asset exit.

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

    Identity and jurisdiction

    Fix the exact product, contracting entity, market, licences claimed and legal documents governing the user relationship.

    Evidence: Company and regulator registers, binding terms, dated entity disclosures and right-of-reply records
    Completion gate: The operator and applicable market are supported without relying on the brand name alone.
    Open
  2. 02

    Custody and account security

    Map who controls customer assets, how access is authenticated, what segregation or protection is claimed and which facts are independently testable.

    Evidence: Custody terms, security documentation, audited statements where relevant and reproducible account-control tests
    Completion gate: Custody language, operational behaviour and unresolved contradictions are stated together.
    Open
  3. 03

    Fees, spreads and execution

    Record realistic transaction paths rather than a single advertised fee, distinguishing fees from price spread and network cost.

    Evidence: Timestamped schedules, quotes, receipts, order details and repeatable scenarios for the defined market
    Completion gate: The scenario, amount, asset pair, payment route, time and limitations are reproducible.
    Open
  4. 04

    Funding, withdrawals and restrictions

    Test entry and exit routes, limits, holds, verification steps and closure conditions without exposing credentials or creating unsafe balances.

    Evidence: Binding rules, interface captures, controlled test logs and documented support exchanges
    Completion gate: A reader can see the tested route, result, timing and what was not tested.
    Open
  5. 05

    Reliability, support and incident history

    Separate first-party status notices, independently established incidents and unverified user reports, then record remediation and present relevance.

    Evidence: Primary incident notices, regulator or court records, archived status data and attributable responses
    Completion gate: Dates, affected product, impact, resolution and uncertainty are explicit.
    Open