The SEC Crypto Safe Harbor Proposal: Rule 400 and Form TR
Quick answer. Proposed Rule 400 would deem a token's investment contract ended once the issuer completes or permanently ceases its promised efforts, makes no new promises and files Form TR. It is not adopted.
Video transcript
Proposed Rule 400 would let a token issuer declare, publicly, that its investment contract has ended. It is not adopted yet, but the evidence it asks for is largely technical.
The rule has two conditions. The issuer has completed or permanently ceased the essential managerial efforts it promised, with no new promises. And it files a transition report on Form TR.
Form TR carries a description, a certification, and an analysis clear enough for a reasonable investor to follow. The SEC need not review it, but could still challenge it.
Per SEC staff guidance, handing the roadmap to a foundation or DAO does not end the contract. Maintaining a functional system is different.
Delivery is judged against the issuer's own definitions, not a general market idea of decentralization.
So the evidence is technical: each promise mapped to deployed code, bytecode matched to the audited commit, every privileged role and key, and who can still upgrade.
The safe harbor holds only while its conditions do. New promises or new powers, like a role grant or an upgrade, can reverse the analysis. Monitor them and keep a dated log.
Guardian builds this record and monitors it on every block after filing. Your counsel owns the certification. Read the full article, or talk to Guardian.
The SEC crypto safe harbor proposal would let an issuer state, on the public record, that the investment contract around its token has ended.
Proposed Rule 400 would codify the Commission's March 2026 interpretation. A crypto asset separates from an investment contract once the issuer has fulfilled its promises, or once purchasers could no longer reasonably expect it to.
Comments closed on October 20, 2026, and the rule may change before adoption. Issuers can still prepare now, because many of the facts Form TR asks for are technical.
This article explains the technical and security side of the SEC's proposed Regulation Crypto Assets, Rule 400 and Form TR. It is not legal advice; confirm how it applies to you with counsel.
Rule 400's Two Conditions
As proposed, a covered investment contract would be deemed to have ceased to exist when both conditions are met.
- (a) Efforts done. The issuer has completed or otherwise permanently ceased all promised essential managerial efforts. It is not making and does not intend to make new promises.
- (b) Form TR. The issuer files a transition report on Form TR with the Commission.
The crypto asset would then be deemed not subject to the contract, for the Securities Act and Exchange Act definitions of security.
From the release:
- It is a non-exclusive safe harbor. An asset can fall outside the securities laws without it.
- It is open to issuers that used the proposed startup or fundraising exemptions, and to those that did not.
- The Commission could still challenge whether an issuer met the conditions.
- Other parties could still assert that the asset is a security.
- Neither the Commission nor its staff would have to review a Form TR. Filing satisfies the requirement.
What Form TR Asks For
Form TR would serve the startup exemption, the fundraising exemption and the safe harbor. It would be filed on EDGAR, in HTML.
Under the startup exemption, it is due no later than four years after the notice of reliance.
| Track | Items | Content |
|---|---|---|
| All filers | Issuer information | Name, jurisdiction, address, telephone and email |
| Rule 400(a) satisfied | Items 1 to 3 | Description of the security and asset; certification; supporting analysis |
| Rule 400(a) not satisfied (Rule 200(e) startup report) | Items 4 to 6 | Description; current status and plans; analysis if the contract ceased anyway |
The release says the analysis should let a reasonable investor understand how the issuer made its determination. Issuers would refer to their Rule 103(b)(1) disclosure of promises and progress.
A Form TR would also serve as the widely disseminated, unambiguous public announcement the Interpretive Release describes.
Whether to require the analysis at all, or allow a bare certification, was itself a question for comment.
Why a Hand-Off Does Not Count
Rule 400(a) tracks two routes from the Interpretive Release.
- Completed. The issuer fulfilled its promises, such as features, roadmap milestones or open-sourcing code.
- Ceased. Purchasers could no longer reasonably expect performance, for example if the issuer effectively abandons development.
Handing the roadmap to someone else is neither. Under staff FAQ 2.2, separation would not occur where another party assumes the issuer's promises.
On the staff's reading, moving unfinished promised work to a foundation, a development company or a DAO-funded team would not end the contract.
Maintenance is different. Under FAQ 2.3, services to secure, maintain, improve or enhance a functional system would not involve essential managerial efforts.
The line runs between delivering what was promised and maintaining what was delivered. Our post on security work after launch covers the second.
The Technical Record Behind the Analysis
Delivery is judged by the issuer's own words. If it promised decentralization, the test is how the issuer defined it, not a general market conception.
If the promises were technical, so is the evidence.
| Evidence | What it shows | Where it comes from |
|---|---|---|
| Promise-to-code map | Each promised feature or milestone is live, at a stated address and commit | Offering materials, verified source, deployment transactions |
| Deployment verification | Deployed bytecode matches the reviewed commit | Bytecode comparison, audit reports |
| Role inventory | Every privileged function and its current holder | Contract state and role-grant events |
| Key status | EOA, multisig threshold and signers, timelock delay, governor or none | Safe owners and threshold, timelock settings |
| Ownership transfers | When and how issuer keys left, with transaction hashes | Ownership-transfer and role-revocation events |
| Upgrade authority | Who can change the code today | Proxy admin owner, upgrade authorization |
| Supply mechanics | Who can mint or burn, matching the economics disclosure | Minter roles and caps |
For issuers that used the exemptions, proposed Rule 103(b) disclosures are the starting point. They cover promises and progress, the development plan, security, supply mechanics, governance and permissions.
Build the analysis as a trace: each disclosed promise, its acceptance test, the deployed contract that meets it, and dated evidence.
Where (b)(8) described permissions, the role inventory should show what changed before the filing.
The same record informs the central party test. Under FAQ 2.4, once a functional system has no central party, issuer statements likely would not create a new investment contract.
That bears on Rule 400(a)'s no-new-promises limb. Our central party explainer maps FAQ 1.5's powers to code.
Keeping the Facts True After Filing
The safe harbor would apply only to the extent an issuer satisfies its conditions.
If an issuer misrepresents, intentionally or otherwise, that it has met Rule 400(a), the Commission may take the position that the contract has not ceased.
Two kinds of drift can undo a filing.
- New promises. Review roadmaps, token communications and buyback language against the no-new-promises limb.
- New powers. A role grant to an issuer address, a new Safe module or a reintroduced admin function can reverse the facts.
Monitor role, ownership and upgrade events continuously, and keep a dated log.
How It Relates to the CLARITY Act
The Digital Asset Market Clarity Act, H.R. 3633, is not law. Its bill status record was last updated September 17, 2026.
The House passed it on July 17, 2025, 294 to 134. The Senate Banking Committee reported it with a substitute amendment on June 1, 2026.
On September 15, 2026, the Senate did not invoke cloture on the motion to proceed (49 to 50). A motion to reconsider was entered.
The House text uses a control test closer to FAQ 1.5 than to Rule 400. A mature blockchain system is one not controlled by any person or group under common control.
An issuer or others could certify maturity, and the SEC would have 60 days to rebut. The Senate committee's substitute replaces that framework with ancillary asset provisions.
For evidence, the point is practical. Rule 400 asks whether the issuer has finished; the House bill asked whether anyone controls the system. One role-and-key record answers both.
How Guardian Builds the Evidence
Guardian's regulatory and compliance work packages this record as technical evidence, each artifact tied to the commit or date it was produced at.
It includes deployment verification against the audited commit, and a privileged role and upgrade path map with each holder, threshold and timelock.
Contract configuration drift dates every change to roles, parameters and upgrades. After filing, Managed Security monitors role, ownership and upgrade events on every block.
Your counsel owns the certification and the legal analysis.
Frequently Asked Questions
What is the SEC's proposed crypto safe harbor?
Proposed Rule 400 would deem a covered investment contract to have ceased to exist. The issuer must have completed or permanently ceased its promised efforts, make no new promises, and file Form TR.
Is Rule 400 in effect?
No. Regulation Crypto Assets, Release No. 33-11434, was proposed on August 18, 2026. The comment period closed on October 20, 2026, and the rule has not been adopted.
What goes in a Form TR?
Issuer information, a description of the covered investment contract and crypto asset, a certification that Rule 400(a) is satisfied, and an analysis a reasonable investor could follow.
Does handing development to a foundation end the investment contract?
No. Under SEC staff FAQ 2.2, separation would not occur where another party assumes the issuer's promises, affirmatively or by operation of law. Maintaining a functional system is a separate matter under FAQ 2.3.
Sources
- Federal Register: Regulation Crypto Assets, proposed rule, Release No. 33-11434, 91 FR 54510 (Aug. 21, 2026)
- Federal Register: Release No. 33-11412, Application of the Federal Securities Laws to Certain Types of Crypto Assets, 91 FR 13714 (Mar. 23, 2026)
- SEC Division of Corporation Finance: Frequently Asked Questions on the Application of the Federal Securities Laws to Certain Types of Crypto Assets (issued Sept. 25, 2026; updated Nov. 2, 2026)
- GovInfo: H.R. 3633, Digital Asset Market Clarity Act of 2025, engrossed in House
- GovInfo: H.R. 3633, reported in Senate with an amendment (June 1, 2026)
- GovInfo: H.R. 3633 bill status record (updated Sept. 17, 2026)
Build the evidence behind a Form TR
Guardian produces dated, commit-pinned evidence of what you deployed and who can still change it, ready for your counsel's analysis.