Regulation

Recherche vérifiée par sources: FSB 2026 Crypto WORK

5 min

Le corps de l'article est affiché dans sa version anglaise vérifiée. La traduction sera ajoutée après revue des sources.

Verified Fact Boundary

1. FSB's crypto policy area lists a 2026 work programme and crypto-related regional consultative group activity. 2. FSB says the G20 charged it with coordinating delivery of an effective and comprehensive regulatory framework for crypto-assets. 3. FSB's crypto-assets and global stablecoins page keeps the 2023 crypto-asset and global-stablecoin recommendations as key reference documents. 4. FSB material says implementation progress is welcome but gaps and inconsistencies remain. 5. AMF says FSB and IOSCO published reports assessing implementation of recommendations on crypto-asset and stablecoin activities. 6. A global policy implementation map does not prove that a specific user, account, stablecoin, venue or jurisdiction has a final binding permission.

Réduire

Decision Matrix

Tableau de l’article : faites défiler horizontalement ou placez le focus sur le tableau et utilisez les flèches.

CheckWhat it meansPractical actionUnknown to keep explicit
Policy source typeFSB recommendations and work programmes are global coordination sources, not local account permissionslabel the source as recommendation, work plan, peer review or local rulewhether a jurisdiction has implemented the relevant element
Stablecoin arrangementglobal stablecoin work focuses on arrangements, governance and cross-border risksidentify issuer, reserve, redemption, transfer and oversight source separatelywhether a wallet user has enforceable redemption rights
CASP or VASP activityframework implementation can cover exchanges, custody, transfer, stablecoin and DeFi interfaces differentlymap the activity before applying a broad crypto-policy labelwhether a local provider sits inside or outside the relevant perimeter
Implementation gapFSB references gaps and inconsistencies across jurisdictionstreat cross-border service claims as higher risk until local evidence is foundwhether regulatory arbitrage changes user protection
Exchange termsglobal policy does not replace a venue's account, region and product termsread official platform terms before onboarding, depositing or tradingwhether a product is unavailable despite broad policy discussion
Evidence datepolicy work evolves through work programmes, reviews and implementation reportsrecord source date and next review date in the decision notewhether a later local rule supersedes the global reference

Source Map

Control Notes

1. Policy source type

Policy source type is the point where public documentation must become an operating rule. In this package, it means FSB recommendations and work programmes are global coordination sources, not local account permissions. The practical action is to label the source as recommendation, work plan, peer review or local rule. The unresolved edge is whether a jurisdiction has implemented the relevant element, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

2. Stablecoin arrangement

Stablecoin arrangement is the point where public documentation must become an operating rule. In this package, it means global stablecoin work focuses on arrangements, governance and cross-border risks. The practical action is to identify issuer, reserve, redemption, transfer and oversight source separately. The unresolved edge is whether a wallet user has enforceable redemption rights, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

3. CASP or VASP activity

CASP or VASP activity is the point where public documentation must become an operating rule. In this package, it means framework implementation can cover exchanges, custody, transfer, stablecoin and DeFi interfaces differently. The practical action is to map the activity before applying a broad crypto-policy label. The unresolved edge is whether a local provider sits inside or outside the relevant perimeter, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

4. Implementation gap

Implementation gap is the point where public documentation must become an operating rule. In this package, it means FSB references gaps and inconsistencies across jurisdictions. The practical action is to treat cross-border service claims as higher risk until local evidence is found. The unresolved edge is whether regulatory arbitrage changes user protection, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

5. Exchange terms

Exchange terms is the point where public documentation must become an operating rule. In this package, it means global policy does not replace a venue's account, region and product terms. The practical action is to read official platform terms before onboarding, depositing or trading. The unresolved edge is whether a product is unavailable despite broad policy discussion, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

6. Evidence date

Evidence date is the point where public documentation must become an operating rule. In this package, it means policy work evolves through work programmes, reviews and implementation reports. The practical action is to record source date and next review date in the decision note. The unresolved edge is whether a later local rule supersedes the global reference, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

Known Unknowns

  • whether a jurisdiction has implemented the relevant element
  • whether a wallet user has enforceable redemption rights
  • whether a local provider sits inside or outside the relevant perimeter
  • whether regulatory arbitrage changes user protection
  • whether a product is unavailable despite broad policy discussion
  • whether a later local rule supersedes the global reference

Practical Takeaway

FSB crypto work remains a policy-implementation story rather than a single new trading rule. The FSB crypto-assets policy area lists the 2026 work programme and recent regional consultative group activity, while the FSB crypto-assets and global stablecoins page keeps the 2023 global framework and later implementation reviews as the core reference set. FSB material says implementation progress is welcome but gaps and inconsistencies remain, creating regulatory-arbitrage and oversight challenges. The useful decision is to map whether a user question is about a binding local rule, an FSB recommendation, a stablecoin arrangement, a CASP/VASP activity, or an exchange's own account terms before acting. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.

Sources

05
  1. Financial Stability BoardPolicy Area: Crypto Assets
  2. Financial Stability BoardCrypto-assets and Global Stablecoins
  3. Financial Stability BoardThematic Review on FSB Global Regulatory Framework for Crypto-asset Activities
  4. Autorité des marchés financiersFSB and IOSCO reports assessing implementation of crypto recommendations
  5. Bank for International SettlementsFinancial stability implications of tokenisation