Delaware Court Rules Crypto Code Can Still Be a Trade Secret on a Public Blockchain
Court Hands Diamond Fortress a Win Over Crypto Rival in Delaware
A Delaware judge just cleared the way for a crypto-linked firm and its founder to press claims against a former partner accused of misusing confidential code and trade secrets. The ruling matters because it signals that state courts will treat digital-asset technology as protectable property and are willing to police competitive foul play even when the underlying product is blockchain-based.
The dispute erupted after Charles Hatcher II and Diamond Fortress Technologies parted ways with a company they say had agreed to integrate their facial-recognition software into a cryptocurrency platform. Plaintiffs claim the partner copied their proprietary algorithms, rebranded the code, and launched a competing token project without paying royalties or honoring the joint-development deal. Defendants moved to dismiss, arguing the claims were too vague and that any ideas at issue were not truly secret once posted to a public blockchain.
Superior Court Judge Paul R. Wallace refused to toss the case. He found the complaint detailed enough to show both the existence of protectable information and the likelihood that defendants used it without permission. The judge also rejected arguments that blockchain’s transparency automatically destroys secrecy, holding that the specific implementation steps and optimization methods allegedly copied could still qualify as trade secrets. Because the conduct occurred inside Delaware’s borders and the contracts invoked Delaware law, the court decided it had jurisdiction and that the claims could proceed to discovery.
In plain terms, the decision tells founders and coders that ideas turned into working crypto software are not fair game for copying simply because the end product sits on a public ledger. Companies that sign joint-development deals or NDAs now face real litigation risk if they try to bolt with the tech, and plaintiffs gain leverage to force document exchanges that could expose internal token launches and token-distribution plans.
For markets, the ruling quietly strengthens Delaware’s hand as the go-to venue for crypto-related contract fights, potentially pulling more disputes away from federal securities regulators and into state commercial courts. It also adds another layer of legal armor around code that exchanges or DeFi protocols might license, raising the cost of “inspired” clones and making due-diligence reviews of token provenance more important. Traders should watch whether similar suits surface; a wave of them could chill quick-copy launches while rewarding projects that lock down their intellectual property early.
Bottom line: Delaware just made it slightly harder—and legally riskier—to swipe someone else’s crypto code and call it your own.
