IoT, blockchain, and the reconciliation problem

A temperature sensor in a pharmaceutical warehouse generates a reading every thirty seconds. A GPS tracker on a shipping container reports its position every minute. A vibration sensor on a turbine blade streams data continuously. Multiply by thousands of devices across a supply chain or industrial operation, and you have a firehose of data that needs to be verified, filtered, and anchored to a blockchain for auditing and compliance.

Most enterprise IoT deployments bolt blockchain verification on as an afterthought. They collect data in centralized systems first, then push hashes or summaries to a ledger later. This approach works, but it misses the point. The value of blockchain is real-time, deterministic verification. If the data spends hours in a centralized database before touching a chain, the immutability guarantee starts after the most vulnerable window has already closed.

Our patents describe a different architecture: one where connected devices feed data directly into a reconciliation pipeline that interfaces with distributed ledgers.

What the claims cover

The '029 patent (US 10,943,029) specifically addresses criteria-based retrieval of data from connected devices. In practical terms, this means a system that does not ingest all available sensor data but filters it: "give me temperature readings above 90 degrees from cold storage units in the northeast region." The system retrieves data matching those criteria and processes it against rules before writing results to a blockchain.

The '711 patent uses seven limitations involving a network-connected computer, distributed-ledger interfaces, data objects, rules, and compilation objects. An IoT workflow may offer candidates for those terms, but the data source and complete system relationships must be verified.

Dependent claims refer to device, user, and company objects. Sensors, operators, and organizations may provide comparison points; a label match is not enough to establish the limitation.

Who cited us and why

Toyota, Siemens, and Bosch have all filed patents that cite Rock Innovation's work. All three are heavy IoT operators building blockchain integration for their industrial systems. Toyota for procurement and parts tracking. Siemens for industrial equipment monitoring. Bosch for automotive supply chain verification.

Those citation records identify later patents for review. They do not show that an assignee's attorneys concluded the architectures overlap or that a commercial Bosch system practices a Rock Innovation claim.

The gap in current IoT-blockchain integration

Most IoT-blockchain platforms today handle the device layer and the blockchain layer as separate concerns. Data collection happens over here. Blockchain recording happens over there. The reconciliation step in between, where data gets filtered, validated against rules, and compiled into a verified output, is treated as application logic rather than infrastructure.

The '029 includes criteria-based retrieval and the '711 includes rule-application language. Those limitations make the pipeline important to review, but neither should be reduced to a general statement that filtering or rules are present.

Enterprise IoT companies building blockchain verification systems should review these claims. The architecture they are implementing was described and patented in November 2016, before most enterprise blockchain platforms existed. Claim mapping templates are at rockinnovationip.com.