The CLARITY Act Explained: Developer Safe Harbors, Stablecoin Rules, and Self-Custody Rights

For years, digital asset developers and cryptocurrency businesses have operated in regulatory limbo. A protocol developer could face securities registration requirements. A wallet creator could be prosecuted for money transmission, and a stablecoin platform offering rewards could be accused of operating an unlicensed bank.
The Digital Asset Market Clarity Act (CLARITY Act), currently advancing through Congress with bipartisan support, aims to resolve these questions. The bill establishes explicit safe harbors for non-custodial developers, clarifies federal versus state authority, protects self-custody rights, and creates clear rules for stablecoin yields.
With Senate markups scheduled and passage expected in early 2026, understanding these provisions is critical for compliance planning. This analysis breaks down the key frameworks affecting DeFi developers, infrastructure providers, and stablecoin platforms.
The Developer Safe Harbor: Section 15H Protection

Section 601 introduces Exchange Act §15H, creating explicit safe harbors for blockchain developers. Under this provision, you are not subject to Exchange Act registration requirements solely because you:
- Relay or validate transactions on distributed ledger networks
- Operate nodes, oracles, or bandwidth infrastructure
- Develop, publish, or maintain distributed ledger technology systems
- Create or distribute self-custody tools like non-custodial wallets
Theprovision states that these carve-outs do not expand SEC jurisdiction by implication; the agency cannot use safe harbors as grounds to assert broader authority over adjacent activities.
SEC Rulemaking Requirements
Section 15H directs the SEC to clarify when DeFi-adjacent activities alone don’t trigger intermediary obligations, specifically addressing:
- User interfaces that read or display blockchain data
- Governance systems and DeFi messaging
- Liquidity pools and AMM protocols
- Distribution of wallet and self-custody tools (with First Amendment considerations)
Federal Preemption, State Authority Preserved
The provision supersedes state securities and digital asset licensing laws only for core §15H(b) development activities. States retain full authority over anti-money laundering, anti-fraud, and anti-manipulation enforcement. A California DeFi developer wouldn’t need a DFAL license for covered development, but remains subject to state fraud prosecution.
BRCA Safe Harbor: The “Non-Controlling” Developer Standard

Section 604 incorporates the Blockchain Regulatory Certainty Act, creating a federal safe harbor from money services business registration (31 U.S.C. § 5330) and criminal money transmission prosecution (18 U.S.C. § 1960) for “non-controlling” developers.
Defining “Non-Controlling”
You’re considered “non-controlling” when, in regular operations, you lack:
- Legal right to control user transactions
- Unilateral ability to initiate transactions on demand
- Power to effectuate transactions without another party’s approval or consent
Covered Activities
The safe harbor protects:
- Publishing or maintaining distributed ledger software
- Providing hardware/software for customer self-custody
- Providing infrastructure support to maintain decentralized services
What’s Not Covered: Centralized exchanges, hosted wallets, or any service exercising unilateral control over customer funds must obtain appropriate money transmitter licenses.
Treasury’s Offshore Reach

Section 603 grants Treasury authority to impose special measures against offshore platforms presenting money laundering or sanctions risks—even for non-custodial protocols:
“Treasury can lean on US rails to isolate an offshore venue or transaction class even if the underlying protocol is non-custodial. The practical reach turns on how Treasury defines ‘transmittals of funds’ by regulation.”
Practical Impact: Technical decentralization doesn’t guarantee immunity from U.S. enforcement. Treasury can effectively cut off any platform’s U.S. access, regardless of its custodial model.
Keep Your Coins: Self-Custody Protection

Section 605 prohibits federal agencies from restricting individuals’ ability to self-custody digital assets using self-hosted wallets for lawful purposes.
The aim of this section is to protect the right to self-custody and protect the regulator’s ability to pursue enforcement of the Bank Secrecy Act, sanctions, anti-fraud actions, and the prosecution of illicit finance.
Stablecoin Yield Restrictions

Section 404 prohibits digital asset service providers from paying “interest or yield” solely for holding payment stablecoins.
Permitted Activity-Based Rewards
Platforms may offer rewards tied to:
- Transactions, payments, or settlement activity
- Wallet, platform, or protocol usage
- Loyalty programs, merchant rebates, or subscriptions
- Liquidity provision, collateral posting, or staking
Marketing Prohibitions
Section 404 bans:
- Comparing yields to bank deposit rates or suggesting FDIC insurance
- Claiming the issuer pays when third parties provide rewards
- Marketing as “risk-free” or “bank-interest” equivalent
- Material omissions about reward sources or conditions
Disclosures must clearly identify who pays rewards and explain program mechanics. Issuers aren’t deemed to pay yield unless they actually direct the rewards program.
What This Means for Your Business

The CLARITY Act resolves threshold questions about developer liability, self-custody rights, and stablecoin economics that have created compliance uncertainty for years. However, effectiveness depends on implementation; SEC, CFTC, Treasury, and FinCEN rulemaking over the next 18-24 months will determine whether the law delivers regulatory certainty or shifts ambiguity from statutes to regulations.
Immediate Action Items:
- For DeFi Developers: Document your non-controlling status and structure activities to fall within §15H protections. Participate in SEC rulemaking to ensure your activities receive appropriate clarification.
- For Stablecoin Platforms: Eliminate passive holding rewards or restructure as activity-based incentives. Implement Section 404-compliant disclosures and separate issuer operations from platform reward programs.
- For Infrastructure Providers: Assert BRCA protections against state licensing demands while maintaining OFAC screening and sanctions compliance.
The regulatory landscape will shift rapidly once the CLARITY Act becomes law. Companies that proactively restructure operations and engage with rule making processes will avoid enforcement actions during the transition period.
Further Reading
Legislative Resources:
- Digital Asset Market Clarity Act (CLARITY Act)
- Guiding and Establishing National Innovation for U.S. Stablecoins Act (GENIUS Act)
Legal Analysis:
- Clarifying the CLARITY Act: What To Know About the House Crypto Market Structure Bill, Arnold & Porter Legal Advisories (August 2025)
- Inside 2025’s Biggest Crypto Policy Breakthroughs, DeFi Education Fund Policy Analysis (December 2025)
Disclaimer: This blog post is for informational purposes only and does not constitute legal advice. The CLARITY Act remains pending legislation. Companies affected by digital asset regulation should consult qualified legal counsel to assess their specific compliance obligations.
