Why writing open-source code is suddenly an existential risk, and the five-page bill designed to fix it

Two senators introduced the five-page Blockchain Regulatory Certainty Act of 2026 to clarify that "non-controlling" developers and infrastructure providers of blockchain software should not be classified as money transmitters under federal law. This addresses the existential risk faced by developers whose open-source code is being aggressively targeted by prosecutors, exemplified by the Tornado Cash co-founder case, under existing regulations written for traditional payment intermediaries.

The bill focuses on defining a "non-controlling" developer as someone who lacks the legal right or unilateral ability to move users' funds, aiming to create a statutory safe harbor where publishing code is distinct from custody. While FinCEN guidance exists, advocates seek a clear rule because guidance is subject to reinterpretation, especially when facing expansive state licensing statutes or criminal prosecution theories.

The legislation attempts to preserve foundational open-source work while still allowing enforcement against actors who actually handle customer money. If passed, it would narrow the narrative space for regulators and incentivize system architects to minimize control features. However, the success depends on how clearly the term "non-controlling" applies to complex, real-world systems that often mix open-source components with managed services, forcing a clearer legislative boundary between writing code and moving money.

(Source：CryptoSlate)