Digital Asset Market Clarity Act: What the Senate Draft Actually Says

The Senate Banking Committee just released a 10-page section-by-section summary of the Digital Asset Market Clarity Act. It is the clearest look so far at how the US Senate intends to draw the lines between commodities and securities, what banks are allowed to do with digital assets, and where developers stand under federal law.

The summary is a draft. The text itself is still moving. But the architecture is now visible - and the architecture is what matters for anyone trying to position around the next year of US crypto regulation.

The Default Position: Tokens Are Commodities

The single most consequential framing in the bill sits in Title I. The draft introduces the concept of an "ancillary asset" - a network token whose value depends on entrepreneurial or managerial effort - and creates a rebuttable presumption that any network token is an ancillary asset and therefore treated as a commodity, not a security.

That presumption can be overridden, but the burden sits with the SEC or the originator to provide evidence that a token is something else. This inverts the regulatory posture of the last several years, where the default assumption from the SEC was that most tokens were securities until proven otherwise.

Section 103 then carves out an SEC registration exemption called Regulation Crypto. Under it, an ancillary asset originator can raise up to $50 million per calendar year for four years, or 10% of the outstanding token value - whichever is greater - up to a hard cap of $200 million in gross proceeds. Initial and semi-annual disclosures are required. This is meaningful for projects that want to raise from US retail without going through the full securities-registration regime.

There are guardrails. Section 104 restricts how much insiders can resell over a 12-month window, which is designed to prevent the kind of insider dump dynamics that have defined past token cycles. Notably, this section explicitly states that DAOs and decentralized governance systems are not treated as a single coordinated actor - a clarification that the DeFi community has been pushing for years.

What Banks Are Allowed to Do

Title IV addresses something that has been quietly limiting institutional crypto adoption: banks have not had a clear federal mandate to handle digital assets in their existing business lines.

Section 401 fixes this directly. It amends the Bank Holding Company Act, the National Bank Act, and other banking statutes to clarify that financial holding companies, national banks, state banks, and certain credit unions can use digital assets and blockchain technology for any activity they are already permitted to perform - payments, lending, custody, trading.

This is not a new license. It is a clarification that the existing license already covers these activities. The practical effect is that banks no longer need to wait for a separate regulatory blessing to integrate digital assets into payment rails, custody products, or lending operations.

Section 402 then requires the SEC and CFTC to jointly issue portfolio margining rules across securities, swaps, futures, and digital commodity accounts. For sophisticated traders running multi-asset positions through a single broker, this is a structural improvement - risk is netted across the full book rather than fragmented across silos.

Stablecoins: No Yield, By Design

Section 404 prohibits covered digital asset service providers and their affiliates from paying US customers passive, deposit-like interest or yield on payment stablecoin balances. Activity-based rewards - staking, transaction rebates - are still allowed under joint rules to be issued by the SEC, CFTC, and Treasury.

This is the provision that draws the clearest line between stablecoin issuers and banks. Banks are the only entities legally permitted to pay deposit-like interest on dollar balances. The bill preserves that moat.

The economic logic is straightforward. If stablecoins paid yield natively, they would functionally compete with bank deposits - and the deposit base is what funds bank lending. A no-yield rule keeps stablecoins in the role of payment infrastructure rather than deposit substitutes.

Section 304 then adds a recurring Treasury report on offshore stablecoins that depend on US Treasuries and are used at scale, with a focus on whether they pose illicit finance risks. This is the legal scaffolding for treating issuers like Tether differently from domestic, regulated alternatives.

DeFi: A Decentralization Test Before Regulation

Title III is where the bill draws its most technical lines. Section 301 directs the SEC to define when a DeFi trading protocol is "non-decentralized" - focusing on control, discretion, or the ability to alter or censor protocol operations.

Protocols that meet the non-decentralized test get pulled into existing securities intermediary requirements and Bank Secrecy Act obligations. Protocols that pass the decentralization test remain outside that perimeter. The bill also excludes core infrastructure - nodes, validators, relayers - and security councils from the controlling-actor analysis, provided no single actor has unilateral or practical control.

