# US 2026/0074903 A1 · Privacy-preserving identity verification using blockchain and granular data control > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2026/0074903 A1 - Document ID: US20260074903A1 - Status: Published application - Kind: A1 - Application number: 18/828,238 - Filed: 2024-09-09 - Published: 2026-03-12 - Earliest claimed: 2024-09-09 - Inventors: Serge M KRASNYANSKY - Web page: https://patentgrep.com/patent/US20260074903A1 ## CPC - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L 9/3236: {using cryptographic hash functions} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3247: {involving digital signatures} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Approaches are described for secure identity verification using blockchain technology. A configuration record for a user's identity attributes is obtained. The configuration record is used to evaluate and verify various identity elements through cross-referencing with authoritative sources. Based on the configuration record, identity tokens (KYbits) are generated using cryptographic techniques and stored on a blockchain ledger. These KYbits encapsulate verified identity information and can be utilized in verification processes without disclosing sensitive personal data. The identity tokens enable secure and privacy-preserving transactions across various platforms, ensuring compliance with data protection regulations and enhancing user control over personal identity information. ## Claims ### Claim 1 A system for secure identity verification and management, comprising: a computing device processor; a plurality of user devices configured to communicate over a network, the network incorporating features of both decentralized blockchain architecture and centrally-managed identity verification systems; and a memory device including instructions that, when executed by the computing device processor, enables the system to: obtain user credential data from heterogeneous data sources, the user credential data comprises at least one data element, the user credential data being unstructured and in various formats, extract the user credential data by parsing the user credential data using at least one data parsing technique to generate parsed user credential data, segment the parsed user credential data into discrete identity elements, individual discrete identity elements representing a specific attribute of an identity of a user associated with the user credential data, standardize the discrete identity elements to generate standardized discrete identity elements, wherein standardizing the discrete identity elements comprises applying formatting rules to ensure the discrete identity elements conforms to a predefined structure, map verification questions to the standardized discrete identity elements to generate verification pairs, wherein mapping comprises utilizing algorithms to match the standardized discrete identity elements with relevant question templates, transform the verification pairs into identity tokens, the identity tokens representing verified identity attributes and generated through application of cryptographic techniques, and maintain the identity tokens on a computerized ledger system. ### Claim 2 (depends on 1) The system of claim 1, wherein transforming the verification pairs into identity tokens includes converting each verification pair into a corresponding binary representation using a one-way function. ### Claim 3 (depends on 2) The system of claim 2, wherein the one-way function comprises at least one of a cryptographic hash function, a keyed-hash message authentication code (HMAC), or a hash-based message authentication code (HMAC), or a digital signature algorithm. ### Claim 4 (depends on 2) The system of claim 2, wherein the computerized ledger system is a distributed ledger system, and the corresponding binary representation is stored as transaction data on the distributed ledger system. ### Claim 5 (depends on 2) The system of claim 2, further comprising a verification system, coupled to a data repository that stores corresponding binary representations, that: receives a verification request from a verifying party, the verification request specifying one or more attributes to be verified about the user; retrieves the corresponding binary representation corresponding to the one or more attributes from the data repository; compares the corresponding binary representation retrieved to the one or more attributes; and generates a verification result to the verifying party indicating whether the corresponding binary representation matches the one or more attributes, without revealing personal information to the verifying party. ### Claim 6 (depends on 5) The system of claim 5, wherein a user associated with the user credential data authorizes the verification system to release the corresponding binary representation to the verifying party by providing an authentication credential. ### Claim 7 (depends on 6) The system of claim 6, wherein the authentication credential comprises one of: a cryptographic proof, a zero-knowledge proof, or a blind signature. ### Claim 8 (depends on 1) The system of claim 1, further comprising instructions that, when executed by the computing device processor, enables the system to: receive a verification request from a service provider, the verification request seeking to verify specific identity attributes of a user, retrieve relevant identity tokens from the computerized ledger system in response to the verification request, using a private key associated with a user to access and decode stored information on the computerized ledger system, and provide validated identity tokens in response to the verification request, allowing the service provider to make decisions based on the verified identity attributes without disclosing user data, thus preserving user privacy and ensuring data minimization. ### Claim 9 (depends on 8) The system of claim 8, further comprising instructions that, when executed by the computing device processor, enables the system to: analyze a user consent log to verify that the user has provided consent for data sharing, prompting the user for explicit consent if required consent is not found or is insufficient. ### Claim 10 (depends on 8) The system of claim 8, further comprising instructions that, when executed by the computing device processor, enables the system to: validate the identity tokens by cross-referencing the computerized ledger system to ensure their integrity and authenticity. ### Claim 11 (depends on 1) The system of claim 1, further comprising instructions that, when executed by the computing device processor, enables the system to: encode the identity tokens with cryptographic authentication information, including generating digital signatures and applying encryption to protect the identity tokens, and associating the identity tokens with authentication metadata. ### Claim 12 A computer-implemented method, comprising: obtaining user credential data from heterogeneous data sources, the user credential data comprises at least one data element, the user credential data being unstructured and in various formats, extracting the user credential data by parsing the user credential data using at least one data parsing technique to generate parsed user credential data, segmenting the parsed user credential data into discrete identity elements, individual discrete identity elements representing a specific attribute of an identity of a user associated with the user credential data, standardizing the discrete identity elements to generate standardized discrete identity elements, wherein standardizing the discrete identity elements comprises applying formatting rules to ensure the discrete identity elements conforms to a predefined structure, mapping verification questions to the standardized discrete identity elements to generate verification pairs, wherein mapping comprises utilizing algorithms to match the standardized discrete identity elements with relevant question templates, transforming the verification pairs into identity tokens, the identity tokens representing verified identity attributes and generated through application of cryptographic techniques, and maintaining the identity tokens on a computerized ledger system. ### Claim 13 (depends on 12) The computer-implemented method of claim 12, wherein transforming the verification pairs into identity tokens includes converting each verification pair into a corresponding binary representation using a one-way function. ### Claim 14 (depends on 13) The computer-implemented method of claim 13, further comprising: receiving a verification request from a verifying party, the verification request specifying one or more attributes to be verified about the user; retrieving the corresponding binary representation; comparing the corresponding binary representation retrieved to the one or more attributes; and generating a verification result to the verifying party indicating whether the corresponding binary representation matches the one or more attributes, without revealing personal information to the verifying party. ### Claim 15 (depends on 14) The computer-implemented method of claim 14, further comprising: analyze a user consent log to verify that the user has provided consent for data sharing, prompting the user for explicit consent if required consent is not found or is insufficient; and validating the identity tokens by cross-referencing the computerized ledger system to ensure their integrity and authenticity. ### Claim 16 (depends on 14) The computer-implemented method of claim 14, wherein transforming the verification pairs into identity tokens includes converting each verification pair into a corresponding binary representation, and further comprising: receiving a verification request from a verifying party, the verification request specifying one or more attributes to be verified about the user; retrieving the corresponding binary representation corresponding from a data repository; comparing the corresponding binary representation retrieved to the one or more attributes; and generating a verification result to the verifying party indicating whether the corresponding binary representation matches the one or more attributes, without revealing personal information to the verifying party. ### Claim 17 A non-transitory computer readable storage medium storing instructions that, when executed by at least one processor of a computing system, causes the computing system to: obtain user credential data from heterogeneous data sources, the user credential data comprises at least one data element, the user credential data being unstructured and in various formats, extract the user credential data by parsing the user credential data using at least one data parsing technique to generate parsed user credential data, segment the parsed user credential data into discrete identity elements, individual discrete identity elements representing a specific attribute of an identity of a user associated with the user credential data, standardize the discrete identity elements to generate standardized discrete identity elements, wherein standardizing the discrete identity elements comprises applying formatting rules to ensure the discrete identity elements conforms to a predefined structure, map verification questions to the standardized discrete identity elements to generate verification pairs, wherein mapping comprises utilizing algorithms to match the standardized discrete identity elements with relevant question templates, transform the verification pairs into identity tokens, the identity tokens representing verified identity attributes and generated through application of cryptographic techniques, and maintain the identity tokens on a computerized ledger system. ### Claim 18 (depends on 17) The non-transitory computer readable storage medium of claim 17, wherein the instructions, when executed by the at least one processor, further enables the computing system to: transforming the verification pairs into identity tokens by converting each verification pair into a corresponding binary representation using a one-way function. ### Claim 19 (depends on 18) The non-transitory computer readable storage medium of claim 18, wherein the instructions, when executed by the at least one processor, further enables the computing system to: receive a verification request from a verifying party, the verification request specifying one or more attributes to be verified about the user; retrieve the corresponding binary representation corresponding to the one or more attributes from a data repository; compare the corresponding binary representation retrieved to the one or more attributes; and generate a verification result to the verifying party indicating whether the corresponding binary representation matches the one or more attributes, without revealing personal information to the verifying party. ### Claim 20 (depends on 19) The non-transitory computer readable storage medium of claim 19, wherein the instructions, when executed by the at least one processor, further enables the computing system to: use a user's private key to access and decode stored information on the computerized ledger system.