Cross-Border RWA Regulatory Challenges: A Guide to Global Compliance with Blockmaze Layer-0
Cross-border RWA regulatory challenges are the conflicts that arise when one tokenized real-world asset is issued, sold or traded under more than one country's rules: different classifications of the same token, licences that do not travel, and resale restrictions that follow the token abroad. In October 2025 the FSB found cross-border cooperation on crypto-assets fragmented, inconsistent and insufficient.
TL;DR — Key Takeaways
- ✓Classification decides the rulebook: MiCA does not apply to crypto-assets that qualify as financial instruments, and SEC staff said on January 28, 2026 that tokenization does not change how US securities law applies.
- ✓EU in 2026: The MiCA transitional period ended EU-wide on 1 July 2026. The DLT Pilot Regime cap is EUR 6 billion; a December 2025 proposal would raise it to EUR 100 billion.
- ✓Passports are partial: MiCA Article 65 lets an authorised CASP serve another member state from the 15th calendar day after notification, but only for crypto-asset services, not tokenized securities.
- ✓Rules travel with the token: US Rule 144 holding periods of six months or one year apply to restricted securities wherever the next buyer sits.
- ✓Uneven progress: The FSB counted 11 jurisdictions (39%) in its review with a finalised crypto-asset framework addressing financial stability, as of August 2025.

