Blockchain patent claims raise a practical challenge for developers and organizations building distributed applications: the technology may work as one coordinated process even though different participants perform its steps. For industrial automation teams exploring distributed ledgers for supply chains, transactions, licensing, or smart contracts, that distinction matters when describing an invention in a patent application. Claim drafting must account for how the system operates, which actors carry out its functions, and where those activities take place.
This is a technical and legal drafting issue, not simply a matter of naming blockchain components. The organization of a claim can affect whether its steps are attributed to one actor and how the claimed systemâs use is assessed. Specific legal questions depend on the facts and should be addressed with qualified patent counsel.
How a distributed ledger organizes transactions
A blockchain is a form of decentralized, distributed database. Rather than relying on a single central authority to maintain records, it involves multiple participants, such as a managing entity and network nodes. Depending on the application, nodes may include users or miners.
Transactions are grouped into blocks. A cryptographic hash is generated from block data, and blocks are linked through hashes that refer to earlier blocks. This structure supports a shared record of transactions across the network. The underlying arrangement can be used in areas such as supply chain management, licensing and deeds, financial transactions, and cryptocurrency.
Distributing recordkeeping can reduce reliance on a single central point of failure. But distribution also affects how a patent claim should describe an invention: activities that appear to form one end-to-end operation may be carried out by separate devices or parties.
Why blockchain patent claims face divided-performance issues
Consider a method for recording a transaction. A user might submit a proposed transaction; a managing entity could provide a cryptographic algorithm; a miner could hash the transaction; other miners could verify it; and miners or the managing entity could record the verified transaction. The steps belong to one functional workflow, but the example assigns them to different actors.
That separation can raise the issue commonly called divided infringement: whether the acts of multiple participants can be treated as the performance of a claimed method by an alleged infringer. The Federal Circuitâs decision in Akamai Technologies, Inc. v. Limelight Networks, Inc. (2015), as described in the source material, identifies circumstances involving direction or control, as well as a joint enterprise. Direction or control may involve conditioning participation or a benefit on performing a step and establishing how or when it is performed. A joint enterprise involves specific elements, including an agreement, a common purpose, a shared pecuniary interest, and an equal right of control.
For claim drafting, the practical concern is that a method claim divided among users, miners, and a managing entity may be harder to map to one actorâs conduct. The claim should reflect the actual architecture and the relationships among participants rather than treating the network as though every operation occurs under one operatorâs direct control.
System claims and method claims present different questions
Focus system claims on a coherent actor or system
A system claim describes components and their relationships rather than listing a sequence of actions alone. In a blockchain implementation, those components might include a distributed network, a device that hashes submitted transactions, a device that verifies them, and a database that records verified transactions.
A drafting approach identified in the source is to direct every system element to a single actorâs activities where the invention allows it. For example, the claim may focus on functions performed by a managing entity or on activities associated with a node. The intended system boundaries should be clear: which components are included, what each does, and how they interact.
Make method-step control explicit where supported
Method claims should be examined step by step. If different participants perform different actions, the application should accurately describe who performs each step and what relationships govern that performance. Where the implementation supports it, the source highlights control over the manner and timing of steps, or conditioning participation or a benefit on performing them, as relevant considerations.
These are drafting considerations, not a guarantee that a particular claim will be enforceable. The technical description should not imply control that the actual system does not provide. Engineers and patent counsel should align the claim language with the product architecture, operating model, and participant roles.
Account for where distributed activity occurs
Distributed networks may involve devices and participants in different locations. That geography can matter under U.S. patent law. The Federal Circuitâs decision in NTP, Inc. v. Research In Motion, Ltd. (2005) is cited for the principle that, for a process to be used âwithinâ the United States under the relevant provision, each step must be performed in the country.
For system claims, the cited decision frames the place of use as where the system as a whole is put into serviceâwhere control is exercised and beneficial use is obtained. The distinction between a method and a system claim therefore matters when evaluating a distributed implementation. A networkâs components may be geographically dispersed, so claim language and the actual use of the system need to be considered together.
Practical drafting considerations for automation teams
When documenting a blockchain-enabled application, technical teams can help make the invention easier to assess by mapping its operation before claims are drafted. Record:
- Actors: Identify the managing entity, users, nodes, miners, and other participants.
- Functions: Show who submits, hashes, verifies, and records transactions.
- Control relationships: Describe how participation, benefits, step timing, and operating instructions work in practice.
- System boundaries: Distinguish the components under a particular actorâs control from those operated independently.
- Geography: Document where relevant devices and process steps operate, and where system control and use occur.
This architecture map does not replace legal analysis. It gives engineers, integrators, and counsel a shared technical account to use when considering system and method claims.
Conclusion: connect claim structure to system architecture
Blockchainâs distributed design can complicate patent claims because one process may span multiple actors and locations. For industrial automation decision-makers, the key implication is to treat claim drafting as an architecture-aware exercise: define system boundaries, assign functions accurately, consider control among participants, and account for where steps occur and where a system is put into use. Early coordination between engineering teams and patent counsel can help ensure the description of an invention reflects how the distributed application actually works.
Access Official Technical PDF