A patent's title sells the technology; its claims define what is owned. And of the claims, claim 1 matters most, because it is almost always an independent claim — a single, self-contained sentence that does not refer back to any other claim and that states the broadest version of the invention. Everything else in the document — the abstract, the figures, the description — exists to support and interpret that sentence. If you read only one part of a blockchain patent, read claim 1, and read it the way the statute tells you it was drafted.

The statutory backbone is 35 U.S.C. 112. Subsection (b) requires that the specification “conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention,” and subsection (c) provides that “a claim may be written in independent or, if the nature of the case admits, in dependent or multiple dependent form.” That is the entire architecture in two lines: claims must distinctly mark the boundary of the right, and they come in independent and dependent flavors.

“The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.”— 35 U.S.C. § 112(b), source

The practical key is the limitation. A claim is a list of elements or steps — each phrase is a limitation — joined into one sentence. The rule that governs scope is counterintuitive at first: every limitation must be present for something to fall within the claim. Adding words to a claim therefore narrows it, because it adds requirements that must all be met. A claim reciting “a node, a private key share, and a threshold signature scheme” is narrower, not broader, than one reciting just “a node,” because all three must be present to infringe. This is why an independent claim is the broadest in its family: dependent claims add limitations to it, so they are always narrower.

Reading scope on a real consensus claim

Take a granted distributed-ledger patent, US11348095B2, assigned to nChain Licensing AG and titled “Rapid distributed consensus on blockchain.” Its abstract previews the independent method, and the structure is exactly what claim-reading expects — a sequence of steps, each a limitation:

“The computer-implemented method includes i) joining, by a node, a group through transfer of tokens to a public group address to become a group member, the group being associated with a threshold signature scheme for which the node controls a private key share, the transfer of tokens being made on a proof-of-work blockchain network; and ii) cooperating, by the node, with other nodes of the group to achieve a distributed consensus as to the correctness of work product of a proposer in response to a challenge.”— Rapid distributed consensus on blockchain, US11348095B2

Walk the limitations. To read on this claim, an accused system must have: a node that joins a group; joining done by transferring tokens to a public group address; the group associated with a threshold signature scheme; the node controlling a private key share; the token transfer made on a proof-of-work blockchain network; and the node then cooperating with other group nodes to reach consensus on a proposer's work product in response to a challenge. Every one of those is a requirement. A consensus system that reaches agreement some other way — without group membership purchased by token transfer, or without a threshold signature scheme, or on a non-proof-of-work network — falls outside this claim, however similar its goal. That is the discipline: the claim covers the recited combination, not the abstract aim of “fast consensus.”

Three habits for reading any claim 1

One further wrinkle is worth flagging because it recurs in software and blockchain claims. Section 112(f) allows a limitation to be expressed as a “means” for performing a function without reciting the supporting structure, in which case the claim is construed to cover the corresponding structure described in the specification and its equivalents — not any and every way of achieving the function. A blockchain claim that recites, say, “means for reaching consensus” is therefore narrower than it sounds: its scope is tied back to the specific algorithm the description discloses. Spotting functional language is part of reading scope honestly, because it determines whether a limitation reaches broadly or is anchored to a disclosed implementation. With that noted, three reading habits cover most claims.

First, identify the claim type from its opening words: “A computer-implemented method comprising…” or “A system comprising…” signals an independent claim; “The method of claim 1, wherein…” signals a dependent claim that inherits every limitation of its parent and adds more. Second, note the transitional word: “comprising” is open (the claim is met even if the accused system has extra elements), whereas “consisting of” is closed — a distinction that changes scope materially. Third, list the limitations and treat them as an AND, not an OR: missing any single recited element means the claim is not met. None of this resolves validity, which turns on the prior art and the prosecution history, and none of it substitutes for formal claim construction by a court. But it is enough to answer the question a reader actually has in front of a blockchain patent — what does this thing cover? — by reading the one sentence, claim 1, that the statute built to answer it.