How three patents cover the full blockchain reconciliation stack

The Rock Innovation family uses different claim sets across a parent and two continuations, moving from detailed exception-handling limitations to a shorter set of system limitations.

Here is how the three patents layer together, starting from the broadest.

The '711: the widest net

US 11,720,711 includes seven limitations in its independent system claims and does not include the same flagging requirement as the '073 patent. The claims describe interfaces with distributed ledgers, data retrieval, rule application, and storage of compilation objects.

Rollups, bridges, oracle networks, and DeFi aggregators may perform functions that resemble parts of that sequence. Resemblance at this level does not establish that every limitation is present.

A licensing analysis should identify the asserted claim, construe its terms, and map each limitation to evidence for the current product version. Unmapped or disputed limitations must be addressed rather than assumed.

The '029: conditional logic and filtered retrieval

US 10,943,029 sits in the middle of the family. Ten independent claim elements. It keeps the core architecture of the '711 but adds specificity around how data gets retrieved: the system applies criteria to determine which data objects to pull from connected sources.

Many production systems filter data rather than retrieving everything available. Examples include collateral thresholds, contract-address filters, and geographic parameters. Whether those filters meet the claim language depends on how the criteria and connected sources are defined.

The '029 includes criteria-based retrieval as a limitation. Its presence in a product cannot be inferred from a general statement that the product filters data.

The '073: exception handling with teeth

US 10,192,073 is the parent patent and the most specific. Thirteen independent claim elements. It describes a system that goes beyond basic reconciliation to include flagging, replacement, and documentation of data corrections on-chain.

When a data discrepancy appears, the system flags it. When the discrepancy is resolved, the system replaces the record. When the replacement happens, the system creates an addendum logging what changed and why. This is blockchain reconciliation for environments where auditability is mandatory: financial settlement, regulatory compliance, healthcare records, government systems.

Optimistic-rollup dispute mechanisms offer possible comparison points for the '073 flagging and correction limitations. A full comparison must account for how the challenged state, replacement, and addendum language operate in the claim and in the reviewed implementation.

The '073 contains more limitations, so a claim chart requires more implementation-specific evidence. A conclusion is supportable only if each limitation is addressed.

How the funnel works in licensing

A review may begin with the '711 because it has the shorter limitation set, but no conclusion should be drawn until every limitation is mapped to evidence.

The '029 and '073 raise additional questions about filtered retrieval, flagging, correction, and documentation. Those features should be checked against the current architecture rather than presumed from a product category.

Twenty-eight total claims across the three patents. Dependent claims cover report generation, multiple data object types, external data sources via API, and rules engine functionality. The family covers reconciliation at the broadest architectural level and drills down into specific operational patterns that production systems actually implement.

The three patents claim priority through the November 19, 2016 family and have been examined. The 87-family citation count supplies a list of later records for research; it does not confirm market relevance, validity, or infringement.

Details on each patent and claim-chart templates are available at rockinnovationip.com for independent review.