Editorial policy
What decides a published order, what does not, and how to check both.
Revised 2026-09-14.
How ChainChoice earns money
Some outbound links carry a provider's referral parameter. When a reader signs up through one and the provider confirms it, Simi Ventures GmbH, the operator, may receive a commission.
Commission is not an input to any score or order. The modules that compute an order cannot import partner, payout or click data, and the build fails if one can.
There are no paid placements, sponsored scores or paid listings.
How an order is computed
Each published score is a weighted sum of five dimensions: Availability, Published criteria, Friction, Trust record and Measured data. Their base weights add up to 86 points.
Profile match is computed and shown in breakdowns but carries no weight.
Every dimension score, weight and constant, and the formula, is published in /data/rankings.json. Every build rebuilds each score from that file alone and fails if one does not match.
The methodology changelog lists each published version with its date and changes. The current version is 2026.09.15, published 2026-09-16.
Where the evidence comes from
Where a score has quoted evidence, the quote and its source URL are published per category, for example in /data/evidence/exchange.json. Where a category has a verified research payload, the build fails when a shipped criterion score differs from it.
406 of the 983 published scores have no quoted source behind them yet.
Each category states a re-read interval of 45 days. The build fails when more than 3 categories are over 7 days past it.
Conflicts of interest
The people who publish ChainChoice are the managing directors of Simi Ventures GmbH, the company that receives any referral commission. That conflict is why commission is kept out of the ranking code by a build check rather than by a promise.
Personal holdings of the people on the roster are not published.
The roster is on /methodology.
Data and privacy
What is collected, where it is stored and which processors receive it is set out in the privacy policy at /privacy.
Accepting analytics sets a first-party cookie, cc_anon_id, holding a random identifier with a 30-day rolling lifetime. Declining sets no such cookie.
Corrections and contact
To report an error, email mathias@cryptopaymentfinder.com.
Published corrections are listed at /methodology/corrections with what was wrong, what changed and how it was caught. Entries in the log today: 33.