Federated Directory Service for Decentralized Ledger Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current decentralized distributed ledger systems lack an efficient mechanism for securely managing and accessing customer account details, particularly in a decentralized environment where trust and validation are distributed among multiple nodes, making it difficult to facilitate transactions without compromising user privacy.
Innovation Solution
A decentralized distributed ledger system that hosts a directory service for customer aliases, allowing user data to be stored in a secure, immutable, and pseudoanonymous manner, enabling nodes to validate and manage transactions while keeping sensitive information private by using aliases and tokens, and ensuring data integrity through cryptographic interlocking.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user data is stored in a decentralized distributed ledger system, then data security and privacy are improved, but access efficiency and transaction facilitation deteriorate due to distributed validation requirements
Solution Approach 1:
The system segments user data into two distinct parts: identification information (aliases, contact details) stored in the distributed ledger for security and verification, and sensitive account information (account numbers, routing details) stored locally in contributing entity databases for efficient access. This segmentation allows the system to maintain security through distributed validation while improving access efficiency by storing frequently accessed data in centralized locations that can be queried directly without involving all ledger nodes.
2Reliability
If aliases are used to protect user privacy, then user privacy is improved, but the ability to retrieve accurate account information deteriorates
Solution Approach 1:
The system introduces a directory service as an intermediary layer between aliases and account information. The directory service stores mappings between aliases and contributing entity identifiers in the distributed ledger, enabling privacy protection through alias usage while maintaining accurate account information retrieval. When a transaction requires account details, the system uses the alias to query the directory service, which returns the appropriate contributing entity identifier, ensuring both privacy and accuracy.
3Reliability
If data is stored in contributing entity databases rather than centralized location, then system decentralization and security are improved, but system complexity increases
Solution Approach 1:
The system creates a universal directory service that can be accessed by all contributing entities and requesting entities in the network. This directory service performs multiple functions: storing alias-to-identifier mappings, enabling privacy protection, facilitating cross-entity transactions, and maintaining data integrity through distributed validation. By providing this single universal interface, the system manages the complexity of distributed data storage while maintaining security and enabling efficient access across the entire network.
Data Source
AI summary
Systems and methods are provided for a decentralized distributed ledger that hosts a directory service for customer aliases to facilitate obtaining customer account details. Aspects of the present disclosure may include receiving a request to execute a transaction, wherein the request includes identification information associated with a particular user, transmitting a communication to the database of the existing distributed ledger, wherein the second communication includes a request for an identity of a contributing entity that previously contributed user data associated with the particular user to the database, and wherein the request for the identity of the contributing entity includes an alias associated with the particular user, receiving the identity of the contributing entity, executing a request for account information for the particular user from the contributing entity, wherein the request for account information is transmitted to the contributing entity, receiving account information associated with the particular user, and executing the transaction using the account information.