Sources

Product facts come from official documentation, official download pages, published source repositories where a product is open source, and primary reporting. Where a fact cannot be traced to a primary source, we omit the field rather than estimate it.

Hands-on testing

We only describe hands-on testing where it actually took place, and we say what was tested, on what device, and when. Articles that are documentation-based research are not presented as device testing.

Specification fields

Wallet quick-facts modules — wallet type, custody model, supported platforms, hardware integration, open-source status and supported networks — are populated only from verified sources. Unknown fields are shown as “Not verified” or omitted entirely.

Scores and rankings

We publish no numeric security scores, trust scores, star ratings or “best wallet” lists. A score without a published methodology is a marketing device, not research.

Security claims

We avoid phrases such as unhackable, bank-grade, military-grade, completely anonymous or guaranteed safe. Where a specific audit, certification or disclosure exists, we name it, date it and link to it. Where it does not, we say nothing.

Update policy

Publication dates are never altered to create the appearance of freshness. Update dates reflect real edits. Articles older than two years carry a legacy notice so readers can judge whether technical steps still apply.

Disclosure

If commercial or affiliate relationships apply to a page, they are disclosed on that page. Commercial relationships never guarantee positive coverage and are not a condition of being reviewed.

Corrections

Factual errors are corrected in place with the update date changed. Substantive corrections are noted in the article. Report an issue through the contact page.