Bank crypto activity leaderboard

Methodology

• Counts reflect initiatives we have verified, not a full census; absence means not yet reviewed, not “not active”. Coverage is strongest for the EU, US, UK, Hong Kong, Singapore and the UAE.
• Source data: only the adoption tracker (content/tracker/initiatives.json, institutions, sources). Every initiative cites dated sources; tracker sources are re-fetched and quote-checked before each deploy.
• Verified = initiatives naming the institution as a participant. Joint initiatives count once for each named participant (7 of 97 initiatives are joint, so the per-institution counts add up to 147).
• Stage = the most advanced verified technical or commercial status: Live (restricted or commercial), Pilot, Developing / partnership, Announced. If neither is confirmed but a regulator authorisation or MiCA Art. 60 notification exists, it counts as regulatory record only. Regulatory status is also counted on its own (“Authorised / notified”); a MiCA notification is not an authorisation.
• Order: verified initiatives, then live initiatives, then jurisdictions — institutions equal on all three share a rank. Ties are listed by latest verified activity, then name.
• Jurisdictions = distinct markets mapped from each initiative’s stated target market, as on jurisdiction pages. An EU member state also counts the EU-wide market; “global” scopes are not mapped.
• Latest verified = newest dated status event in an initiative’s history (each event cites its source), else its announcement date.

What this is not

• Not a measure of quality, size, safety or market share, and not a recommendation.
• Not weighted: for a weighted view of verified statuses see the readiness scorecards (method).
• Missing an initiative or a bank? Send the primary source via contact; errors go to corrections.

Open data: /api/rankings.json (CC BY 4.0) · all datasets on Data.