Treasury moves to lock in stablecoin rules with state–federal hybrid framework

ambcryptoPubblicato 2026-04-01Pubblicato ultima volta 2026-04-01

Introduzione

The U.S. Treasury has proposed a hybrid state–federal regulatory framework for stablecoin issuers under the GENIUS Act. Issuers with less than $10 billion in outstanding supply may operate under state-level supervision if state regimes are "substantially similar" to federal standards, which set strict requirements for reserve backing, anti-money laundering, and consumer protection. Once an issuer exceeds $10 billion, it must transition to federal oversight under the Office of the Comptroller of the Currency. The proposal aims to prevent regulatory arbitrage by ensuring state rules meet or exceed federal safeguards, treating stablecoins more like traditional financial instruments with bank-like oversight.

The U.S. Department of the Treasury has taken a key step toward implementing U.S. stablecoin legislation, releasing its first proposed rule under the GENIUS Act and opening a 60-day public comment period.

The notice of proposed rulemaking [NPRM] outlines how payment stablecoin issuers may operate under either federal oversight or qualifying state-level regimes. This marks a shift from legislative intent to regulatory execution.

A hybrid model with strict limits

At the center of the proposal is a dual-track system. Stablecoin issuers with less than $10b in outstanding supply may opt for state-level supervision, but only if those regimes are deemed “substantially similar” to federal standards.

Treasury’s proposal makes clear that similarity does not mean flexibility on core safeguards. State frameworks must “meet or exceed” federal requirements for key areas such as reserve backing, anti-money laundering compliance, and consumer protections.

This effectively sets a federal floor while allowing limited state-level customization in areas like capital requirements, provided outcomes remain equally stringent.

A built-in transition to federal oversight

The framework also introduces a structural threshold. Once a stablecoin issuer exceeds $10b in supply, it would transition toward federal supervision, with the Office of the Comptroller of the Currency [OCC] positioned as the primary regulator.

Treasury’s proposal repeatedly anchors the federal benchmark to OCC rules and interpretations. This signals a long-term pathway where larger issuers are brought under a unified national framework.

This creates a tiered regulatory model: smaller issuers may operate under state regimes, but growth ultimately leads to federal oversight.

Limiting regulatory arbitrage

A central objective of the proposal is to prevent regulatory fragmentation. By requiring state regimes to align closely with federal standards, Treasury aims to eliminate incentives for issuers to seek out weaker jurisdictions.

State-level rules must remain consistent with federal law. They cannot dilute core protections such as reserve composition or disclosure frequency. Any deviation that weakens these standards would fail the “substantial similarity” test.

Stablecoins move closer to bank-like oversight

The proposal reinforces a broader trend of treating stablecoins as financial infrastructure rather than experimental assets.

Requirements around custody, insolvency treatment, and supervision mirror traditional banking safeguards, including prioritizing stablecoin holders in insolvency scenarios.

With this NPRM, Treasury is effectively laying the groundwork for a regulated, scalable stablecoin market that balances innovation with systemic safeguards.


Final Summary

  • Treasury’s proposal sets a federal floor that limits state-level flexibility, reducing the risk of regulatory arbitrage.
  • Smaller players can operate under state regimes, but growth beyond $10b will likely push them into federal oversight under the OCC.

Domande pertinenti

QWhat is the key step the U.S. Department of the Treasury has taken regarding stablecoin legislation?

AThe U.S. Department of the Treasury has released its first proposed rule under the GENIUS Act and opened a 60-day public comment period, outlining how payment stablecoin issuers may operate under either federal oversight or qualifying state-level regimes.

QWhat is the threshold amount that triggers a transition from state-level to federal supervision for stablecoin issuers?

AOnce a stablecoin issuer exceeds $10 billion in outstanding supply, it would transition toward federal supervision under the Office of the Comptroller of the Currency (OCC).

QWhat are the core safeguard areas where state frameworks must meet or exceed federal requirements?

AState frameworks must meet or exceed federal requirements for key areas such as reserve backing, anti-money laundering compliance, and consumer protections.

QWhat is the primary objective of requiring state regimes to be 'substantially similar' to federal standards?

AThe primary objective is to prevent regulatory fragmentation and eliminate incentives for issuers to seek out weaker jurisdictions, thereby limiting regulatory arbitrage.

QWhich federal agency is positioned as the primary regulator for larger stablecoin issuers under the proposed framework?

AThe Office of the Comptroller of the Currency (OCC) is positioned as the primary regulator for larger stablecoin issuers under the proposed federal oversight framework.

Letture associate

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