Section 302 then handles the front-end question. A "distributed ledger messaging system" - defined as the web-hosted front-end that lets users interact with a DeFi protocol - is treated separately from the protocol itself. Treasury is directed to publish sanctions and AML/CFT guidance specifically for US-person-owned or operated front-ends. This is where the regulatory pressure on DeFi will concentrate first: the websites, not the smart contracts.

Self-Hosted Wallets: Protected, With Limits

Section 605, titled the Keep Your Coins Act, states that federal agencies cannot prohibit, restrict, or impair the ability of a person to use a self-hosted wallet to custody their own digital assets. This codifies what has been a contested area of policy.

Section 307 layers on top of it: Treasury can issue guidance for financial institutions dealing with self-hosted wallets, but that guidance cannot generally require collecting personally identifiable information on the controller of a self-hosted wallet who is not the institution's customer or transaction counterparty.

These provisions preserve existing illicit-finance, sanctions, and money-laundering authorities. The protection is for the act of self-custody - not a blanket immunity from existing financial-crime enforcement.

Software Developers: Explicit Safe Harbor

Title VI provides the clearest protection for technical contributors. Section 601 states that software developers and network participants engaged solely in software development - compiling transactions, providing computational work for distributed ledgers - are not subject to federal or state securities laws for those activities.

Section 604, the Blockchain Regulatory Certainty Act, exempts blockchain developers and providers from being classified as money transmitters. Criminal liability for knowingly moving proceeds of crime is preserved. Civil registration requirements are removed.

This addresses one of the longer-running anxieties in the US crypto-developer community: that maintaining open-source infrastructure could trigger securities or money-transmitter obligations. The bill says explicitly that it does not.

Tokenized Securities Are Still Securities

Section 505 closes one of the more frequently asked questions. Tokenized securities - equity or debt instruments represented on a distributed ledger - receive the same regulatory treatment as the underlying securities they represent. The SEC retains full authority over them.

This forecloses the argument that tokenization on its own can change the legal character of an asset. The token wrapper does not convert a security into a commodity.

Bankruptcy: Customer Property Protections

Title VII addresses what happens when an exchange or custodian fails. Section 701 defines ancillary assets and digital commodities as customer property under Chapter 7 of the bankruptcy code - meaning they are treated like other commodities and securities in a bankruptcy proceeding, not as part of the failed firm's estate.

Section 702 creates a bankruptcy safe harbor for digital commodity transactions, deeming them commodity contracts under federal law. This allows counterparties to close out positions and access collateral outside standard bankruptcy proceedings, mirroring the protections that already exist for conventional derivatives and securities.

For users of regulated exchanges, this is a meaningful improvement on the post-FTX status quo, where customer claims have been contested for years in court.

Timing and What Could Still Change

Section 905 requires each regulator to adopt rules within one year of enactment. Section 906 sets a general effective date of 360 days after enactment - or 60 days after the final rule is published in the Federal Register if rulemaking is required, whichever is later.

So even after the bill passes, the operative rules arrive on a one-year delay at minimum. The implementation surface is large: the SEC, CFTC, Treasury, FinCEN, OFAC, NIST, and federal banking regulators all have rulemaking obligations under different sections.

Two areas remain especially live in negotiation. The anti-manipulation language for DeFi was scaled back in earlier drafts after industry lobbying - it could move again. And the precise definition of "non-decentralized" in Section 301 will shape which protocols fall inside or outside the perimeter, and that definition has not been finalized.

How to Read This

The summary document is a roadmap, not a final text. But the architectural choices are clear enough to position against:

• Default classification favors commodities. Token issuers can structure for the ancillary-asset presumption rather than the securities default.
• Banks are explicitly permitted to integrate digital assets into existing business lines. Expect institutional product launches to accelerate once the framework is in place.
• Stablecoin yield is structurally blocked. Payment stablecoin issuers cannot compete with bank deposits on rate. Domestic issuers are favored over offshore ones.
• Self-hosted wallets and software development are explicitly protected. The legal risk to non-custodial infrastructure drops materially.
• Tokenized securities remain securities. Tokenization is not a regulatory escape hatch.
• Implementation is at least a year out from enactment, and probably longer for the technical rules.

The bill is still draft. The footnotes are not written. But the shape of US crypto rules - for the first time in a serious legislative vehicle - is now legible.

Logs over lambos.