How Skrumble scores platforms
Every score on this site is the output of a documented test. We don't take payment for placement. We don't change scores in exchange for affiliate deals. This page documents how we do it.
Our principles
- Receipts over vibes. Every claim ties to a tested transaction, a dated screenshot, or a primary-source citation.
- Dated transparency. Every review carries a "last tested" date. Anything older than 6 months is flagged.
- Affiliate-blind scoring. Commission rates have zero weight in our scoring. The order in which exchanges appear is determined by score, not by what they pay us.
- Independent. No platform pre-approves what we publish. No paid placements. Read how we make money.
What we test
For every platform we publish a verdict on, we run a hands-on test. That includes:
- Account creation, KYC, and time-to-first-trade.
- A real deposit (typically the platform's minimum), priced and timed.
- A spot buy at a stated USD amount — actual cost vs market mid recorded.
- A withdrawal of the asset (when fees and timing permit) — actual fee and arrival time recorded.
- Customer support: at least one real ticket, time-to-first-response and time-to-resolution captured.
Scoring rubrics by platform type
Different platforms get different weights. We publish each rubric publicly:
- → How we score crypto exchanges
5 pillars: Security & Trust (30%), Fees (25%), Asset Variety (20%), Ease of Use & Features (15%), Customer Support (10%).
- → How we score crypto bridges
5 pillars: Security & Audits (35%), Transaction Speed (20%), Fees (20%), Chains & Tokens Coverage (15%), Reliability (10%).
When scores change
Scores are re-evaluated quarterly, or sooner when a platform publishes a material change (security incident, fee restructure, country restriction, regulatory action). Every score change is recorded with a date and a note of what triggered it.
What you can hold us to
Spotted a score that looks wrong, a number that doesn't match the platform's docs, or a fee we haven't updated? Tell us. Corrections get logged at the bottom of the affected review with a date.