Digital identity verification and compilation patent concepts

Blockchain identity works like this: a user submits documents and biometric data. A verification platform checks those inputs against government databases, watchlists, and other authoritative sources. If everything passes, the platform issues a credential: a compiled, verified identity object stored on-chain. Downstream applications can read that credential without repeating the full verification. The credential is the trust anchor.

That workflow is a compilation process. Individual identity attributes enter the system as interaction objects. Verification rules get applied. A single compiled output gets recorded on a distributed ledger. The Rock Innovation patents describe this architecture, and they were filed before the blockchain identity industry existed.

How the terminology maps

The patent claims use terms that can be compared with components in some identity-verification systems.

"Interaction objects" are the individual identity inputs: a scanned driver's license, a biometric template, a wallet address, a utility bill, a credit report. Each one is a discrete data object that enters the reconciliation pipeline from an external source.

"Preconfigured rules" are the verification logic: KYC checks, sanctions list lookups, liveness detection, document authenticity scoring, address verification. The rules determine whether each input is valid and whether the combined set meets the issuance threshold for a credential.

A verified credential may be a candidate for comparison with "compilation object," depending on how it is created and stored. A W3C Verifiable Credential, attestation, or token should not be assigned that claim meaning without analysis.

A verification platform may be a candidate for the claimed network-connected computer. The roles of any external services, users, and blockchains still need to be mapped.

The '029 patent and filtered identity lookups

The '029 patent (US 10,943,029) claims criteria-based retrieval. In identity verification, this is a constant operation. The system does not pull all available data about a person. It queries specific sources using specific parameters: "retrieve sanctions list entries matching this name and date of birth." "Retrieve employment records matching this employer and date range." "Retrieve wallet transaction history matching this address and time window."

Some identity-verification steps use filtered lookups. The '029 criteria-based retrieval language may therefore warrant review, but the system's actual queries and connected sources must be documented.

The '711 patent and the broad architecture

The '711 includes seven limitations and does not use the same flagging or device-criteria language as the earlier claims. An identity pipeline may provide comparison points, while its blockchain, proof system, actors, standards, and storage design can all matter to the complete analysis.

Priority date and the identity market

Civic launched its blockchain identity product in 2017. Serto's uPort project started in 2017. The Ethereum Attestation Service, Worldcoin, Polygon ID, and other major identity projects all came later. Our priority date of November 19, 2016 predates the entire blockchain identity sector.

Identity systems and regulatory requirements continue to change. Current product documentation is therefore necessary before comparing a platform's data flow with the patent language.

What identity companies should review

A platform that collects identity data, checks external sources, and stores a credential on a blockchain may warrant comparison with the claims. The patents are in force, but that fact and the priority date do not make the mapping automatic.

Claim chart templates for identity verification systems are available at rockinnovationip.com. The analysis is worth doing now, while the identity infrastructure is still being designed, rather than after it is locked into production.