出典確認済みリサーチ: Genius ACT Stablecoin AML
本文は確認済みの英語原文で表示しています。翻訳版は出典確認後に追加します。
Verified Fact Boundary
1. Treasury's OFAC recent action page describes a proposed rule to implement GENIUS Act sanctions compliance requirements for permitted payment stablecoin issuers. 2. Treasury's GENIUS Act congressional report discusses technologies to counter illicit finance involving digital assets. 3. The Federal Reserve published a statement on proposed customer-identification-program requirements for payment stablecoin issuers. 4. Federal Reserve statement language raises concerns about illicit finance risks in secondary market stablecoin transactions. 5. A proposed rule or report does not prove a specific wallet, issuer, exchange route or transfer is approved for a user. 6. Users and operators should separate issuer compliance duties from account-specific transfer, identity and sanctions-screening evidence.
閉じる
Decision Matrix
記事の表：横にスクロールするか、表の領域にフォーカスして矢印キーを使ってください。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Rule status | a proposed rule is not the same as final compliance state | label proposal, report and final rule separately | final regulatory text and effective dates |
| Issuer duty | permitted payment stablecoin issuers may face program obligations | map issuer, regulator and program scope before drawing user conclusions | issuer-specific implementation |
| Sanctions screening | sanctions compliance can affect transfers and counterparties | avoid using stablecoin route claims without screening and jurisdiction notes | private screening outcome |
| Customer identification | CIP requirements concern identity programs, not anonymous universal access | separate customer onboarding from secondary market wallet movement | implementation by non-bank entities |
| Secondary market | stablecoin use beyond the issuer can create different risk surfaces | identify whether the user is dealing with issuer, exchange, wallet or DeFi route | off-platform transaction monitoring |
| User checklist | regulatory language should become a transfer-readiness checklist | verify issuer, route, counterparty, jurisdiction, wallet and freeze or block risk | support-only account facts |
| Claim boundary | compliance progress is not a safety, redemption or liquidity guarantee | keep compliance facts separate from product suitability | future enforcement interpretation |
Source Map
- U.S. Treasury OFAC: Treasury Proposes Rule to Implement the GENIUS Act's Requirements to Counter Illicit Finance (treasury-genius-ofac)
- U.S. Treasury: GENIUS Act Illicit Finance Innovation Congressional Report (treasury-genius-report)
- Federal Reserve Board: Statement on Customer Identification Program Requirements for Payment Stablecoin Issuers (federal-reserve-cip-statement)
Control Notes
1. Rule status
Rule status is the decision point where public documentation must become an operating rule. In this package, it means a proposed rule is not the same as final compliance state. The practical action is to label proposal, report and final rule separately. The unresolved edge is final regulatory text and effective dates, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
2. Issuer duty
Issuer duty is the decision point where public documentation must become an operating rule. In this package, it means permitted payment stablecoin issuers may face program obligations. The practical action is to map issuer, regulator and program scope before drawing user conclusions. The unresolved edge is issuer-specific implementation, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
3. Sanctions screening
Sanctions screening is the decision point where public documentation must become an operating rule. In this package, it means sanctions compliance can affect transfers and counterparties. The practical action is to avoid using stablecoin route claims without screening and jurisdiction notes. The unresolved edge is private screening outcome, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
4. Customer identification
Customer identification is the decision point where public documentation must become an operating rule. In this package, it means CIP requirements concern identity programs, not anonymous universal access. The practical action is to separate customer onboarding from secondary market wallet movement. The unresolved edge is implementation by non-bank entities, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
5. Secondary market
Secondary market is the decision point where public documentation must become an operating rule. In this package, it means stablecoin use beyond the issuer can create different risk surfaces. The practical action is to identify whether the user is dealing with issuer, exchange, wallet or DeFi route. The unresolved edge is off-platform transaction monitoring, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
6. User checklist
User checklist is the decision point where public documentation must become an operating rule. In this package, it means regulatory language should become a transfer-readiness checklist. The practical action is to verify issuer, route, counterparty, jurisdiction, wallet and freeze or block risk. The unresolved edge is support-only account facts, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
7. Claim boundary
Claim boundary is the decision point where public documentation must become an operating rule. In this package, it means compliance progress is not a safety, redemption or liquidity guarantee. The practical action is to keep compliance facts separate from product suitability. The unresolved edge is future enforcement interpretation, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.
The operating test is also narrow. A public page can prove public wording.
Known Unknowns
- final regulatory text and effective dates
- issuer-specific implementation
- private screening outcome
- implementation by non-bank entities
- off-platform transaction monitoring
- support-only account facts
- future enforcement interpretation
Practical Takeaway
GENIUS Act stablecoin compliance should be read as an issuer and supervisory implementation question, not as a user guarantee that any stablecoin route is safe. Treasury's OFAC action describes a proposed rule requiring permitted payment stablecoin issuers to maintain effective sanctions compliance programs. Treasury's congressional report discusses innovative technologies for countering illicit finance involving digital assets, and the Federal Reserve published a statement on proposed customer-identification-program requirements for payment stablecoin issuers. The decision outcome is to separate issuer obligations, proposed-rule status, sanctions screening, customer identification, secondary-market risk and user transfer checks. 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, callback, policy framework, settlement route or liquidity position will work under every future condition.