COURT SLAPS DELAWARE FIRM IN CRYPTO IP FIGHT
Delaware’s Superior Court just handed down a win that could ripple through how crypto projects protect their code and who actually owns the intellectual property behind their tokens. The ruling came in a contract and trade-secret dispute between Diamond Fortress Technologies and its former executive, Charles Hatcher II, and the decision tightens the screws on how Delaware companies must document ownership of blockchain-related innovations.
The case began when Diamond Fortress accused Hatcher of misappropriating proprietary software and trade secrets tied to a crypto-security platform the pair had developed together. Hatcher claimed the technology belonged to him personally or to a separate venture, triggering a lawsuit over breach of contract, conversion, and misappropriation. The court was asked to decide whether the company’s internal agreements and assignment clauses actually transferred the rights to the disputed code and whether Hatcher’s post-departure use of that code violated Delaware law.
Judges ruled that Diamond Fortress held clear ownership under the operative contracts and that Hatcher’s continued exploitation of the technology amounted to misappropriation. The company emerged the victor on the core claims, securing both injunctive relief and potential damages, while Hatcher lost the right to commercialize or license the contested materials. The decision leaves little room for similar disputes to be resolved on “he said, she said” arguments once written agreements exist.
In plain English, Delaware courts will treat signed IP-assignment clauses as ironclad even when the asset is crypto code, meaning founders who leave a project cannot simply walk away with the tech and launch a clone. Any ambiguity in those contracts now carries heavier legal and financial risk for departing executives.
The ruling nudges crypto projects toward tighter corporate housekeeping: clear IP assignments reduce the chance that a single engineer can fork a protocol and claim ownership, but it also raises the stakes for token projects that rely on open-source contributions or informal founder arrangements. Exchanges and DeFi protocols that integrate such code could face secondary liability if a court later finds the underlying rights were never validly transferred, injecting fresh diligence costs into token listings and partnership deals.
Founders who skip airtight IP paperwork are inviting Delaware courts—and potentially the SEC—to treat their tokens as unregistered securities built on disputed foundations.