A DeFi protocol launches with a creative brand, a novel automated market-maker mechanism and a governance token that coordinates community decisions. Six months later, the founding team discovers that a competitor has filed a trademark application in three major markets, a patent examiner has rejected a blockchain-method claim as abstract, and an NFT licensee is asserting unlimited commercial rights to derivative works. The legal question is how to protect innovation and brand identity in an environment built on open-source composability, pseudonymous contributions and cross-border deployment. Under the applicable intellectual-property frameworks, the answer turns on where and how rights vest, what a blockchain architecture makes enforceable, and whether the project's open posture conflicts with exclusive rights. This page maps trademark strategy, patentability constraints, open-source licence compatibility and the IP dimensions of NFTs, so that Web3 businesses structure protection before the first infringement surfaces.
The analysis below addresses the regimes that govern brand, invention and code in digital-asset projects. It explains the decision points where founders choose between defensive publication and patent filing, where trademark classes align with on-chain activity, and where an open-source licence imposes obligations that a proprietary wrapper cannot reverse. The guidance is built for operators who understand protocol mechanics and need the legal framework that sits around them.
Trademark strategy for Web3 brands
A Web3 trademark claim succeeds when the mark identifies the commercial source of a service or good, is used in commerce, and does not conflict with prior rights. The application routes through national trademark offices or regional systems – the European Union Intellectual Property Office for an EU-wide mark, the United States Patent and Trademark Office for US protection, the UK Intellectual Property Office post-Brexit, and corresponding offices in Singapore, the UAE, Hong Kong, Switzerland and other flagship jurisdictions. There is no global trademark registry; protection is territorial, and a mark filed in one jurisdiction grants no automatic right in another.
For a protocol or exchange, the relevant Nice Classification classes typically include Class 9 (software, mobile applications, blockchain-related software), Class 36 (financial services, digital-asset exchange, custody services), Class 42 (software-as-a-service, platform hosting, technical support), and Class 41 if the project includes educational or community events. The applicant must demonstrate genuine use in each claimed class within the grace period prescribed by the jurisdiction. A token name, a protocol brand and a DAO identifier can each be separate trademarks if they function as source identifiers; filing early, before public launch, protects the priority date and prevents squatters from registering confusingly similar marks in competing jurisdictions.
In our cross-border practice, operators building multi-region user bases routinely file defensive applications in the EU, the US, the UK, Singapore and the UAE in parallel, because a strong brand in one hub offers no protection when a copycat registers the same name in an adjacent market. The USPTO and EUIPO each publish opposed and granted marks in searchable databases, so a clearance search before launch surfaces existing conflicts. Where a conflict exists, the project may negotiate a coexistence agreement, rebrand, or argue that the goods and services are sufficiently distinct – but rebranding after a community has formed around a name is expensive and reputationally damaging. A clearance opinion before the first public use is faster and cheaper than a post-launch opposition.
Common mistakes include filing only in the founder's home jurisdiction, selecting classes that do not cover the actual on-chain activity (a DeFi protocol filing only Class 9 software but not Class 36 financial services), and launching a brand publicly before the application is filed, which can forfeit priority or trigger prior-use defenses in some jurisdictions. Another mistake is treating a DAO's decentralised governance as incompatible with trademark ownership – in reality, the trademark is held by a legal wrapper entity (a foundation, a traditional company, a DAO LLC where recognised), and the DAO's off-chain governance determines brand-use policy. The trademark office will not register a mark to "the community" as an amorphous holder.
For a scoped brand clearance and filing strategy that aligns trademark classes with your Web3 business model and anticipated jurisdictions, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts – the entity structure, the user geography, the service layers – change the filing roadmap and the priority queue.
Patentability of blockchain methods and defensive publication
A blockchain-related invention is patentable if it is novel, non-obvious and produces a technical effect beyond the abstract idea of using a computer to implement a business method. The United States Patent and Trademark Office, the European Patent Office and the patent offices of major Web3 hubs apply subject-matter tests that reject pure software and business-method claims lacking a concrete technical improvement. In the US, the Alice/Mayo framework (following Alice Corp. v. CLS Bank International) holds that an abstract idea implemented on a blockchain is not patentable unless the claim recites a specific technical solution – for example, a novel consensus mechanism that reduces latency through a defined architectural change, rather than the generic concept of "using a distributed ledger to record transactions."
The EPO's approach, under the European Patent Convention, similarly requires that the invention solve a technical problem: a smart-contract execution model that demonstrably reduces gas consumption through a new opcode sequence may be patentable, while a claim to "tokenising an asset" without a concrete technical advance will be refused. Patent offices in Singapore, Hong Kong, Switzerland and other common-law or civil-law jurisdictions apply variants of these tests, all converging on the requirement that the invention be more than an automation of a known process.
Defensive publication is the alternative to patent filing. A project that publishes technical detail in a peer-reviewed journal, a technical blog with a timestamp, or a dedicated prior-art registry (such as IP.com or a blockchain-based publication platform) establishes prior art that blocks later patent applicants from claiming the same method. This strategy preserves the project's freedom to operate without the cost, disclosure obligations and territorial limitations of a patent. A patent grants exclusive rights for a defined term but requires public disclosure of the invention's workings, which in a composable DeFi environment may accelerate competitor forks.
In a recent matter, a DeFi team assessed whether to file a patent on a liquidation-auction mechanism or publish defensively; we modelled the enforceability risk against copycat protocols, the cost of prosecution in five jurisdictions, and the likelihood that an examiner would reject the claim as abstract. The decision turned on whether the team intended to license the method commercially or to keep it open for ecosystem adoption. Where the goal is adoption, defensive publication is faster and cheaper; where the goal is exclusive commercial control, a patent application in the core markets – conditioned on prior-art clearance – is the protective route.
Open-source licences and smart-contract code
Smart-contract code is copyrightable as a literary work, and the copyright holder may release it under an open-source licence that permits use, modification and redistribution subject to the licence's terms. The choice of licence determines the project's composability posture and the obligations that downstream users inherit. The MIT Licence and the Apache 2.0 Licence are permissive: they allow commercial and non-commercial use with minimal restrictions, requiring only that the licence text and copyright notice accompany distributions. The GNU General Public Licence (GPL), in its version 3 form, is copyleft: any derivative work must be released under the same GPL terms, a requirement that can conflict with proprietary business models or with the integration of GPL code into a closed protocol layer.
A protocol that combines permissive and copyleft code must audit the dependency tree to ensure licence compatibility. The GPL's virality does not extend to code that merely interacts with a GPL-licensed contract through a public interface – calling a function on-chain is use, not derivation – but forking and modifying the contract code does create a derivative work governed by the original licence. Where a project's token-sale terms or service agreements assert proprietary rights over the protocol, but the core contracts are released under GPL, the legal positions conflict, and a court or arbitrator will resolve the conflict by reference to the intent expressed in the licence and the actual control the proprietary wrapper claims.
For NFT projects, the copyright in the underlying artwork and the licence granted to the token holder are separate. Purchasing an NFT does not automatically confer copyright in the image; the project's terms of use define whether the holder may reproduce, display or create derivatives. Some projects grant full commercial rights; others permit personal display only. A holder who mints derivative works or licenses the image for merchandise without the requisite grant from the original creator risks copyright infringement. The fact that the NFT is transferable on-chain does not expand the IP licence beyond what the creator specified.
The decision matrix for Web3 builders is as follows. A project prioritising rapid ecosystem adoption and composability selects MIT or Apache 2.0, accepts that competitors will fork the code, and competes on brand, user experience and network effects. A project seeking to restrict commercial forks or to require reciprocal openness selects GPL, but must accept that the copyleft obligation constrains later proprietary pivots. A project asserting proprietary control releases only binaries or maintains the source in a private repository, at the cost of reduced developer trust and no contribution from the community. There is no licence that achieves both unrestricted composability and exclusive commercial control – the two goals are in tension, and the licence choice is the legal instrument that resolves that tension.
NFT licensing terms and holder rights
An NFT is a token referencing off-chain content, most commonly an image, video or audio file hosted on IPFS, Arweave or a centralised server. The creator retains copyright in the work unless the copyright is expressly transferred, and the NFT buyer acquires only the rights the creator grants in the project's terms of use. Those terms may grant the holder a non-exclusive licence to display the image personally, a commercial licence to reproduce it on merchandise up to a revenue cap, or – rarely – a full copyright assignment. The absence of express terms means the buyer holds only the token itself, with no right to reproduce the image.
The Bored Ape Yacht Club model granted holders full commercial rights to their individual ape image, including the right to create derivative works and to sub-license those rights, a generous grant that enabled holder-driven product lines and media deals. Other projects limit commercial use to a revenue threshold or restrict derivatives. The enforceability of these terms turns on whether the buyer had notice of them at the point of purchase – a link in the mint transaction metadata or in the project's documentation creates constructive notice, but a buyer who acquires the NFT on a secondary market may argue lack of notice if the terms were not accessible. Best practice is to embed a short-form licence in the token metadata, with a link to the full terms, and to require that secondary marketplaces display the terms prominently.
Where an NFT holder exceeds the granted rights – for example, launching a commercial product line when only personal display was permitted – the creator's remedy is standard copyright infringement litigation, and the on-chain transfer history provides proof of ownership and timing. The blockchain does not encode or enforce the IP licence; it records only the token's provenance. Enforcement is off-chain, in the courts or through arbitration if the terms specify it. A project that intends to grant broad commercial rights should state that clearly in the terms and should register the underlying copyright in jurisdictions where registration is a prerequisite to filing suit, such as the United States.
Protocol forks and derivative works
Forking a protocol is the creation of a derivative work under copyright law, subject to the licence under which the original code was released. A fork of an MIT-licensed protocol is permissible provided the fork retains the copyright notice and the licence text; no further permission is required. A fork of a GPL-licensed protocol must itself be released under GPL, and the forking team cannot impose additional proprietary restrictions on downstream users. A protocol released with no explicit licence is "all rights reserved" by default, and forking it without permission is copyright infringement, though the author's failure to specify a licence in a publicly accessible repository may create an implied licence to use, an argument that turns on the context and the intent expressed in commit messages or documentation.
Where a protocol's economic model depends on network effects – liquidity in an AMM, staked capital in a proof-of-stake validator set, user reputation in a social graph – a fork fragments that network, and the original protocol may argue competitive harm but generally has no legal claim unless the fork copied proprietary branding, misrepresented the relationship, or violated a non-open component. The line between permissible competition and trademark infringement is crossed when the fork uses a confusingly similar name or logo that implies endorsement or continuation. A fork marketed as "Uniswap V4" or using the Uniswap sushi logo without permission infringes the trademark; a fork branded distinctly and disclosing that it is based on Uniswap's open-source code does not.
In one recent technical review, a DeFi team considered forking a competitor's liquidation engine, which was released under Apache 2.0, and integrating it into a proprietary yield aggregator. We confirmed that the fork was permissible under the licence, that the team must retain the Apache notice and satisfy the licence's attribution requirements, and that the aggregator's closed-source components could remain proprietary because Apache 2.0, unlike GPL, does not impose copyleft on combined works. The team proceeded with the fork and competed on the user-interface and vault-strategy layers, where the differentiation lived.
If a recovery clock is running after discovering an infringing fork, or if you are assessing a pre-launch fork for licence compliance, reach our disputes desk now at info@oboluslaw.com.
Trade secrets and disclosure risk
A trade secret is information that derives economic value from being secret, is subject to reasonable efforts to maintain secrecy, and is not generally known. For a Web3 project, trade-secret protection applies to off-chain components – the matching-engine logic that is never published, the private key-management architecture, the proprietary risk-scoring algorithm that feeds a lending protocol. Once code is deployed on a public blockchain and is readable, it is no longer secret, and trade-secret protection is lost.
The tension is that on-chain transparency is both a feature and a disclosure risk. A project cannot claim trade-secret protection over a smart contract whose bytecode is published on Etherscan, because the "reasonable efforts" element fails when the information is globally accessible. The protection, if any, lies in copyright and patent, not trade-secret law. Where a project wishes to protect a key algorithm, the options are to keep it off-chain, to deploy only compiled bytecode without publishing the source, or to apply for a patent before deployment and accept the quid-pro-quo of disclosure. The first option is cleanest but reduces verifiability and trust in a community that values open code; the second invites reverse-engineering; the third is costly and slow.
For partnerships with traditional finance institutions or enterprise clients, confidentiality obligations in the commercial contract protect shared data and integration details, but those obligations bind only the counterparty, not the broader market. If an integration detail is published on-chain, the confidentiality clause cannot retract it. The practical discipline is to define clearly, before launch, which components are public and which are proprietary, and to structure the system architecture so that the proprietary layer sits off-chain or in a trusted-execution environment where disclosure does not occur by design.
Cross-border IP enforcement and jurisdictional strategy
Intellectual property rights are territorial, and enforcement requires action in the jurisdiction where infringement occurs or where the infringer is located. For a Web3 project with a global user base, infringement is multi-jurisdictional by nature – a trademark may be violated in the EU by one actor, the same protocol forked without attribution by a team in Singapore, and NFT image rights breached by a US merchandise seller. The project must prioritise enforcement based on where the harm is greatest, where assets can be recovered, and where the legal system offers rapid interim relief.
The courts of England and Wales, the DIFC Courts in Dubai, Hong Kong and Singapore are leading forums for digital-asset disputes because they grant worldwide freezing orders, proprietary injunctions and Norwich Pharmacal disclosure orders against pseudonymous defendants where the cause of action is strong and the assets can be traced on-chain. A trademark-infringement or copyright-claim filed in these forums can be coupled with an asset-freeze application where the infringer holds crypto or fiat in an account subject to the court's jurisdiction. The United States offers statutory damages for wilful copyright infringement and ex parte seizure orders under the Lanham Act for counterfeit trademarks, remedies that can be faster than a full trial but require that the plaintiff has registered the IP in the US before the infringement began.
For defendants sitting in jurisdictions that do not recognise crypto-asset property rights or that lack a developed IP bar, the enforcement route may be to target the infrastructure – the domain registrar, the hosting provider, the payment processor – rather than the defendant directly. A DMCA takedown notice to a US-based host or a UDRP complaint to seize an infringing domain are administrative routes that bypass full litigation. Where the defendant is a DAO with no legal personality, the enforcement target is the multi-sig signers or the foundation that controls the brand, and the claim is structured as a proceeding against "Persons Unknown" (in common-law systems) until disclosure orders identify the individuals.
IP assignment and contributor agreements
A Web3 project that accepts code contributions from external developers or designers must document who owns the resulting IP. Under the default copyright rule in most jurisdictions, the author of a creative work is the initial copyright holder unless the work is made for hire or the copyright is assigned by written agreement. A contributor who submits a pull request to a GitHub repository retains copyright in that contribution unless the project's contributor licence agreement (CLA) or a terms-of-contribution document effects an assignment or grants a broad licence.
A CLA signed before the first contribution clarifies that the contributor either assigns the copyright to the project entity or grants a perpetual, irrevocable, worldwide licence that allows the project to use, modify, sub-license and commercialise the contribution under any licence the project chooses. Without a CLA, the project holds only an implied licence to use the contribution as part of the whole work, and if the project later pivots from an open-source to a proprietary model, the original contributor may assert that the new licence exceeds the scope of the implied grant. Open-source foundations such as the Apache Software Foundation and the Linux Foundation publish standard CLAs that Web3 projects adapt.
For token incentives paid to contributors, the legal question is whether the contribution is work-for-hire (which would vest copyright in the project entity if the contributor is classified as an employee or, in some jurisdictions, an independent contractor in a defined category) or an independent creation (which leaves copyright with the contributor unless assigned). Most Web3 projects structure contributors as independent, so a written assignment or a CLA is the only reliable mechanism to consolidate IP ownership. Where a DAO funds a grant to a developer, the grant agreement should specify that deliverables vest in the DAO's legal wrapper entity and that the developer waives moral rights where applicable.
Regulatory overlap: IP and securities classification
The intellectual-property strategy intersects with securities classification where a token's economic value is tied to the exploitation of IP. If a project promises that token-holder governance will direct how a patent portfolio is licensed, and that licence revenues will flow back to token holders, the token may be classified as a security under the relevant regime because the holder's return depends on the project's efforts to commercialise the IP. Under the US Howey test and similar frameworks in the EU, Singapore, Hong Kong and Switzerland, the critical question is whether the buyer expects profit from the efforts of others. An IP-licensing model that ties token value to those efforts increases the classification risk.
Conversely, a governance token that confers voting rights over brand use, over which open-source licence to adopt, or over whether to enforce a trademark does not inherently create a security, provided the token does not promise a financial return and the governance decisions are made by the holders collectively, not by a promoter. The distinction turns on the economic substance: a token that is purely governance over IP policy is less likely to be a security than a token that entitles the holder to a share of IP-licensing revenues. We assess classification against the substance of rights, not the marketing label.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the entirety of our practice, and we act only for businesses, so when the question is how to structure IP protection in a composable Web3 environment without forfeiting network effects, we speak the language of both the technology and the applicable regimes. To pressure-test your IP stack before launch or to enforce rights after infringement surfaces, write to us at info@oboluslaw.com.
FAQ
Can a decentralised protocol be regulated?
Yes. Regulators assess who operates, controls or profits from the protocol, regardless of the decentralisation narrative. If a team or foundation maintains control over core parameters, upgrades or treasury, that entity is the regulatory target. True decentralisation, where no actor can alter the protocol and no central party profits, may fall outside regulatory perimeters, but achieving that state requires provable immutability, distributed governance and no ongoing promotional activity by the founders. Most protocols remain sufficiently centralised to attract licensing obligations.
Who is liable when a smart contract fails?
Liability turns on the relationship between the user and the entity operating the interface or the protocol. If the contract is deployed by a foundation or a company offering a service, that entity may be liable for losses under consumer-protection, tort or contract law, depending on the jurisdiction. Disclaimers in the terms of use may limit liability but will not eliminate it where negligence or misrepresentation is proven. If the contract is genuinely autonomous and no entity promotes or maintains it, establishing a liable defendant is harder, though a plaintiff may still target the original deployers or the multi-sig signers who retain upgrade keys.
What wrapper suits this structure?
The entity choice turns on where the team and capital sit, where banking is accessible, and what regulatory obligations apply. A Cayman foundation company or a BVI company works for projects that need a neutral entity with flexible governance and access to banking. A Swiss association or a Liechtenstein foundation offers a civil-law frame for decentralised governance. A DAO LLC in Wyoming or a UNA in the Marshall Islands gives the DAO itself legal personality but constrains where banking and licensing are recognised. For projects that need passporting or MiCA licensing, an EU entity – often Malta, Lithuania or Ireland – is the starting point. The decision is multi-variable; there is no single best wrapper. The fit is determined by mapping your licensing, tax, banking and governance constraints.
By Roman Levitt, Technology & DeFi Counsel – advising token issuers and DeFi protocols on smart-contract structuring, IP protection and regulatory interface.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.
Related at OBOLUS
- DeFi, Tokenization & Smart-Contract Law – advising on protocol structuring, securities classification and decentralised-governance design
- Token and Equity Incentive Plans for Web3 Teams – structuring contributor compensation to align IP vesting with token launches
- Oracle and Data-Feed Liability in On-Chain Finance – liability allocation for off-chain data that triggers on-chain logic