On-chain vs. off-chain reconciliation: where the real IP lives
On-chain reconciliation handles data already on the blockchain. Off-chain reconciliation bridges the gap between blockchain records and external systems. The patents cover both.
Two recurring questions in technical reviews are whether off-chain computation or on-chain logic changes the analysis.
Both responses misunderstand what the patents claim. The patents describe the pipeline, not the location of the compute.
How to read this analysis
Technical similarities are starting points for review, not legal conclusions. A patent citation does not prove product use, materiality, validity, or infringement. Any product-specific conclusion requires current evidence, claim construction, and an element-by-element review by qualified patent counsel.
How the split actually works
Many blockchain systems operate across an on-chain/off-chain boundary. Examples can include rollup sequencers, bridges, oracle nodes, and applications that process data off-chain before publishing a result.
In each case, a system retrieves data from a distributed ledger, processes it through a rules engine, and records the output. Where the processing happens does not change the functional architecture. The '711 patent (US 11,720,711) describes a network-connected computer that interfaces with blockchain systems, retrieves data objects, applies rules, and stores compiled results. The claim does not specify whether the computer runs on the same hardware as the blockchain node or on a separate server across the internet.
Why "off-chain only" is not a design-around
If a system processes blockchain data off-chain but never writes results to a ledger, that fact may matter to a storage limitation. Systems vary, so the prevalence of a design should not be assumed.
Arbitrum's sequencer performs computation off-chain and posts batch commitments to Ethereum. That end-to-end path can be compared with retrieval, processing, and storage language, subject to the other limitations and evidence about the reviewed version.
Chainlink's oracle nodes aggregate data off-chain. But they submit the aggregated price to an on-chain contract. Without that submission, no DeFi protocol can use the price. The off-chain aggregation is the processing step. The on-chain submission is the storage step. Both are claimed elements.
Why "on-chain only" is not a design-around either
A smart contract may depend on a relayer, keeper, bot, oracle, or user to provide data or trigger a function. Whether one actor or a combination of actors meets the claimed system relationships is a fact-specific legal question.
A DeFi protocol's liquidation bot monitors positions, identifies those below the threshold, and calls the liquidation function. The bot is the system described in the patents. The smart contract is the execution environment. The bot performs the retrieval, the rule evaluation, and the function call. The contract records the result. The on-chain/off-chain split exists even when the project claims to be "fully on-chain."
The actual question
Where computation runs is one part of the architecture. Reading data, applying rules, and recording output create potential comparison points, but they do not show that all seven '711 limitations are met.
The on-chain/off-chain boundary, the responsible actors, and the location and form of storage can all affect claim analysis. They should be documented rather than treated as interchangeable.
Claim mapping details are at rockinnovationip.com.
Primary patent records
Verify claim text, continuity, status, and prosecution details in the official records before relying on this analysis.