Four Archetypes of Stablecoin Regulation
A Plexo decision lens for separating an implemented rulebook, an entry-stage framework, a restricted perimeter, and an unresolved policy perimeter.
By Anton Titov, Founder · Plexo Institute
Four analytical states for framing a regulatory due diligence question. They are not country scores, legal conclusions, or forecasts.
A regulatory label is only useful when it leads to the next primary-source question. It is not a substitute for the answer.
Reading Guide
Four moves that turn jurisdictional complexity into a five-action operator decision.
Most stablecoin regulation analysis starts with country labels. This framework starts with a narrower question: what is the legal and supervisory status of the named activity inside the relevant regulatory perimeter today?
The labels — proactive, permissive, restrictive and reactive — are Plexo shorthand for four observable regulatory situations. They help an operator ask the right next question: is there an implemented rulebook, an entry-stage pathway, an express restriction, or unresolved treatment?
They do not describe an entire country, predict market outcomes, or establish whether a particular issuer, service or token is permitted. Those conclusions require the current primary text and, where appropriate, local counsel.
MiCA is an EU regulation with category-specific application and transitional conditions. The GENIUS Act is enacted US law with a statutory implementation timeline. A Bank of England consultation is a proposal, not an operative authorisation route. These are different legal states even where they share policy concerns around issuer, reserves, redemption and supervision.
The category therefore begins with the document’s legal status and scope, not with an assumption about a market’s openness or the behaviour of its participants.
Consultations, sandbox notices, rulemaking proposals and licensing decisions can be useful monitoring signals. They do not establish a future rule, a timetable, or eligibility. FX conditions and adoption data may be relevant context, but cannot independently prove why a regulator acted or what it will do next.
An operator should record the source date, authority, instrument, affected activity and operative date, then refresh the record when any one of those changes.
First identify the proposed activity: issuance, custody, exchange, payment execution, redemption, or technology provision. Then identify the issuer, client type, token, place of establishment, customer location and controlling authority. Only after that can the four labels help organise the primary-source check.
Different authorities and legal categories can coexist within one country. The relevant unit is the defined regulatory perimeter, not a country-wide label.
Why Archetypes
The framework is deliberately coarse: it helps organise research, but never replaces a jurisdiction-by-jurisdiction legal check.
A stablecoin rule can apply differently to an issuer, a service provider, a token holder and a technology vendor. The four labels prevent an operator from treating an isolated regulatory headline as a complete operating answer.
The four labels are intentionally coarse: they distinguish a current implemented framework, an entry-stage framework, an express restriction and an unresolved perimeter. They are a starting point for a research brief, not a validated predictive model.
If a situation spans more than one label, preserve that ambiguity and create separate source packets rather than forcing a classification.
The Four Archetypes
Each archetype describes the evidence an operator has at hand, not the quality of a country or its market.
Each archetype is defined by the observable legal posture for a named activity: implemented and supervised, entry-stage or conditional, expressly restricted, or unresolved. A specific regime can move between these states as instruments take effect or guidance changes.
Four Evidence States For A Regulatory Perimeter
A research lens: classify the available primary-source evidence before making a market or legal claim.
Express restriction
Read the rule, exemptions, territorial reach and affected activity exactly.
do not infer market behaviourImplemented framework
A defined rulebook may apply; eligibility and operative date still need confirmation.
test category and registerUnresolved treatment
The available material does not answer the named payment question.
obtain authority evidenceConditional pathway
A consultation, sandbox or limited route may exist for a defined activity.
confirm scope and status| Archetype | What it means for research | Required verification |
|---|---|---|
Proactive | An implemented framework addresses the named activity through defined permissions, duties or supervision. | Confirm scope, operative date, transition rule and regulator register. |
Permissive | A conditional route, consultation, sandbox or limited framework may exist for the named activity. | Confirm whether the route is open, who can use it and whether it authorises the proposed product. |
Restrictive | The current rule or enforcement posture blocks, limits or conditions a relevant activity. | Read the exact prohibition, its exemptions, territorial reach and latest official notice. |
Reactive | The available material does not resolve how the named payment activity is treated. | Do not infer permission or prohibition; obtain a dated authority source and local advice. |
An implemented framework may define a licence, reserve standard, disclosure duty or supervisory authority. It does not by itself prove that a particular operator or token qualifies. MiCA and the GENIUS Act, for example, use different statutory categories and implementation mechanics.
The next step is to test the proposed product against the precise category and its current transitional or implementing conditions.
A sandbox, consultation or staged authorisation can be useful evidence that an authority is considering a perimeter. It may apply only to a limited activity, participant set or period. It must not be represented as a generally available licence or as a claim that one market is more welcoming than another.
Use the authority’s current page and any published register to establish what is actually open.
An apparent restriction can apply to a bank relationship, consumer payment, exchange service, issuer, token class or cross-border transaction — with different exemptions. Market-adoption data cannot establish the cause or effect of an enforcement rule.
Treat outside-market behaviour as an empirical question requiring its own evidence; do not infer it from a restriction headline.
A crypto-asset rulebook can leave payment activity unresolved. That uncertainty is not permission, and it is not evidence that the framework was designed only for trading. The correct response is to identify the controlling authority, the most recent instrument and the activity it covers.
Where no authoritative answer is available, mark the route as unresolved rather than turning uncertainty into a market claim.
How Archetypes Shift
A change in source status changes the diligence file; it does not create a timetable or market forecast.
A framework can change when a law enters into force, a consultation becomes a rule, a register opens, or an authority issues new guidance. The event is relevant only to the scope stated in that source.
| Observed change | What it may mean | What to verify |
|---|---|---|
Proposal or consultation | An authority is considering a rule or seeking evidence. | Whether it is operative, which activity it covers and the closing or implementation date. |
New rule or register | A defined pathway may have become available. | Eligibility, transitional conditions, limits and the current regulator register. |
Enforcement or guidance update | A prior interpretation may have narrowed or changed. | The exact notice, legal basis, territorial reach and effective date. |
Regulatory systems do not move through a universal maturity ladder. A restriction can remain, be narrowed, be replaced, or coexist with another route. Economic conditions, industry demand and supervisory capacity can be relevant context, but public evidence rarely isolates a single causal driver for a regulatory decision.
Use a dated sequence of primary documents for each perimeter; do not borrow a time horizon or predicted direction from another jurisdiction.
The Transition Pathway
The labels are a checklist of possible evidence states, not a path every regulator follows.
For a single activity, a record can move between restrictive, unresolved, conditional and implemented states. The record should always preserve the source date and the reason for the classification.
How A Regulatory Record Changes
A source-status checklist, not a maturity ladder or forecast.
- 01
Restrictive
Restriction is documented
Record the exact rule, exemption and activity it covers.
- 02
Reactive
Treatment remains unresolved
Identify the authority and preserve uncertainty until evidence resolves it.
- 03
Permissive
A conditional route appears
Verify whether it is open, who may use it and what it authorises.
- 04
Proactive
A framework becomes operative
Test the category, operative date, transition terms and register.
Restriction: record the exact rule, exemption and affected activity.
Unresolved: identify the authority and keep the question open.
Conditional: verify the pathway, participation limits and current status.
Implemented: test eligibility, operative date and supervisory register.
A law, consultation or transition provision may contain a specific date. Outside those documents, this framework supplies no predicted timetable. A projected regulatory window should be labelled as an internal scenario and kept separate from the legal-status record.
How Operators Decide
The framework becomes useful when it translates a jurisdictional map into a concrete market-entry action.
An operator evaluating a jurisdiction begins with a defined activity and primary-source packet. The label helps determine which missing evidence to obtain; it does not determine a market-entry action on its own.
Operators Need Different Evidence In Each State
The same product needs a current primary-source packet before a market-entry decision.
First control question
What does the current authority source say about this activity?
Test category eligibility
Confirm the operative rule, transition conditions, regulator register and local operating constraints.
Confirm the pathway
Check whether the programme is open, who can participate and whether the activity is in scope.
Do not infer permission
Obtain a dated authority source and qualified local advice before treating the route as available.
Do not launch the affected activity
Read scope and exemptions precisely; monitor future official changes without forecasting them.
| Current evidence state | Responsible next action |
|---|---|
Implemented framework | Test category eligibility, transitional terms, register status and local operating constraints. |
Conditional pathway | Confirm whether the programme is open and whether the proposed activity is inside its mandate. |
Unresolved treatment | Obtain a dated authority source and legal advice before treating the route as available. |
Express restriction | Do not launch the affected activity; analyse scope, exemptions and future changes only as monitoring. |
A consultation, pilot announcement, register update or enforcement notice can trigger a refresh of the source packet. It may justify research or a regulator conversation, but it does not establish a future licence, a market-entry window or future cost.
Maintain the underlying source record and re-check it before any public claim or product decision.
A country can contain different authorities, activity categories and geographic perimeters. A rule about issuing a payment stablecoin does not automatically resolve exchange, custody, payments, marketing or a separate local perimeter.
This is why the record must name the regulator and activity rather than applying one country-wide label.
Why the Archetype Matters More Than the Rule
The archetype is useful only when it leads back to the underlying rule, register or official notice.
The label is not more important than the rule. It is useful because it tells an operator which legal question remains unanswered: operative scope, entry conditions, restriction language or authority position. It must be discarded if the primary material points to a different conclusion.
It cannot establish where capital, users or infrastructure will concentrate. Those are separate empirical questions requiring named, dated evidence.
Implemented means verify eligibility. Conditional means verify the route is genuinely open. Unresolved means obtain authority evidence before proceeding. Restrictive means do not launch the affected activity.
This collapses the research workflow, not the jurisdiction’s legal complexity.
Counter-Arguments & Limitations
The framework is useful because it is coarse, but the same simplification creates the strongest objections.
Two objections matter before operators use the framework as a market-entry map: the four buckets can hide real jurisdictional variation, and archetype does not replace tax, substance, or banking-access analysis.
The argument: MiCA's category-specific obligations, the GENIUS Act's statutory issuer categories and a UK systemic-stablecoin proposal are materially different. A four-label shorthand can hide that difference.
Response: it should never be used as a legal taxonomy. The label exists only to route the reader to the document-level review; the source packet retains the distinctions that decide eligibility and implementation.
The argument: a real operating decision also depends on tax, banking access, capital controls, data, employment, counterparties and commercial demand.
Response: correct. This framework does not rank locations or calculate an operating decision. It isolates the regulatory-status question, which is one required input alongside those other facts.
About the Author
About This Framework
Scope, disclosure, and method.
Published by Plexo Institute. This is a dated analytical lens for organising stablecoin-regulation research around a defined activity and regulatory perimeter. It does not classify countries conclusively, rank markets or predict market outcomes.
Plexo uses the lens to structure research questions. Operators must confirm specific pathways against current primary sources and, where needed, qualified local counsel. The framework guides what to verify; it does not replace the rule that governs the activity.
Classification criteria: the legal status and scope of an authoritative document for a named activity — implemented framework, conditional route, restriction or unresolved treatment. The labels are analytical, non-exhaustive and may coexist across activities or authorities.
Source material starts with official legal text, regulator notices and registers. FATF, IMF and market-research material can add context but cannot establish permission, prohibition or future regulatory action. A country-specific conclusion requires a dated regulator packet.
Continue Reading
G20 Stablecoin Regulation: Where the World Stands - a dated comparison method for selected primary-source regimes.
When Dollars Stop - a separate analysis of FX conditions and payment constraints.
Kenya's Stablecoin Economy - a country-specific analysis that requires its own dated source review.
References
Chainalysis, Sub-Saharan Africa Crypto Adoption 2024.
FATF, Updated Guidance for a Risk-Based Approach to Virtual Assets and VASPs, 2021.
EU, MiCA Regulation (EU) 2023/1114, Official Journal.
US Congress, GENIUS Act, Public Law 119-27, July 18, 2025.
UAE VARA, Virtual Asset Rulebooks; ADGM FSRA, Fiat-Referenced Token framework materials.
MAS, Payment Services Act - SCS Framework.
ESMA, Statement on the End of Transitional Periods under MiCA, April 17, 2026.
IMF, Article IV Consultation Reports, 2024-2026 series.
Central Bank of Nigeria, Guidelines on Operations of Bank Accounts for Virtual Asset Service Providers, December 22, 2023.
Hong Kong Monetary Authority, Granting of stablecoin issuer licences, April 10, 2026.
References
10 references- Sub-Saharan Africa Crypto Adoption 2024 — Chainalysis
- Updated Guidance for a Risk-Based Approach to Virtual Assets and VASPs — FATF
- MiCA Regulation (EU) 2023/1114 — European Union
- GENIUS Act, Public Law 119-27 — US Congress
- Virtual Asset Rulebooks and ADGM Fiat-Referenced Token Framework — UAE VARA; ADGM FSRA
- Payment Services Act - SCS Framework — Monetary Authority of Singapore
- Statement on the End of Transitional Periods under MiCA — ESMA
- Article IV Consultation Reports — IMF
- Guidelines on Operations of Bank Accounts for Virtual Asset Service Providers — Central Bank of Nigeria
- Granting of stablecoin issuer licences — Hong Kong Monetary Authority