Blockchain Identity Proofing via Federation Protocols

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the blockchain environment, there is a need to tie blockchain identities back to verifiable individual identities, especially for cases where identity proofing is required from trusted parties.

Innovation Solution

The system and method for blockchain identity proofing via federation protocols from trusted parties involve a digital wallet application receiving a customer login and request for an assertion, redirecting the session to a financial institution backend for authentication and verification, and writing the assertion to a distributed ledger.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If blockchain identity is created independently without external verification, then identity creation is simple and fast, but the identity cannot be tied to verifiable real-world individuals

Engineering Contradiction:
Improveidentity verifiabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces trusted third-party entities (financial institutions, government agencies) as intermediaries that issue cryptographic proofs about user identities. These intermediaries bridge the gap between anonymous blockchain identities and verified real-world identities by providing cryptographically signed attestations that link the two without revealing sensitive information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the identity verification process into separate components: identity creation on blockchain, external verification by trusted parties, and cryptographic proof generation. This allows each component to operate independently with specialized functions, reducing overall system complexity while improving reliability.

Inventive Principle:
Principle #1Segmentation

2Reliability

If traditional centralized identity verification is used, then identity proofing is reliable, but the system lacks decentralization and single points of failure

Engineering Contradiction:
Improveidentity proofing reliabilityVSAvoiddecentralization
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal identity proofing system where multiple different trusted entities (banks, governments, other organizations) can all issue standardized cryptographic proofs that are recognized across the blockchain network. This multi-functional approach allows any verified entity to serve as an identity anchor, providing both reliability through diverse verification sources and decentralization through distributed trust.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If sensitive personal information is stored on blockchain for verification, then identity verification is straightforward, but security risks and privacy concerns increase

Engineering Contradiction:
Improveverification simplicityVSAvoidsecurity risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

Instead of storing actual sensitive personal information on the blockchain, the system stores cryptographic proofs and hashes that serve as verifiable copies. These cryptographic representations contain all necessary verification information without exposing the underlying sensitive data, maintaining verification simplicity while eliminating security risks associated with storing actual PII on distributed ledgers.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250190978A1Systems and methods for blockchain identity proofing via federation protocols from trusted parties
Publication Date: 2025.06.12 JPMORGAN CHASE BANK NA
  • US20250190978A1 patent drawing
  • US20250190978A1 patent drawing
  • US20250190978A1 patent drawing

AI summary

Blockchain identity proofing via federation protocols is disclosed. A method may include: receiving, at a digital wallet application for a financial institution on a customer electronic device, a customer login from a customer; receiving, by the digital wallet application and from the customer, a request for an assertion, wherein the request redirects a session with the digital wallet application to a financial institution backend via a financial institution website or a financial institution application using a federation protocol; authenticating, by the financial institution backend, the customer; confirming, by the financial institution backend, the assertion using verified customer information in a verified customer information database; redirecting, by the financial institution backend, the session to the digital wallet application; returning, by the financial institution backend and using the federation protocol, the assertion to the digital wallet application; and writing, by the digital wallet application, the assertion to a distributed ledger.