Exchange comparison methodology

Data methodology

Scope of this page A score is useful only when its data, timestamp and limitations are clear.

Use this page to separate measured results from inference and to know when not to rely on a score.

Updated Aug 13, 2026 · 14:35

2 hours ago

Helpful when You need to understand a score

Always read the timestamp, sources and tool limitations with the result.

Main content

Three layers that must not be conflated

Fit score: fees, features, product range, usability and user-selected needs.
Data coverage: source count, freshness, completeness and consistency.
Legal status: only official announcements recorded by Coin4VN; never inferred from the other scores.

Current formula

Version comparison-v2.1 uses need-based fit and a separate confidence layer covering freshness, source quality, coverage and consistency. An exchange may fit a particular need while its profile still lacks data; the interface must show both facts separately.

Sources and change history

Coin4VN uses direct exchange data, app registries, market sources and manual editorial input. Fast-changing fields such as fees, KYC, products and app versions need their own checked-at timestamps. Where no complete connector exists, the field stays missing instead of being guessed.