Content
Consensys is pushing Treasury to draw a clearer line around self-custody as U.S. agencies implement the GENIUS Act.
In a policy post, the company said it supports the law’s stablecoin framework but wants Treasury’s final rules to explicitly distinguish self-custodial wallets from regulated digital asset service providers (DASPs). The timing matters because Treasury’s GENIUS Act rulemaking process is now the key venue where those definitions get operationalized.
Consensys’ core argument: wallets are tools, not intermediaries
Consensys frames the issue around how self-custody software is classified.
The company argues that self-custodial wallets should not be treated as DASPs, even when they include embedded features like swaps, bridges, or fiat on-ramps. Its position is that these wallets provide software tools for users acting on their own behalf, rather than custody, exchange, transfer, or issuance services on behalf of others.
Consensys also leans on the policy framing: it says self-custody has been recognized by Congress and the executive branch as an important part of U.S. digital asset leadership, and that Treasury should preserve that distinction in implementation.
The specific GENIUS Act point they want Treasury to clarify
The most concrete ask in Consensys’ post is about the wallet exemption in the GENIUS Act.
Consensys cites Section 3(h)(1)(C), which it says exempts transactions conducted via self-custodial wallets from the Act’s prohibitions, and argues Treasury should clarify that this applies broadly — including wallet transactions that use embedded services.
That’s a meaningful distinction for wallet providers because the user experience in modern wallets often includes built-in routing, bridging, and fiat access. If Treasury interprets those features too broadly as regulated intermediation, it could reshape how self-custody products are designed in the U.S. (This is a practical implication, not a statement from Treasury.)
Why Treasury rulemaking is the real battleground now
Treasury’s ANPRM on GENIUS Act implementation makes clear it is collecting feedback on a wide range of issues, including regulatory clarity, illicit finance obligations, foreign regimes, and the scope of key definitions.
The Federal Register notice also specifically asks whether the scope of “digital asset service provider” is sufficiently clear, which is exactly the lane Consensys is targeting with this submission. Treasury’s initial ANPRM comment window closed in October 2025, and the notice shows hundreds of comments were received.
In other words: this is not just a blog-post debate. It is part of a formal rulemaking process that will shape how stablecoin and wallet activity is treated in practice under U.S. law.
Why it matters for crypto
- Self-custody policy is now a rulemaking issue, not just a political talking point. Treasury’s definitions will determine how wallet products can operate under the GENIUS framework.
- The DASP definition is a major pressure point. If wallet software is treated as an intermediary, product design and compliance burdens could change materially.
- This affects more than MetaMask. The same interpretation could impact many wallets that bundle swaps, bridges, and on-ramps into one interface. (Inference based on the type of features Consensys described.)
- GENIUS implementation is becoming the next major U.S. crypto policy layer. The law is passed; now the details come from Treasury and other agencies.
What to watch next
- Treasury’s next-stage rule proposals or guidance on DASP scope and how it treats self-custody wallet software.
- Whether Treasury explicitly addresses the Section 3(h) wallet exemption in future text or FAQs.
- Additional public comment letters from wallet providers, exchanges, and banking groups as agencies move from ANPRM to proposed rules.
- How other GENIUS implementation tracks (AML/sanctions, foreign issuer comparability, state/federal oversight) interact with wallet and stablecoin distribution models.
Source: Consensys blog post; U.S. Treasury / Federal Register GENIUS Act implementation materials