Delaware Court Narrows Crypto Code Ownership in Diamond Fortress v. Hatcher: Written Contracts Now Required
Diamond Fortress Ruling Shakes Up Crypto Contract Battles
Delaware Superior Court just handed down a decision that could change how crypto companies handle disputes over code, contracts, and ownership rights. The ruling in Diamond Fortress Technologies v. Hatcher is not about crypto tokens or exchanges, but it directly affects the legal scaffolding that many DeFi protocols, token issuers, and exchanges rely on when they draft Delaware-governed agreements. With most crypto firms incorporating in Delaware, this case could become the first stop in future legal fights over smart-contract ownership and trade-secret claims.
The case started when Diamond Fortress Technologies and its founder Charles Hatcher sued a former business partner over the alleged misappropriation of proprietary blockchain-based identity software. The plaintiffs claimed the defendant had taken code, customer relationships, and trade secrets to build a competing product. The defense countered that the software in question was jointly developed and that no enforceable contract or confidentiality agreement existed to bar its use. The legal question before the court was whether Delaware contract law could enforce ownership claims in a fast-moving, open-source–adjacent crypto project where formal agreements were thin or informal.
The court ruled that the plaintiffs failed to show a clear contractual assignment of rights or a binding non-compete, and that vague oral understandings were not enough to restrict the defendant’s use of the technology. The judge dismissed most claims, but allowed a narrow trade-secret count to survive, signaling that Delaware courts will still protect genuinely secret code if companies can prove reasonable secrecy measures were in place. In practical terms, Diamond Fortress lost its broad ownership hammer, while the defendant can continue development unless the remaining claim succeeds at trial.
Translated into plain English, the decision tells crypto startups that Delaware incorporation alone does not give founders or companies automatic control over jointly built technology. Without crisp written contracts, equity agreements, or documented assignment of code rights, courts will treat contributions as shared. That raises the bar for any team hoping to lock up blockchain IP through handshake deals or GitHub commits.
For markets, the ruling tilts power toward individual developers and away from parent companies that treat Delaware charters as a blanket ownership shield. It could slow token launches if teams fear future disputes over who actually owns the protocol code, and it may push exchanges and DeFi projects to demand iron-clad contributor agreements before integrating new software. Regulators watching the space will note that Delaware courts are willing to step in on ownership, but only when contracts are clear; this limits the SEC’s ability to lean on state-law gaps to expand its reach over code itself.
The case is a warning flare: if your crypto project lives in Delaware, paper your ownership stakes now or risk watching your code walk out the door.
