Major patent filings reveal that enterprise blockchain identity management is defined by specific cryptographic workflows and hardware implementations. Patent portfolios across enterprise assignees demonstrate that using a blockchain for identity does not mean storing personal data directly on an immutable ledger. Instead, these technical architectures use block hashes, hardware security enclaves, smart contracts, and off-chain data stores to manage user verification and access control.
The following analysis details the technical mechanisms described in core blockchain digital identity patents. It covers credential issuance, cryptographic protections, biometric integration, key revocation systems, and off-chain data structures.
What Is Being Patented in Blockchain Identity Management?
Patents in this domain focus on concrete technical methods for handling identity data, cryptographic validation, and system access. Intellectual property offices reject broad concepts like using a ledger for identity. Instead, patent claims target specific algorithmic steps and hardware interactions.
Patent filings in blockchain identity center on distinct architectural mechanisms:
- Identity identification information separating raw user profile markers from public verification parameters
- Authentication information validating dynamic challenge responses without transmitting underlying credentials
- Cryptographic hashes linking distributed ledger blocks to establish tamper-proof sequences of verification events
- Public and private key credentials managing asymmetric encryption pairs assigned to human users or device nodes
- Identity tokens representing verifiable claims issued by authorized entities for limited-scope access
- Biometric authentication protecting local access to cryptographic key stores on client hardware
- Blockchain records maintaining immutable transaction indices, public key mappings, and status logs
- Identity attributes managing granular user traits like age or employment status independently from core identity keys
- Credential verification enabling third-party relying parties to validate claims cryptographically without contacting the original issuer
- Identity revocation providing automated protocols to invalidate compromised keys or expired tokens on-chain
Samsung patent filings illustrate this approach by separating personal identity identification information from authentication information. The system connects distinct blockchain records using block hashes. This approach proves identity control across different service providers without exposing raw personal records to ledger participants.
The Blockchain Digital Identity Patents
Four granted U.S. patents anchor this analysis. Each solves a distinct piece of the identity puzzle rather than competing for the same claim territory.
US9,635,000 B1 was granted April 25, 2017, originating from inventor Sead Muftic’s work under Business Information Exchange System Corp before reassignment to Muftic directly. It lays the conceptual groundwork with a public identities ledger built on peer-to-peer validation.
US10,637,665 B1, assigned to Trusted Key Solutions Inc. and later acquired by Mastercard, moves that foundation to mobile devices. It wraps key generation and signing inside a mobile Trusted Execution Environment and gates access with biometrics.
US11,018,869 B2 is a continuation within the same Trusted Key patent family that tackles the essential problem of revocation, addressing what happens when a device is lost, or a credential must be invalidated before its formal expiration date.
US10,992,478 B2 was granted to Samsung SDS on April 27, 2021, listing inventor Hyun and colleagues. It formalizes the dual-block architecture that keeps identity data and authentication events cryptographically linked yet structurally distinct.
Together, these four filings cover the complete lifecycle: how an identity is created, how it authenticates on a device, how it gets revoked, and how the underlying blockchain data structure keeps the system auditable without creating a privacy liability.
US9635000B1: Blockchain Identity Management Through a Public Identities Ledger
Muftic’s patent acts as a direct response to the identity-provider vulnerabilities of the 2010s, such as the 2017 Equifax breach and the widespread reliance on linked accounts that turned a single compromised password into a cross-platform risk. The invention proposes a decentralized alternative: a public identities ledger where identity objects are validated by network consensus rather than a single corporate authority.
The core mechanics drive its utility. The ledger operates on an append-only basis, meaning entries can be added but never silently overwritten. Individual identity attributes, such as a professional license or verified employment record, are processed as discrete cryptographic claims rather than bundled into a single monolithic profile. As a result, a relying party checking whether an individual is a licensed electrician never gains access to unrelated personal details. Every identity record is forward- and backward-linked through digital signatures, applying the same tamper-evident principles found in cryptocurrency ledgers directly to identity claims.
The most enduring aspect of this filing lies in its explicit privacy-by-design framework. The underlying identity payload remains in user-controlled storage, while only cryptographic pointers are written to the public ledger. This architectural choice anticipated data minimization principles prior to major regulatory shifts like GDPR, allowing the underlying framework to remain relevant while many single-token identity projects from that period faded.
US10637665B1: Digital Identity Credentials on a Mobile Device
Where the Muftic patent establishes foundational theory, Trusted Key’s filing focuses on mobile implementation. This patent shifts identity management from an abstract ledger to the primary device people use to authenticate: their smartphones.
The core architecture relies on the Trusted Execution Environment (TEE), a hardware-isolated zone within the mobile processor that operates independently of the primary operating system to generate and store private keys. Even if malware fully compromises the device’s main operating system, it cannot extract a key stored inside the TEE. This offers a fundamentally stronger security guarantee than storing an encrypted key file in general application storage, which remains vulnerable to elevated privilege attacks.
Layered above the TEE, the patent outlines a Digital Identity Management (DIM) mobile app that handles user-facing operations: requesting credentials, receiving signed identity tokens, and routing authentication challenges directly to the hardware. Biometric and PIN checks function strictly as local gates; matching a fingerprint or face scan unlocks the enclave’s signing capabilities without serving as the cryptographic proof itself. On the issuer side, Hardware Security Modules (HSMs) anchor the trust chain, signing tokens using keys that never interact with general-purpose infrastructure.
The specification’s description of its network of trust model highlights a critical structural shift: any party holding a key pair can issue identity tokens to another party. This mechanism enables credentials like a government-issued driver’s license token to satisfy a financial institution’s KYC requirements without requiring direct API integration between the bank and the issuing agency. This interoperability model directly aligns with modern verifiable credential standards, such as the digital wallet frameworks deploying across global regulatory jurisdictions.
US11018869B2: Identity Tokens, Credentials, and Revocation
Revocation proved to be the point where many early blockchain identity proposals struggled, primarily because immutability and revocability initially appear contradictory. This continuation patent from the Trusted Key family addresses that exact challenge: rather than deleting a credential, the system appends a new, equally immutable entry stating that the specified credential is no longer valid.
The patent structures two parallel tracking mechanisms to handle different operational scopes. A Credential Revocation List manages foundational, long-term credentials like driver’s licenses or professional certifications. In parallel, an Identity Token Revocation List handles short-lived, purpose-specific tokens issued for individual transactions or active sessions. Separating these mechanisms prevents high-frequency session revocations from triggering full credential re-issuance workflows, while ensuring that the status of a foundational credential does not get buried within a rapidly changing list of short-lived tokens.
Smart contracts execute the underlying enforcement. When an authorized issuer submits a revocation transaction, the contract updates the on-chain state immediately. Relying parties checking a credential’s validity receive real-time verification without depending on a centralized status server that could experience downtime or latency. Additionally, the multi-device provisions account for practical edge cases: losing a single mobile phone revokes only the keys associated with that specific device, preventing the user’s broader identity profile from collapsing or requiring complete re-enrollment.
US10992478B2: Linking Identity and Authentication Data Through Blockchain
Samsung SDS’s filing introduces structural precision by dividing identity management across two distinct blockchain block types, linking them via cryptographic hashes rather than a shared database index.
The first block stores identity identification information, containing static structural metadata that defines which record an entity owns. The second block houses authentication information, recording dynamic proofs generated during active login attempts, including challenge tokens, verified signatures, and session artifacts.
The authentication block embeds the cryptographic hash of the identity identification block directly within its header. This creates a verifiable connection between a specific login event and the underlying identity without consolidating sensitive personal data into a single queryable record.
Biometric processing follows the isolated execution patterns seen in the Trusted Key filings. Biometric data, whether derived from fingerprints, iris scans, vein patterns, voice characteristics, or facial geometry, is converted into a local feature hash. This hash is validated against the authentication block structure without exposing raw biometric inputs to the chain. Enterprise architects frequently cite this filing for its support of cross-service verification, allowing two independent organizations to validate the same underlying identity without merging user databases or exposing user records to third parties.
How These Patents Handle Identity Data
A common misconception is that blockchain identity platforms store complete user profiles directly on a public ledger. Storing unencrypted personal data on an immutable ledger violates global privacy regulations, such as GDPR right-to-be-forgotten mandates, and creates long-term security risks.
The analyzed patent portfolios demonstrate clear technical boundary lines between on-chain parameters and off-chain data repositories:
- On-Chain Data Elements: Public ledgers hold low-footprint, non-reversible data structures. This includes public keys, cryptographic hashes of identity attributes, smart contract execution states, credential revocation vectors, and block timestamps. These entries provide auditability without exposing readable personal data.
- Off-Chain Data Elements: Personally Identifiable Information (PII)—such as legal names, residential addresses, national identification numbers, and raw biometric records—remains off-chain. This data is stored in encrypted local device storage, hardware enclaves, or secure distributed databases.
- Data Structuring via Identity Identifiers and Hashes: When an identity authority issues a credential, the system processes the raw data through cryptographic hash functions (such as SHA-256). The resulting fixed-length hash string acts as a deterministic fingerprint. The hash is recorded on-chain, while the actual data payload remains in user-controlled off-chain storage.
If a relying party needs to verify an attribute, the user presents the off-chain data. The relying party hashes the presented data locally and compares it to the on-chain hash record. Matching hashes confirm data authenticity without requiring raw records to persist on-chain.
The Role of Cryptographic Keys and Identity Credentials
At an operational level, these architectures rely on public-private key pairs. The public key is broadcast to the network, while the private key remains secured on the user’s physical device. The sequence used to prove control over an identity follows a structured cryptographic handshake.
First, key pairs are generated inside isolated hardware modules like a TEE or Secure Enclave, and the resulting public key is published as the identity’s on-chain anchor. An authorized issuer then verifies real-world attributes off-chain, packages them into a structured credential, signs the payload with its private key, and delivers it to the user’s wallet.
When access is requested, the relying party issues a unique, single-use nonce to prevent replay attacks. The user authenticates locally on their device using a PIN or biometric prompt, which authorizes the secure enclave to sign the payload. Finally, the enclave signs the challenge using the private key and returns the response. The relying party fetches the user’s registered public key from the blockchain to verify the signature mathematically.
Once validated, the relying party establishes proof that the user controls the corresponding private key and holds a valid credential. No static passwords cross the network, and no central database retains a master secret that could be targeted in a breach. This challenge-response workflow adapts established security models, like those found in FIDO2 and WebAuthn, directly into ledger-anchored identity frameworks.
Biometrics Have a Different Role Than the Blockchain
Patent disclosures explicitly distinguish between biometrics and blockchain ledgers. Biometrics do not replace cryptographic primitives, nor are raw biometric templates stored on distributed ledgers.
Biometrics serve as a local access gatekeeper for device-stored credentials:
- Local Capture and Matching: Sensors capture biometric features such as fingerprints, iris data, voice patterns, or facial geometry. The device converts this data into a local cryptographic feature vector or hash.
- Enclave Authorization: The processed biometric hash is compared against the reference template locked inside the mobile device’s secure hardware. Matching data authorizes the enclave to perform operations using the stored private key.
- Isolation from Public Ledgers: Biometric feature data remains within local device hardware. Storing biometric templates on a public ledger would present permanent identity risks if decrypted. The ledger records only public key mappings and transaction signatures, keeping biometrics bound entirely to client-side authentication hardware.
What Makes Blockchain Useful for Digital Identity?
Because these systems actively keep personal data off-chain, the value of the ledger comes down to specific architectural capabilities rather than generalized claims about the technology.
Shared verification infrastructure allows independent organizations, such as banks, employers, and government agencies, to validate identity attestations without any single entity controlling the underlying system. Tamper-evident record chains ensure that identity state changes remain auditable over time, allowing parties to verify when a key update occurred without relying on centralized logs.
Public key anchoring enables systems to verify signatures directly using on-chain public keys, eliminating the need for real-time central directory lookups. Interoperable standards allow multiple issuers and verifiers to operate within a single shared protocol, reducing the need for custom point-to-point integrations between individual organizations. Lastly, automated revocation through smart contracts executes credential revocations immediately across the network, removing reliance on periodic batch processing updates.
The ledger is used for what it does best: maintaining a tamper-evident, shared state that no single party can alter unilaterally, while keeping sensitive underlying data out of the system entirely.
What These Patents Reveal About the Direction of Digital Identity
Reviewing patent filings from 2017 through 2021 shows a clear shift in enterprise identity architecture. Early filings focused primarily on establishing the core mechanisms for decentralized validation over centralized identity providers. Later patents moved beyond basic validation to address operational mechanics, focusing on dual-block data separation and immediate revocation handling.
Recent developments continue to refine these core principles. Filings incorporate zero-knowledge proofs (ZKPs), allowing individuals to confirm specific attributes, such as proving age or income limits, without sharing underlying birth dates or exact financial numbers. Decentralized key recovery mechanisms are expanding to address practical usability issues, ensuring that a lost physical device does not permanently compromise a user’s digital identity. Fine-grained revocation indexing also continues to evolve alongside major public initiatives, including global digital wallet frameworks that build on the core credential concepts established in these early patents.
The broader trend across a decade of patent filings remains clear: enterprise identity frameworks prioritize privacy compliance, localized key control, and cross-organizational interoperability over placing sensitive data on a chain. As these architectures mature, less personal data reaches the ledger, relying instead on off-chain storage linked by verifiable cryptographic proofs.
Checking the Current Status of a Blockchain Identity Patent
While a patent specification outlines how an invention operates, it does not confirm whether the patent is active or enforceable. Evaluating the operational and legal status of a filing requires reviewing several distinct factors.
Document types marked with A1 represent pending applications that may be altered, rejected, or abandoned during examination, whereas numbers ending in B1 or B2 indicate fully granted patents with enforceable claim sets. Jurisdictional scope is equally critical: patents granted by the USPTO provide legal protection exclusively within the United States, meaning international protection requires separate filings in target jurisdictions, often managed through Patent Cooperation Treaty (PCT) applications.
Priority dates and maintenance terms dictate the lifespan of a patent. Utility patents generally maintain a 20-year term from their non-provisional filing date, contingent on regular maintenance fee payments. Failing to pay required maintenance fees causes an otherwise valid patent to lapse early. Furthermore, continuation and divisional filings can expand or narrow the scope of claims established in an initial parent application, meaning assessing a single patent requires reviewing its broader family history.
Finally, while the written abstract and description provide context, the numbered claims at the end of the document define the precise legal boundaries of the invention. To accurately verify ownership and operational status, consult primary databases like the USPTO Patent Public Search system or official national patent registries directly, as third-party aggregators may not reflect real-time maintenance fee statuses or ownership transfers.
