Distributed Ledger Identifier Change via Signed Key Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing identifier change management in distributed ledger systems requires a trusted third party, which can lead to loss of the decentralized authority feature and potential key leakage due to betrayal or negligence.
Innovation Solution
An identifier change management apparatus and method that allows identifier changes without a trusted third party by using a distributed ledger network with a user terminal capable of managing public and secret keys, issuing transactions with electronic signatures, and verifying conditions for identifier changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a trusted third party is introduced to manage identifier changes, then the reliability of identifier change management is improved, but the decentralized authority feature of the distributed ledger is lost
Solution Approach 1:
The system enables users to autonomously manage their own identifier changes through cryptographic key pairs without requiring external trusted parties. The user terminal generates secret keys and corresponding public keys, and performs identifier changes independently by broadcasting signed transactions to the network, thus maintaining decentralized authority while ensuring reliability through cryptographic verification
Solution Approach 2:
The patent introduces a cryptographic verification mechanism as an intermediary between the user terminal and the distributed ledger network. The public key and signature verification process acts as a trustless mediator that enables reliable identifier changes without requiring a human trusted third party, preserving decentralization while ensuring security
2Ease of operation
If a trusted third party manages keys, then the ease of operation for identifier change is improved, but the risk of key leakage due to betrayal or negligence increases
Solution Approach 1:
Users independently generate and manage their own secret keys using their user terminal without entrusting them to any third party. The system provides automated functions for key generation, transaction signing, and identifier change execution, making the process easy to operate while keeping cryptographic keys secure locally on the user's device
Solution Approach 2:
The patent extracts the trusted third party from the system entirely, removing the source of key leakage risk. Instead of storing keys with a third party, the system design allows users to retain exclusive control of their secret keys while still enabling secure identifier changes through cryptographic proof mechanisms
3Reliability
If multi-signature mechanism is used with trusted third party, then the reliability of identifier change is improved, but the device complexity increases
Solution Approach 1:
The patent removes the trusted third party component from the multi-signature system, reducing complexity while maintaining security. The system uses a simplified model where a single user terminal generates its own key pair and signs identifier change transactions independently, eliminating the need for complex key distribution and coordination among multiple parties
Data Source
AI summary
An identifier change management apparatus according to an embodiment includes: a distributed ledger in which an identifier change program holding a public key used in an identifier change is registered; a distributed ledger management unit that manages the distributed ledger; an identifier change key input unit that receives a secret key used in the identifier change; a transaction issuing unit that issues an identifier change transaction including a signature value of an electronic signature that has been performed using the secret key; and a program control management unit that changes the identifier when the distributed ledger management unit receives the identifier change transaction, by the identifier change program, on condition that the signature value included in the identifier change transaction is verifiable by using the public key.