Rock Innovation

Industry Exposure Reports

Technical questions for comparing documented blockchain systems with Rock Innovation's patent claims. These sector summaries identify what to investigate; they do not decide infringement or validity.

These are preliminary technical screening guides based on public information. Similar terminology or system behavior does not establish that every limitation of a patent claim is present. Product-specific conclusions require current evidence, claim construction, and review by qualified patent counsel.
Illustrative Review

Cross-Chain Bridges and Interoperability

Bridge and interoperability systems often retrieve information from separate chains, validate messages or proofs, and record an outcome. Those general functions provide starting points for review, but protocol-specific evidence and claim construction are required before reaching any legal conclusion.

Technical Review Questions

  • Which components retrieve data from source and destination chains?
  • What rules govern message, proof, validator, or guardian verification?
  • What output is created, and where is it recorded?
  • Does the implementation include the remaining limitations of a complete claim?

Market Questions

  • Which protocols and versions are currently in production?
  • When did the reviewed architecture first become public or operational?

Evidence to Collect

  • Versioned protocol documentation and architecture diagrams
  • Pinned source-code commits and deployed contract addresses
  • Transactions showing the actual source-to-destination workflow
Illustrative Review

Layer 2 Scaling Solutions

Rollups process transaction batches and publish commitments or proofs to a base chain. That workflow can be compared with selected patent terms, but similar vocabulary does not establish that a rollup practices every limitation of a claim.

Technical Review Questions

  • What data does the sequencer, proposer, or prover retrieve?
  • Which validation, fault-proof, or validity-proof rules are applied?
  • What commitment, proof, or state output is posted to the base chain?
  • Which claimed steps, if any, are absent or performed by a different actor?

Market Questions

  • Which software version and proof system should be evaluated?
  • Are shared rollup components configured differently by individual operators?

Evidence to Collect

  • Sequencer, proposer, and prover documentation
  • Pinned implementation code and deployment configuration
  • Representative on-chain commitments and proof transactions
Illustrative Review

DeFi Protocols and Aggregators

Some DeFi systems aggregate prices, liquidity, collateral, or transaction data and then execute an on-chain action. A review must distinguish multi-chain retrieval from activity confined to one chain and must test every claim limitation against the actual implementation.

Technical Review Questions

  • Does the product retrieve data from one chain or several?
  • Are retrieval criteria supplied by a user, a contract, or an off-chain service?
  • Which rules determine routing, lending, liquidation, or settlement?
  • What output is stored on-chain, and by which component?

Market Questions

  • Which functions are live rather than described only in marketing materials?
  • Has the architecture changed across versions, chains, or deployments?

Evidence to Collect

  • Verified smart-contract source and relevant off-chain code
  • Technical documentation and governance proposals
  • Representative transactions tied to the reviewed version
Illustrative Review

Enterprise Blockchain Platforms

Enterprise systems may combine records from permissioned or public ledgers, apply business rules, and expose results through reports or APIs. Product labels are not enough; the review must identify the specific components and data flow used by a deployed system.

Technical Review Questions

  • Which ledgers and external sources does the system connect to?
  • How are records selected, compared, corrected, or compiled?
  • Are reports or API responses stored on a blockchain or only off-chain?

Market Questions

  • Is the reviewed system a product, a customer-specific implementation, or a pilot?
  • Who operates each component in the end-to-end workflow?

Evidence to Collect

  • Product documentation, case studies, and architecture diagrams
  • Public APIs, technical white papers, and implementation records
  • Evidence separating vendor functions from customer-controlled functions
Illustrative Review

Financial Services and Payments

Financial-sector systems can involve ledger retrieval, compliance checks, settlement rules, and transaction records. A citing patent record does not show that an institution's product uses the same architecture or practices a Rock Innovation claim.

Technical Review Questions

  • Does the system retrieve data from multiple ledgers or from one internal ledger?
  • Which compliance, netting, custody, or settlement rules are applied?
  • What record is produced, where is it stored, and who controls that step?
  • Does public evidence support every limitation of the claim being reviewed?

Market Questions

  • Is the referenced initiative in production, in a pilot, or discontinued?
  • Does the public patent record concern the same system as the product under review?

Evidence to Collect

  • Regulatory filings and dated technical materials
  • Product documentation tied to a named service and version
  • Patent prosecution records with citation-source attribution
Illustrative Review

Blockchain Analytics and Compliance

Analytics and compliance tools may retrieve data from multiple chains, apply risk rules, and return reports or API results. Whether those functions correspond to a complete patent claim depends on claim construction, storage behavior, and evidence about the specific system.

Technical Review Questions

  • Which blockchain data is retrieved and how is it selected?
  • What compliance or risk rules transform the source data?
  • Are scores, reports, or API results stored on-chain?
  • Which functions are performed by the vendor rather than a customer or data provider?

Market Questions

  • Which offerings are multi-chain, and which analyze one chain at a time?
  • What public materials document the production workflow?

Evidence to Collect

  • Technical methodology and API documentation
  • Dated product materials and public demonstrations
  • Evidence of where processing and storage occur

These guides identify categories of public evidence that can support a later analysis. They do not state that Rock Innovation has verified every listed product, implementation, or market fact, and they are not legal advice.

Licensing DetailsContact Us