Senate Republicans Release Revised Clarity Act: What Changes for DeFi and Stablecoin Accounting
Senate Republicans published a revised version of the Clarity Act on September 10, 2026, less than a week before its first procedural vote on September 15. The update introduces a statutory definition of "non-decentralized finance trading protocols" and mandates CFTC registration for entities that meet that definition. For accounting firms, CFOs, and auditors with any US-facing crypto exposure, the bill's direction matters now, not after it clears the Senate, because the classification choices made today in your ledgers will either align or conflict with the framework Congress is writing.
What the Revised Bill Actually Says
The Clarity Act has been in legislative circulation for roughly a year, aimed at establishing the first federal-level regulatory framework for the crypto industry. The September 10 revision is significant because it responds to Democratic demands while still preserving the bill's core architecture under Republican sponsorship. Senator Lummis, who shepherded the bill and is not seeking re-election, confirmed that more than 114 separate provisions were incorporated at Democratic colleagues' request. Her characterisation: a "strong bipartisan product."
The New "Non-DeFi Protocol" Definition
The most consequential addition for accounting teams is the new language around non-decentralized finance trading protocols. The bill defines this category as any person or group of persons acting in concert who hold, directly or indirectly, the authority to control or materially alter the functionality, operation, or rules of consensus of a decentralized finance trading protocol. Put plainly: if a protocol has an identifiable human or corporate controller with real power to change how it works, it likely falls outside the "truly decentralised" carve-out and into the regulated bucket.
Entities that meet this definition would be required to register with the Commodity Futures Trading Commission. The bill also directs the CFTC and the Treasury Department to develop implementing rules, meaning the precise compliance obligations will be shaped through a rulemaking process that follows enactment, not before.
CFTC Jurisdiction and Spot Digital Commodity Markets
The revised text also includes clarifications related to spot and cash digital commodity transactions, a change Lummis attributed to concerns raised by tribal governments about the bill's potential overlap with prediction market regulation. Credit union crypto activity received additional definitional clarity as well. These are targeted adjustments rather than wholesale structural changes, but they do affect the jurisdictional lines that auditors and compliance officers will need to map.
Where the Bill Stands Politically
Passage is far from certain. The bill's path to President Trump's desk has been disrupted by a series of unresolved disputes, and the latest revision does not close all of them.
The Stablecoin Rewards Dispute
One of the long-running friction points involves the treatment of stablecoin rewards, specifically whether and how yield paid on stablecoins like USDC should be regulated. Banks and crypto firms have been on opposite sides of this debate. The stablecoin accounting implications are significant: depending on how rewards are ultimately classified, firms may need to account for them as interest income, fee income, or something else entirely, each carrying different tax and financial statement treatment. The revised bill does not appear to have resolved this dispute definitively.
Ethics Provisions and Trump's Crypto Holdings
A separate and politically charged obstacle involves ethics language tied to President Trump's growing crypto holdings, reportedly valued in the hundreds of millions of dollars and linked to digital asset ventures. In July, Trump agreed to a provision that would bar public officials, employees, and their spouses from issuing or sponsoring digital assets. That provision would be enforced by the Justice Department rather than state attorneys general, and it is written to expire in January 2029.
Democrats, joined by Republican Senator Thom Tillis, have pushed for stronger language. According to reporting by Politico cited in The Block's coverage, the latest version still lacks Democratic support on this point, which is critical because the bill needs bipartisan votes to clear the Senate. The revised text retains Justice Department primacy on enforcement and does not substantially alter the ethics section.
The September 15 Vote and Legislative Clock
The procedural vote scheduled for September 15 is not a final passage vote. It is a cloture motion or similar procedural step that tests whether there is enough support to advance debate. The Senate's calendar is tight: Lummis is departing Congress in January 2027, removing one of the bill's most committed advocates. That urgency has driven the Republican caucus to release a revised text quickly, but urgency alone does not resolve the substantive disagreements still outstanding. For firms tracking the legislative timeline, the September 15 result will be a reliable signal of whether the Clarity Act has a realistic path in the current session. Our earlier analysis of what a failed Clarity Act vote means for crypto accounting remains directly relevant as that date approaches.
Accounting Implications: DeFi Exposures
The new non-DeFi protocol definition has immediate practical relevance for DeFi accounting, even though the bill has not passed. Accounting teams and auditors should begin assessing existing protocol relationships against the bill's proposed control test.
Classifying Protocol Relationships Under the Proposed Control Test
The definition turns on whether a person or coordinated group can "control or materially alter" a protocol's functionality or consensus rules. In practice, this means reviewing governance structures: does your firm interact with a protocol that has an active multisig, a foundation with upgrade authority, or a team that can pause contracts? If yes, that protocol is a strong candidate for the "non-DeFi" category under the bill's framework.
From an accounting standpoint, classification matters because the type of counterparty affects how transactions are recorded. Interactions with a CFTC-regulated trading venue carry different disclosure, internal control, and potentially different asset classification obligations compared to interactions with a genuinely decentralised protocol. Firms using digital asset accounting software should confirm whether their current categorisation methodology can absorb a control-based test, because a rules-based regulator framework will eventually require that granularity.
On-Chain Governance Data and Audit Evidence
Auditors face a related challenge. Demonstrating that a protocol meets the "truly decentralised" standard will require on-chain governance data as audit evidence: voting records, upgrade histories, multisig key holder counts, and similar artefacts. This is not standard in most current audit file structures. Firms should start building that evidence-gathering process now, whether the bill passes in September 2026 or is deferred to a future session.
Accounting Implications: Stablecoin and USDC Positions
The stablecoin rewards dispute that continues to hold up the bill has direct consequences for USDC accounting and broader stablecoin accounting practices at US firms.
Revenue Recognition and Balance Sheet Treatment
If the final legislation treats stablecoin rewards as interest, holders may need to recognise them as interest income under ASC 835 or the relevant revenue recognition standard, which changes timing and gross vs. net presentation decisions. If rewards are treated as fee income or some other category, the treatment shifts again. CFOs carrying material USDC or other stablecoin balances that generate yield need contingency accounting policies prepared for at least two scenarios: a regulated interest model and an unregulated yield model. The bill's silence on this point in its current form is itself useful information: it signals that the accounting treatment will depend on rulemaking that follows enactment, not on the statute itself.
Credit Union Clarity and Treasury Policy
The credit union clarifications in the revised bill are narrow but worth monitoring for firms that bank with or audit credit unions active in digital assets. If the CFTC and Treasury rulemaking ultimately draws credit union crypto activity inside a specific regulatory perimeter, the accounting for those custodial or transactional relationships may need to be updated to reflect a new counterparty risk profile.
What Accounting Firms and CFOs Should Do Before September 15
The procedural vote is days away. There are concrete steps to take regardless of the outcome.
Protocol Inventory and Control Assessment
Pull a list of every DeFi protocol your firm interacts with, whether through direct trading, treasury management, yield strategies, or client activity. For each protocol, document who holds upgrade or governance authority, what on-chain mechanisms exist to change the protocol's rules, and whether any identified controller is a legal entity. This inventory is the foundation for applying the bill's non-DeFi test and will also be useful for any subsequent CFTC registration determination.
Stablecoin Accounting Policy Review
Review your current stablecoin accounting policies, specifically the sections that address yield, rewards, and income recognition. Identify where policy choices are currently contingent on regulatory classification. Flag those contingencies for the board or audit committee so that a policy update can be enacted quickly once the legislative outcome is known. For firms tracking how stablecoin licensing is taking shape in other jurisdictions, our coverage of how Clarity Act lobbying is shifting to home states provides useful political context alongside the accounting layer.
Digital Asset Accounting Software Configuration
If your digital asset accounting software or crypto bookkeeping software categorises transactions by protocol type, verify that the category taxonomy can accommodate a "CFTC-registered non-DeFi protocol" distinction. Many systems currently use binary DeFi/CeFi labels. A more granular regulatory classification layer will be needed once implementing rules emerge, and configuring that now reduces the reconciliation burden later.
Frequently Asked Questions
What is the Clarity Act trying to do?
The Clarity Act is proposed US federal legislation that would create the first comprehensive regulatory framework for the cryptocurrency industry at the federal level, allocating oversight responsibilities between the CFTC and other regulators and setting rules for market participants including DeFi protocols and stablecoin issuers.
What does the new "non-DeFi protocol" definition mean for accounting?
Entities that meet the definition will be required to register with the CFTC. For accounting purposes, interacting with a CFTC-registered trading venue carries different disclosure, internal control, and potentially different asset classification obligations than interacting with an unregulated or genuinely decentralised protocol. Firms should begin mapping their protocol relationships against the bill's control test now.
How does the stablecoin rewards dispute affect USDC accounting?
The unresolved treatment of stablecoin rewards means accounting policy for yield-bearing stablecoin positions such as USDC remains contingent on the final statutory and regulatory outcome. CFOs should maintain parallel accounting policy scenarios covering at least an interest income model and a non-interest yield model, ready to implement once the legislation and subsequent rulemaking provide clarity.
Is the Clarity Act certain to pass after the September 15 vote?
No. The September 15 vote is a procedural step, not a final passage vote. Significant disputes remain unresolved, including ethics language related to President Trump's crypto holdings and the stablecoin rewards question. The outcome of the procedural vote will signal whether the bill has a realistic path in the current legislative session.
What should auditors do now given the bill's proposed on-chain governance test?
Auditors should start designing evidence-gathering procedures for on-chain governance data: voting records, upgrade histories, multisig configurations, and similar artefacts. These will be needed to support any assertion that a protocol qualifies as truly decentralised under the bill's framework, and building that capability ahead of enactment reduces audit risk and timeline pressure significantly.
Source: The Block