Why is cross-border RWA tokenization hard to do compliantly?
Because each jurisdiction classifies the same token on its own terms and licenses issuers, venues and service providers separately. The FSB's October 2025 peer review found that only 11 jurisdictions in its review (39%) had finalised a crypto-asset framework that addresses financial stability, with data as of August 2025.
A token is borderless; its legal status is not. An issuer that sells a tokenized fund unit to investors in three countries has to satisfy three offering regimes, use venues licensed in each, and keep transfer rules that respect each country's resale limits. If the basics of tokenization are new to you, start with our institutional guide to RWA tokenization.
The Financial Stability Board's thematic review counted the rest of the field: eight jurisdictions (29%) were consulting on or finalising frameworks, three (11%) had frameworks that partly address financial stability risks, and six (21%) were at an early stage. It also found that supervision and enforcement lag behind rule-writing.
“Cross-border cooperation and coordination is fragmented, inconsistent, and insufficient to address the global nature of crypto-asset markets.”
— Financial Stability Board, Thematic Review on FSB Global Regulatory Framework for Crypto-asset Activities, October 16, 2025
Is a tokenized RWA a security in every jurisdiction?
Not automatically: classification depends on the rights the token gives its holder, and that answer decides which rulebook applies. In the EU, MiCA states that it does not apply to crypto-assets that qualify as financial instruments. In the US, SEC staff said in January 2026 that the issuance format does not change how securities law applies.
MiCA Article 2(4) lists the exclusions: financial instruments, deposits, funds other than e-money tokens, securitisation positions, insurance and pension products, among others. A token that carries a claim on a bond, share or fund unit is therefore regulated under MiFID II and related EU securities law, not under MiCA.
The SEC staff statement of January 28, 2026 adds a distinction that matters across borders. It separates issuer-sponsored tokenized securities from those tokenized by unaffiliated third parties, which are either custodial (the token evidences an interest in a security held in custody) or synthetic (the third party issues its own security tracking the underlying). A synthetic token on a foreign venue can be a different instrument, with a different issuer, from the security it tracks.
Classification also drives the venue question. Our guide to RWA listing compliance for exchanges covers what a venue must check before it admits a token from a foreign issuer.
What changed for EU tokenization in 2026?
The MiCA transitional period ended across the EU on 1 July 2026, so firms without a MiCA licence can no longer provide crypto-asset services to EU clients. Tokenized securities stay outside MiCA, and the DLT Pilot Regime still caps DLT infrastructures at EUR 6 billion unless the December 2025 reform is adopted.
ESMA's statement of 17 April 2026 set the expectation that any unauthorised crypto-asset service provider (CASP) would have implemented its wind-down plan by 1 July 2026. Some member states ended their national grandfathering earlier. Our explainer on what happened after the MiCA transitional period ended covers the client-migration rules.
“After this date, any entity providing crypto-asset services to EU clients without a MiCA licence will be in breach of EU law and must cease offering such services.”
— ESMA, Statement on the End of Transitional Periods under MiCA, ESMA75-113276571-1679, 17 April 2026
For tokenized securities, the binding constraint is the DLT Pilot Regime, Regulation (EU) 2022/858. On 4 December 2025 the Commission proposed, as part of its Market Integration and Supervision Package, to remove product-specific limits and raise the aggregate cap. A Council Presidency discussion paper of February 2026 summarises the numbers:
| Limit | Current regime | December 2025 proposal (regular regime) |
|---|---|---|
| Aggregate cap at admission of a new DLT financial instrument | EUR 6 billion | EUR 100 billion, calculated group-wide |
| Transition-strategy trigger | EUR 9 billion | EUR 150 billion |
| Eligible shares | Market capitalisation under EUR 500 million | All financial instruments |
| Eligible bonds | Issue size under EUR 1 billion | All financial instruments |
| Eligible UCITS units | Assets under management under EUR 500 million | All financial instruments |
The proposal also adds a simplified regime capped at EUR 10 billion. Until an amending regulation is published in the Official Journal, the current limits apply. Our guide to the EU DLT Pilot Regime reform tracks the file.
How far does an EU passport reach for tokenized assets?
A MiCA passport covers crypto-asset services across EU member states, not tokenized securities and not markets outside the EU. Under MiCA Article 65, an authorised CASP notifies its home regulator and may start in another member state at the latest from the 15th calendar day after submitting that information.
Article 65 requires the CASP to send the information to its home competent authority, which forwards it to the host authority. The provider can begin once it receives notice of that communication, or on the 15th calendar day at the latest. Because MiCA excludes financial instruments, this passport does not extend to a tokenized bond or fund unit; those rely on MiFID II passporting or a DLT Pilot Regime permission.
Outside the EU, an issuer works market by market. The UAE alone has three separate regimes, VARA, ADGM and DIFC, and each authorises venues and service providers on its own terms.
How do US resale rules follow a token sold across borders?
They stay attached to the security, not to the venue. Under Rule 144, a restricted security can be resold only after six months if the issuer has reported under the Exchange Act for at least 90 days, or one year if it has not. The token contract has to enforce that period for every wallet, in every country.
17 CFR 230.144(d)(1) measures the period from the later of acquisition from the issuer or from an affiliate, and it applies to the acquiror and “any subsequent holder.” A US investor who sells a restricted token on a foreign venue does not escape the clock.
Permissioned token standards give issuers the hooks to enforce such rules by country. The ERC-3643 specification stores “a country code corresponding to the investor's country of residence” in the Identity Registry, set under ISO-3166, and its Compliance contract can cap the number of investors per country or tokens per investor. A transfer that breaks a rule reverts.
| Rule | Source | How a token can enforce it (our analysis) |
|---|---|---|
| 6-month or 1-year holding period | 17 CFR 230.144(d)(1) | Time-lock module checked by the Compliance contract on each transfer |
| Country eligibility | Offering exemption terms in each market | ISO-3166 country code in the Identity Registry; per-country investor caps |
| Sanctions blocking | 31 CFR Part 501 and local sanctions law | Wallet or partial freeze; the reporting duty stays off-chain |
What should an issuer map before launching in a second jurisdiction?
Five items: how the token is classified there, which offering exemption or prospectus route applies, which licensed venues and service providers can handle it, what anti-money-laundering duties attach, and which resale limits follow it. Each answer becomes a rule in the token contract or a duty for a named party.
- Classification: financial instrument, crypto-asset or something else, with a legal opinion for each market.
- Offering route: prospectus, private placement exemption or professional-investor regime, and the investor categories it allows.
- Licensed counterparties: venue, custodian and transfer agent authorised in that market, or a passport that reaches it.
- AML and sanctions: customer due diligence standards and the sanctions lists the issuer and its agents must screen against.
- Resale limits: holding periods, country restrictions and investor caps, written as contract rules before launch.
The FSB's finding that supervision and enforcement lag behind rule-writing cuts both ways. A market with new rules and thin supervisory practice may change its interpretation after launch, so the mapping should be repeated at least when a regulator issues new guidance.
What can protocol-level infrastructure solve, and what can it not?
Code can enforce a rule once lawyers have defined it, such as a country cap, a holding period or a verified-identity check. It cannot classify a token, grant a licence, or file a regulatory report. Those steps stay with the issuer, its counsel and its licensed service providers in each jurisdiction.
Network-level designs move some enforcement out of individual token contracts. Blockmaze Foundation, for example, describes a Layer-0 network that maintains issuer registries and connects jurisdiction-specific domains. Whether enforcement belongs in the token, the venue or a shared layer is a trade-off our pillar guide on smart contract compliance versus Layer-0 governance sets out, and our piece on Layer-0 regulatory compliance harmonization covers the cross-jurisdiction case.
When on-chain enforcement breaks down
- Conflicting rules: if two jurisdictions impose incompatible conditions on the same holder, the contract can block the transfer but cannot reconcile the law.
- Stale identity data: a country code or eligibility claim is only as current as the provider that issued it.
- Off-chain duties: reports, disclosures and licence conditions are met by people and filings, not by transfer logic.
Frequently Asked Questions
What are the main cross-border regulatory challenges for RWA tokenization?
Four recur: the same token can be a financial instrument in one jurisdiction and a crypto-asset in another; venue and service licences rarely travel across borders; resale restrictions such as US Rule 144 holding periods follow the token to foreign buyers; and supervisors cooperate unevenly. The FSB found in October 2025 that cross-border cooperation on crypto-assets was fragmented, inconsistent and insufficient.
Does a MiCA licence let a firm offer tokenized securities across the EU?
No. MiCA Article 2(4)(a) excludes crypto-assets that qualify as financial instruments, so a MiCA CASP authorisation and its Article 65 passport cover crypto-asset services only. A tokenized bond, share or fund unit needs MiFID II authorisation or a DLT Pilot Regime permission. Since the MiCA transitional period ended on 1 July 2026, firms without a MiCA licence cannot provide crypto-asset services to EU clients.
How much tokenized activity can an EU DLT market infrastructure handle?
Under the current DLT Pilot Regime, the aggregate market value of DLT financial instruments is capped at EUR 6 billion at admission, with a transition strategy triggered at EUR 9 billion. The Commission's 4 December 2025 proposal would raise the regular-regime cap to EUR 100 billion and the trigger to EUR 150 billion, and open the regime to all financial instruments. The current caps apply until an amendment is adopted.
Can a smart contract enforce rules from several jurisdictions at once?
It can enforce rules that are already defined. ERC-3643 stores an ISO-3166 country code for each investor in its Identity Registry, and its Compliance contract can cap investors per country or tokens per investor. A contract cannot decide whether a token is a security, grant a licence or file a regulatory report; those steps stay with the issuer, its counsel and its service providers.
Which jurisdictions have finished building crypto-asset rules?
Fewer than half of those reviewed. The FSB's October 2025 peer review, using data as of August 2025, found that 11 jurisdictions in the review (39%) had finalised a crypto-asset framework that addresses financial stability, eight (29%) were consulting on or finalising one, three (11%) had partial frameworks and six (21%) were at an early stage. Issuers planning a multi-country launch should expect rules to keep changing.
Related Articles
RWA Tokenization in the UAE & Middle East: VARA, ADGM, DIFC Explained
How the UAE's three regulatory frameworks — VARA, ADGM and DIFC — apply to institutional RWA tokenization programs.
How Does Singapore Regulate Tokenised Funds?
MAS did not write a bespoke regime: a tokenised fund unit is treated under existing securities law, and Project Guardian focused on operational frameworks.
Navigating MiCA Regulations for RWA Tokenization
What MiCA means for issuers and service providers handling tokenized real-world assets in the EU.
Compliant RWA Issuer Registries: Best Practices
What an issuer registry record should contain, from on-chain data standards to governance and audit trail requirements.