Hardware Wallet Pairing Transfer via Whitelist Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Hardware wallets connected via Bluetooth can inadvertently match with unauthorized mobile terminals, compromising the security of digital assets stored within them.
Innovation Solution
Implementing a method where a hardware wallet only connects and matches with another mobile terminal if authorized, using a white list to verify terminal information and ensuring that the hardware wallet is matched with the correct terminal before allowing further instructions or connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the hardware wallet communicates via Bluetooth and allows multiple terminal connections, then the ease of operation is improved, but the security is worsened due to unauthorized matching
Solution Approach 1:
The patent implements a white list mechanism that pre-registers authorized terminal information (MAC addresses, device names) before actual connection occurs. When a connection request is received, the system checks whether the requesting terminal's information exists in the white list before establishing the connection. This preliminary verification ensures that only pre-authorized terminals can connect to the hardware wallet, preventing unauthorized matching while maintaining ease of operation for legitimate users.
2Reliability
If the hardware wallet stores terminal information for verification, then the connection security is improved, but the device complexity increases
Solution Approach 1:
The patent extracts the security verification function into a separate white list management module that operates independently from the core wallet functionality. The white list stores only essential terminal identification information (MAC addresses, device names) required for verification, separating the authentication logic from the main connection handling process. This modular extraction reduces overall system complexity while maintaining robust security verification capabilities.
Data Source
AI summary
A method for preventing a hardware wallet from being maliciously paired, comprising: a hardware wallet waiting to receive a connection request; when a connection request is received, determining whether a first terminal sending the connection request has been paired and connected; if so, waiting to receive an instruction of the first terminal; and when receiving a pairing transfer instruction sent by the first terminal, clearing terminal information stored in a whitelist of the hardware wallet. By means of the present technical solution, a hardware wallet can achieve pairing transfer only by means of the authorization of a previously paired terminal, thereby improving the security of the hardware wallet.