Decentralized Identifier Management Across Dual Ledger Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed ledger technology is not suitable for managing decentralized identifiers (DID) and file metadata due to its reliance on a specific administrator, which can lead to a single point of failure and is not appropriate for managing high-commonality information.
Innovation Solution
A user terminal, authentication terminal, and registration terminal that connect to both a decentralized and a centralized distributed ledger network, allowing for the generation and management of decentralized identifiers and tokens, enabling robust and flexible information management by separating the management of DID and file metadata across different networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DID and file metadata are managed by a contract registered in a programmable blockchain, then smart contract functionality is achieved, but a single point of failure is created due to administrator dependency
Solution Approach 1:
The patent segments the management system into two independent parts: a decentralized ledger for storing verification keys and DIDs without administrator control, and a separate programmable blockchain for smart contract functionality. This segmentation eliminates the single point of failure while preserving smart contract capabilities.
Solution Approach 2:
The patent introduces a decentralized identifier (DID) as an intermediary that links the decentralized verification key storage with the programmable blockchain smart contracts. The DID serves as a mediator that enables smart contract functionality without requiring administrator-dependent contracts.
2Device complexity
If all information is managed in a single decentralized ledger, then simplicity is maintained, but flexibility and robustness are reduced
Solution Approach 1:
The patent divides the information management system into two separate ledgers: one for decentralized verification keys and DIDs, and another for smart contract execution. This segmentation increases structural complexity but significantly improves robustness by preventing single-point failures.
Solution Approach 2:
The patent changes the organizational parameter from a single unified ledger to a multi-ledger architecture, where different types of information are stored in separate ledgers with different levels of decentralization, thereby improving overall system robustness.
3Device complexity
If high-commonality information like DID is managed with specific-use information, then management simplicity is achieved, but appropriateness for high-commonality information is reduced
Solution Approach 1:
The patent applies local quality by treating high-commonality information (DIDs and verification keys) differently from specific-use information. DIDs are stored in a purely decentralized ledger without administrator control, while specific-use information can be managed with appropriate smart contracts, optimizing each type of information for its specific requirements.
Data Source
AI summary
A user terminal according to the present embodiment is a user terminal connectable to a first distributed ledger network and a second distributed ledger network, and includes a generation unit, a first control unit, and a second control unit. The generation unit generates a decentralized identifier related to a user using a verification key. The first control unit generates a registration transaction including the verification key and the decentralized identifier, and transmits the registration transaction to the first distributed ledger network. The second control unit generates a token transaction related to issuance of a token, the token transaction including data of the user and the decentralized identifier, and transmits the token transaction to the second distributed ledger network.