Cryptographic Identity Linking for Verifiable Trust Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain systems lack effective methods for linking parties cryptographically and verifying these links, which is crucial for identity management and compliance with regulations like KYC, and they do not interface well with non-blockchain systems.
Innovation Solution
A method involving generating shared private keys between parties and using public-private key pairs to establish a cryptographically linked identity, which can be verified by a third party, ensuring trust transfer between parties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If blockchain systems use public keys and addresses for identification, then uniqueness within the blockchain address space is achieved, but the ability to comply with regulations like KYC and interface with non-blockchain systems is insufficient
Solution Approach 1:
The patent introduces a trusted third party as an intermediary that issues cryptographic attestations linking blockchain public keys to real-world identities. This mediator enables KYC compliance and non-blockchain system integration without compromising the decentralized nature of blockchain, resolving the contradiction between reliability and adaptability.
Solution Approach 2:
The patent embeds multiple layers of cryptographic verification within the blockchain structure. Trusted third parties issue attestations that are themselves cryptographically signed and stored on-chain, creating nested verification layers that enable both regulatory compliance and system interoperability while maintaining blockchain's unique identification capability.
2Reliability
If blockchain systems maintain decentralized identification through public keys, then privacy and security are improved, but the ability to establish trust between parties for sensitive communications is limited
Solution Approach 1:
The patent creates cryptographic copies of identity verification through digitally signed attestations. Instead of disclosing actual identity information, the system generates verifiable cryptographic proofs that replicate the trust relationship without revealing sensitive personal data, enabling secure communication while preserving privacy.
Solution Approach 2:
A trusted third party acts as a mediator that issues cryptographic attestations verifying identity relationships. These attestations enable parties to establish trust for sensitive communications without directly disclosing identity information, resolving the contradiction between trust establishment and information privacy.
3Reliability
If cryptographic linking methods are implemented to verify party relationships, then identity management and KYC compliance are improved, but the system complexity increases
Solution Approach 1:
The patent creates a universal cryptographic attestation framework that serves multiple functions: KYC compliance, identity verification, trust establishment, and non-blockchain system integration. This multi-functional approach consolidates various identity management requirements into a single standardized system, reducing overall complexity despite the advanced cryptography involved.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer-implemented method of verifying a link between a first party and a second party, the method being performed by a third party and comprising: obtaining, from the second party, i) a message signed with a first signature based on a first private key of the second party, and ii) a first public key corresponding to the first private key; obtaining, from the second party, iii) the message signed with a second signature based on a second private key of the second party, and iv) a second public key corresponding to the second private key; obtaining, from the first party, v) the message signed with a third signature based on a shared private key known only to the first party and the second party, and a corresponding shared public key; and determining whether the second public key of the second party has been generated based on the first public key of the second party and the shared public key.