The takeaway in 30 seconds: On August 18, 2026, the SEC proposed “Regulation Crypto Assets”, a tailored securities-offering framework for certain investment contracts involving crypto assets (SEC, August 18, 2026). It builds directly on the March 2026 interpretation that sorted crypto into categories and clarified when a token is a security. The new proposal adds two registration exemptions for crypto offerings and, most consequentially for advisers, a conditional safe harbor that would let a crypto asset stop being treated as a security once an issuer completes the managerial efforts it promised. For RIAs, the offering exemptions are mostly an issuer story, but the safe harbor is the piece that matters because it means a token’s classification can change over time, and a compliance program that classified a holding once and filed it away is now tracking a moving target.
Earlier this year, we looked at the SEC’s March 2026 interpretation, the one that sorted crypto assets into categories and clarified when a token functions as a security versus a commodity, a collectible, a tool, or a stablecoin. The practical takeaway then was that RIAs advising on crypto needed to classify their holdings and understand that classification drives everything downstream: custody, disclosures, marketing, reporting.
Regulation Crypto Assets, proposed August 18, is the next step in that arc. Where the March interpretation explained how the law applies, this proposal starts building the machinery, concrete pathways for crypto issuers to raise capital under the securities laws, and, crucially, a mechanism for a crypto asset to move out from under securities treatment when specific conditions are met.
Most of the proposal is aimed at issuers. But one part reaches directly into how RIAs have to think about the crypto their clients hold, and it’s worth understanding the whole framework to see why.
What the Proposal Actually Does
Regulation Crypto Assets has three moving parts. Two are primarily issuer-facing; the third is the one advisers should focus on.
Two registration exemptions for crypto offerings. The proposal creates tailored exemptions from Securities Act registration for certain crypto investment-contract offerings (SEC, August 18, 2026):
- A one-time exemption permitting offerings of up to $5 million over a four-year period, with principles-based narrative disclosures required.
- A larger exemption permitting offerings of up to $75 million per 12-month period, which additionally requires financial statements and ongoing reporting.
These are designed to give crypto entrepreneurs a domestic, legal pathway to raise capital, addressing the SEC’s stated concern that the previous lack of clarity pushed issuers offshore. For most RIAs, this part is context, not a direct obligation: it shapes the universe of crypto products that may come to market, but it doesn’t impose anything on advisers directly.
A conditional safe harbor from “investment contract” status. This is the part that matters for advisers. The proposal includes a conditional safe harbor from the term “investment contract” in the definition of “security.” If an issuer satisfies the conditions, completing or permanently ceasing all the essential managerial efforts it represents it would undertake, then the crypto asset would be deemed not subject to an investment contract, and therefore not a security under that definition. (SEC, August 18, 2026).
In plain terms: a token that is a security today can stop being one, if and when the issuer finishes the work that made it a security in the first place. Classification isn’t necessarily permanent.
State-law preemption. The proposal would also preempt state securities registration and qualification requirements for offerings made under these exemptions and for certain secondary-market transactions, reducing the state-by-state patchwork for qualifying crypto offerings.
Why the Safe Harbor Is the Part RIAs Should Care About
The March interpretation established that crypto classification matters. The safe harbor establishes that classification can change, and that’s a meaningfully harder thing for a compliance program to handle.
Under a world where a token’s status is fixed, an RIA classifies a holding once and the classification stands. Under the proposed safe harbor, a token that was a security when the client acquired it could later cease to be one, once the issuer completes its promised managerial efforts. The reverse dynamic from the March interpretation is also in play: a non-security token can become subject to an investment contract if an issuer makes the wrong kind of promises. Put together, classification becomes a status that can shift in either direction over the life of a holding.
For an adviser, that changes the nature of the obligation. Classifying crypto holdings is no longer a one-time intake task. It’s an ongoing monitoring responsibility. The compliance question shifts from “what is this token?” to “what is this token now, and does our record reflect the current status or a stale one?” A holding classified as a security two years ago, whose issuer has since completed its roadmap and qualified for the safe harbor, may now sit in the portfolio under an outdated classification that drives outdated compliance treatment, including the wrong custody assumptions, the wrong disclosures, and the wrong reporting.
This is the subtle exposure the proposal creates for honest, careful firms: not that they’ll misclassify a token today, but that a correct classification will quietly go stale as the token’s status evolves and nobody revisits it.
What This Means Practically for RIAs With Crypto Exposure
None of this is final. It’s a proposal with a 60-day comment period, and the framework will likely evolve before it settles. But the direction is clear enough to act on the thinking now, especially because it compounds the classification work the March interpretation already set in motion.
Three practical implications for any RIA whose clients touch crypto.
Classification becomes a monitored status, not a one-time determination.If the safe harbor is adopted, the firm needs a way to track not just what each crypto holding is classified as, but whether that classification is still current. That requires knowing when an issuer’s managerial efforts are completed or ceased, the trigger for the safe harbor. That’s a monitoring obligation the firm didn’t have when classification was treated as fixed.
The compliance treatment has to follow the classification as it changes. Custody, disclosures, marketing, and reporting all flow from whether a holding is a security. If a token’s status changes, the compliance treatment has to change with it, and the firm has to be able to document that it tracked the change and adjusted accordingly. A static classification driving static treatment is exactly the gap an examiner would probe as this framework matures.
The documentation of classification decisions matters more, not less. As classification becomes dynamic, the firm’s recordkeeping of why it classified a holding a given way, when, and on what basis becomes the evidence that its treatment was reasonable at each point in time. A defensible classification with no documented basis, or one that was never revisited as circumstances changed, is the weak point.
The through-line connects directly to where the March interpretation left off: crypto compliance for RIAs is becoming less about a single classification call and more about maintaining an accurate, current, documented picture of holdings whose regulatory status can move. The framework is adding clarity and, with it, a monitoring burden that rewards firms whose recordkeeping can keep pace.
What to Do With This
This is a proposal, not a rule, and nothing requires action today. But it’s the clearest signal yet of where crypto compliance is heading for advisers, and a few things are worth doing now.
- Revisit your crypto classification approach in light of a moving target. If you built a classification process after the March interpretation, ask whether it assumes classification is permanent.If it does, it has a gap the safe harbor would widen, because the proposal makes clear that status can change over a holding’s life.
- Confirm you could detect a classification change, not just record an initial one. For each crypto holding in client accounts, ask: would your firm know if this token’s regulatory status changed, if its issuer completed the managerial efforts that would trigger the safe harbor? If the answer is “we classified it once and haven’t looked since,” that’s the monitoring gap to close.
- Strengthen the documentation behind each classification. Make sure each classification decision has a recorded basis and date, so that as status evolves, the firm can show its treatment was reasonable at each stage. This is the evidence that protects the firm as the framework matures.
- Consider commenting. The SEC is taking input for 60 days. An RIA with a practical view on how a dynamic classification regime would work in advisory practice has a window to put it on the record while the framework is still being shaped.
The March interpretation told RIAs that crypto classification matters. Regulation Crypto Assets is beginning to tell them that classification moves. The firms that come through the maturing framework cleanly will be the ones that treat crypto holdings not as classified once and filed away, but as a living picture kept current as the regulatory ground underneath each token shifts. That’s exactly what the emerging framework, taken as a whole, is going to require.