A researcher discovered a critical "infinite mint" vulnerability in the Zcash cryptocurrency's Orchard protocol using Claude Opus 4.8, leading to a swift fix but also a 50% market drop, erasing billions in value. This incident highlights a new era where powerful, accessible AI models are dramatically lowering the barrier to finding software vulnerabilities. Previously, the security community feared specialized models like Claude Mythos Preview, capable of finding decades-old zero-day exploits. The Zcash case, however, involved a publicly available, general-purpose model. This shift makes advanced security auditing—and attack capabilities—accessible to far more people, not just experts. The mass democratization of vulnerability discovery brings a dual challenge: a flood of low-quality, AI-generated false reports that overwhelm maintainers, and the real, rapid uncovering of deep, dangerous bugs. Open-source projects, often understaffed and unfunded, are particularly vulnerable to this "attention DDoS." The article cites examples like curl shutting down its bug bounty program due to the unsustainable workload. Our perceived digital safety has often been luck, relying on the high cost and effort required to find deeply hidden flaws in complex systems, as seen with historical vulnerabilities like Heartbleed or Baron Samedit. AI changes this cost structure, effectively "mass-producing flashlights" to illuminate every corner of our codebase. While large companies operate extensive security chains involving external white-hat hackers and massive defensive operations, the global cybersecurity workforce faces a severe shortage, especially of experienced personnel capable of analyzing complex threats and coordinating fixes. The core dilemma emerges: AI makes *finding* bugs cheap and scalable, but *fixing* them remains a slow, expensive, and human-intensive process. The article concludes that AI won't destroy the internet but acts as a bright light, revealing that our digital existence is not inherently secure but is precariously maintained by ongoing human effort. The true cost in the AI era may not be discovery, but whether there will be enough people left willing and able to do the hard work of repair.

marsbit3 min fa

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

marsbit3 min fa

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

"Codex Goal Mode: How to Make AI Work Continuously Toward a Specific Goal" OpenAI's Codex "goal mode" (/goal) transforms the AI from a reactive code assistant into a proactive execution agent capable of working autonomously for hours or even days to achieve a defined objective. To maximize its effectiveness, follow these key principles: 1. **Define Clear, Verifiable Exit Criteria:** The goal prompt should be a concise, measurable success condition, not a lengthy specification. Use quantifiable metrics like "reduce build time by 30%" or "achieve 100% test parity." 2. **Provide Initial Guidance and Tools:** Direct Codex toward likely problem areas and specify available tools (e.g., browsers, testing environments) to prevent it from exploring unproductive paths. 3. **Enable Progress Measurement:** Equip Codex with ways to track advancement, such as creating comparison tools for visual tasks or evaluation sets, ensuring it can gauge its own progress. 4. **Use a Realistic Execution Environment:** For tasks like performance optimization, provide access to environments that closely mimic production (e.g., similar configs, databases) to yield valid results. 5. **Be Cautious with Visual Goals:** Avoid vague "pixel-perfect" instructions. Instead, supplement visual references with functional checklists or design system specifications to prevent Codex from obsessing over minor details. 6. **Implement Progress Tracking:** For long-running tasks, have Codex commit code to draft PRs, update progress documents, or send Slack updates to maintain visibility into its work. 7. **Review and Consolidate Results:** Once the goal is met, instruct Codex to review its work, clean up ineffective experimental code, and reflect on what strategies succeeded or failed. Ultimately, using goal mode shifts the developer's role from writing prompts to managing a persistent engineering agent—defining objectives, establishing metrics, configuring environments, and conducting final reviews.

marsbit1 h fa

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

marsbit1 h fa

From Ethereum to AI's 'CROPS': What Exactly Is This 'Slow Variable' That Vitalik Has Repeatedly Emphasized?

Recently, Vitalik Buterin has frequently emphasized the concept of "CROPS," first outlined in the Ethereum Foundation's March mandate as core principles guiding its focus: Censorship Resistance, Capture Resistance, Open Source, Privacy, and Security. CROPS represents Ethereum's commitment to providing foundational capabilities for user sovereignty—enabling asset ownership, identity expression, and coordination without reliance on centralized platforms or surrendering ultimate control. This framework is gaining new urgency with the rise of AI, particularly AI agents managing digital assets and automating transactions. While AI offers convenience, it risks centralizing user data, intent, and control if dependent on opaque, centralized services. Vitalik argues for "CROPS AI"—AI that is open, privacy-preserving, secure, and capable of local execution to maintain user agency. He highlights convergence between "CROPS Ethereum access layers" and "CROPS AI," such as using zero-knowledge proofs for private remote LLM calls and Ethereum RPC reads, ensuring users can access services without exposing sensitive information. Ultimately, CROPS is not just an abstract ideal but a practical guide for Ethereum's development and AI integration. It addresses the critical long-term question: as digital systems grow more powerful, how can users retain control over their privacy, assets, and autonomy? In an AI-driven era, these principles may define Ethereum's enduring value—prioritizing verifiable, secure, and user-centric design over short-term optimizations like speed and cost alone.

marsbit1 h fa

From Ethereum to AI's 'CROPS': What Exactly Is This 'Slow Variable' That Vitalik Has Repeatedly Emphasized?

marsbit1 h fa

Trading

Spot
Futures
活动图片