SEC Commissioner Hester Peirce just told open-source blockchain developers they are protected by the First Amendment, not securities law.
Speaking at the IC3 Blockchain Camp at Princeton University on June 2, 2026, Peirce drew a constitutional line the agency has never explicitly drawn before: publishing open-source code is speech, and speech is not subject to the SEC's registration requirements. "Many blockchain projects involve publishing open-source software, which is generally a protected activity under the First Amendment," Peirce said.
The statement attacks the legal theory that has powered years of SEC enforcement actions against protocol developers. For the first time, a sitting commissioner has argued that the act of writing and releasing code occupies an entirely different category from the financial intermediation the agency was built to regulate.
The rulebook was built for people, not protocols
Peirce's core argument is structural. The SEC's entire regulatory apparatus assumes a human intermediary—someone who takes custody, executes trades, or offers advice. "The SEC's rulebook is full of intermediaries: brokers, dealers, exchanges, clearinghouses, transfer agents, investment advisers and investment companies," she said.
Open-source code fits none of those categories. It is infrastructure. A developer who publishes a smart contract to a blockchain and walks away is not performing any of the functions that trigger registration. The code executes itself. No one collects a spread. No one processes redemptions.
This is a direct challenge to the logic behind cases like the SEC's action against LBRY and its scrutiny of Uniswap Labs. In those enforcement efforts, the agency treated the publication of code as functionally equivalent to operating an unregistered exchange or issuing an unregistered security. Peirce's Princeton remarks repudiate that equivalence. Responsibility for securities law violations, she argued, should rest with the individuals who engage in unlawful conduct, not with developers who publish code others may misuse.
The staff guidance that telegraphed the shift
Peirce's speech did not come out of nowhere. It followed SEC staff guidance suggesting that some DeFi interfaces may not qualify as brokers under existing rules. Staff guidance carries no legal force, but it signals where the agency's interpretive machinery is heading.
A commissioner's public remarks carry a different weight. They are political. They shape the Overton window for what the enforcement division can credibly pursue. When a commissioner says, on the record, that code publication is protected speech, it becomes materially harder for enforcement attorneys to argue the opposite in federal court.
The combination of staff guidance and commissioner speech suggests internal momentum toward codification. Peirce has been pushing this direction for years. Her Safe Harbor 2.0 proposal, a draft rule that would give token projects a three-year exemption from registration to achieve decentralization, has sat on GitHub with 186 stars and 49 forks—a policy proposal in code-repository form.
At a Crypto Task Force roundtable on DeFi in June 2025, she sharpened the distinction further. "DeFi is not a place people go to access services that someone else provides and controls; it is software code that people use to engage in the activity of transacting without a centralized intermediary," she said.
Why the First Amendment changes the legal terrain
Peirce is applying a specific legal mechanism, and it is one with Supreme Court precedent behind it. In Bernstein v. Department of Justice, the Ninth Circuit held that encryption source code is expressive conduct protected by the First Amendment. The logic extends naturally to blockchain software: code is a written language that instructs a machine, and writing it is an act of expression.
If publishing code is speech, then liability for how others use that code evaporates. The developer of an open-source lending protocol is not running a bank. They wrote instructions. Someone else chose to follow them. That distinction matters enormously under the Howey test, which asks whether an investor is relying on the efforts of a promoter to generate profits. A promoter who publishes code and disappears is not making any ongoing effort. The code is doing the work.
This is not a fringe theory. It aligns with a broader First Amendment jurisprudence that has protected software publication for decades. What Peirce is doing is applying that settled doctrine to a regulatory agency that has behaved as though the doctrine does not exist.
The no-action letter that reshapes DeFi
Within 12 to 24 months, the SEC will likely issue a formal no-action letter or interpretive guidance codifying Peirce's view. The political foundation is being laid now. The legal foundation has existed since Bernstein. What remains is the institutional courage to make it binding, and Peirce's speech is designed to create that courage by demonstrating that the argument can be made publicly without collapsing.
Here is the mechanism. A no-action letter works by stating that the SEC staff will not recommend enforcement if a party engages in specific conduct. For a developer, that conduct would be publishing open-source code without operating an intermediary business. The letter creates a safe harbor that is not law but functions as law because no one gets sued for following it. Once issued, it becomes the de facto standard. Enforcement attorneys cannot easily bring cases that contradict it without risking judicial skepticism and internal reputational damage.
The first-order consequence is immediate: enforcement actions against pure protocol developers stop. The SEC redirects its firepower toward the intermediaries that Peirce's rulebook was actually designed to regulate—brokers, exchanges, and token issuers who take custody, collect fees, or make promises about future profits.
The second-order consequence is a capital reallocation. Developers who left the United States or abandoned open-source work return, because the chilling effect that drove protocol development offshore reverses. Law firms that specialize in First Amendment tech defenses see a wave of new clients. Protocol token holders gain a measure of regulatory clarity that has been absent since the DAO Report of 2017.
The third-order consequence is where the real disruption lands. Centralized DeFi front-ends that blur the line between code and service face heightened scrutiny. If the safe harbor narrows to cover only pure code publication, any project that operates a website, collects a fee, or exercises discretion over user funds falls outside the protected zone. The SEC's enforcement staff, who built careers on the theory that code itself can be a security, see their primary weapon dismantled. The agency does not shrink—it pivots. The war on developers ends. The war on intermediaries intensifies.
By mid-2028, this view will be codified. The falsification condition is clear: if no no-action letter or interpretive guidance emerges by June 2028, and if enforcement actions against pure protocol developers continue at their current pace, then Peirce's speech was a signal without follow-through. But the trajectory of staff guidance, commissioner speech, and the Bernstein precedent suggests otherwise.
What to do now
Developers should structure projects as pure code publication with clear disclaimers. Avoid any intermediary function: no front-end fee collection, no governance token sales that resemble underwriting, no promises of future development effort. The closer a project looks to a person providing a service, the farther it falls from Peirce's safe harbor.
Investors should reallocate capital toward protocols with minimal intermediary features. The assets that survive the coming regulatory sorting will be those where the code is the product, not the wrapper around a human-controlled business.
Law firms should prepare First Amendment defenses for developer clients now. The Bernstein precedent is strong, but it has never been tested against the SEC's securities authority. That test is coming, and the firms that have done the work in advance will own the market.
Regulators should watch for Peirce's next move. A formal proposal within six months is plausible. A no-action letter within a year is likely. The direction of travel is set.
The code is not the crime
Peirce's message is simple and radical in its implications: publishing code is speech, and speech is not a security. The burden shifts to those who use the code to commit fraud. The SEC's theory that writing software is a regulated activity has just lost its most articulate internal opponent.
The agency will not stop policing crypto. It will stop pretending that a developer and a broker are the same thing. The pen is not a security.
