Information verification method and device, hardware wallet, terminal equipment and storage medium

Abstract

The application provides an information signature verification method and device, a hardware wallet, a terminal device and a storage medium. The method comprises the following steps: obtaining a hardware wallet ID and a personal certificate of a peer device; determining a corresponding target organization code according to the hardware wallet ID, and determining that the target certificate type is a CA certificate; determining a first target organization public key corresponding to the target organization code and the first type from a pre-stored three-element relationship group of organization codes, certificate types and organization public keys according to the target organization code and the target certificate type; and verifying the personal certificate by using the first target organization public key. Compared with the existing information signature verification process, the scheme does not need to analyze the organization certificate to obtain the first target organization public key, thereby effectively improving the efficiency of obtaining the first target organization public key, and further improving the efficiency of information signature verification, thereby improving the transaction efficiency of digital currency.

Description

Technical Field

[0001] This application relates to the field of digital currency technology, and more specifically, to an information verification method, device, hardware wallet, terminal equipment, and storage medium. Background Technology

[0002] Cryptocurrency is a form of currency in digital form. Currently, an increasing number of cryptocurrency hardware products are being developed. To ensure transactions between hardware wallets issued by different institutions, these wallets must support cross-institutional transactions. That is, a hardware wallet issued by institution A can transact with a hardware wallet issued by institution B.

[0003] Currently, to ensure that hardware wallets support cross-institutional transactions, each hardware wallet needs to be configured with a three-tier certificate system, such as... Figure 1 As shown in the diagram. Root certificates are typically provided by the central bank. Institutional certificates are generated using a private key provided by the central bank, while personal certificates are generated using a private key provided by their respective institutions. In other words, lower-level certificates are signed using the private key corresponding to the higher-level certificate. Therefore, during certificate verification, the public key of the higher-level certificate is needed for signature verification.

[0004] In current cryptocurrency hardware wallet transaction processes, the payer needs to provide the payee with their personal certificate and hardware wallet ID (Identity Document). The payee uses the payer's hardware wallet ID to identify the payer's affiliated institution, obtains the corresponding institution's certificate, parses it, and obtains the institution's public key to authenticate the payer's identity. Similarly, the payee also needs to provide the payer with their personal certificate and hardware wallet ID. The payer uses the payee's hardware wallet ID to identify the payee's affiliated institution, obtains the corresponding institution's certificate, parses it, and obtains the corresponding institution's public key to authenticate the payee's identity and verify the cryptocurrency data.

[0005] Therefore, it's clear that under a three-tier certificate system, the more institutions a hardware wallet supports, the more institution certificates it needs, the more storage space it occupies, and the more time it takes to find the corresponding institution certificate and verify the personal certificate using that certificate during a transaction. However, for the widespread application of cryptocurrency technology, transaction efficiency directly impacts the user experience. Therefore, improving transaction efficiency is a crucial technical aspect for the successful application and promotion of cryptocurrency technology. Summary of the Invention

[0006] The purpose of this application is to provide an information verification method, apparatus, hardware wallet, terminal device and storage medium to improve the transaction efficiency of digital currency.

[0007] This application provides an information signature verification method, including: obtaining the hardware wallet ID and personal certificate of the peer device; determining the corresponding target organization code based on the hardware wallet ID, and determining the target certificate type as a CA (Certification Authority) certificate; determining the first target organization public key corresponding to the target organization code and the first type from a pre-saved ternary relationship group of organization code, certificate type, and organization public key based on the target organization code and the target certificate type; and verifying the personal certificate using the first target organization public key.

[0008] In the above implementation process, by pre-saving a ternary relation group of institution code, certificate type, and institution public key, when personal certificate verification is required, this ternary relation group can be directly searched based on the target institution code and target certificate type to directly obtain the required first target institution public key. Compared with the existing information verification process, there is no need to parse the institution certificate, thus effectively improving the efficiency of obtaining the first target institution public key, thereby improving the efficiency of information verification and ultimately improving the efficiency of cryptocurrency transactions.

[0009] Furthermore, before obtaining the hardware wallet ID and personal certificate of the peer device, the method further includes: obtaining the institution certificates issued by each institution and the institution codes of each institution; verifying the signatures of each institution certificate, and parsing the verified institution certificates to obtain the certificate type and institution public key of each institution certificate; and associating and storing the institution codes, certificate types and institution public keys of each institution to obtain a ternary relationship group of the institution codes, certificate types and institution public keys of each institution.

[0010] In the above implementation process, when obtaining the institution certificates issued by each institution, the institution code corresponding to each institution certificate is obtained, and each institution certificate is verified and signed. The certificate type and institution public key of each institution certificate are obtained by parsing the verified certificate. This enables the associated storage of the institution code, certificate type and institution public key of each institution. This achieves the pre-storage of the ternary relationship group of the institution code, certificate type and institution public key of each institution, ensuring the smooth implementation of the scheme of this application embodiment.

[0011] Furthermore, the method also includes: after successfully associating and saving the organization code, certificate type and public key of any organization, deleting the organization certificate of that organization.

[0012] It should be understood that the internal storage space of a hardware wallet is usually limited, and every bit of storage space is precious. Therefore, in this embodiment of the application, after successfully associating and saving the organization code, certificate type and public key of any organization, the organization certificate of that organization is deleted, thereby saving storage space and improving the effective utilization rate of hardware wallet storage resources.

[0013] Further, the signature verification of each of the aforementioned institution certificates includes: obtaining the root certificate; parsing the root certificate to obtain the root public key within the root certificate; and using the root public key to verify the signature of each of the aforementioned institution certificates.

[0014] Furthermore, the method further includes: upon receiving digital currency data sent by the peer device, determining that the target certificate type is a second type of representation expression certificate; based on the target institution code and the target certificate type, determining the second target institution public key corresponding to the target institution code and the second type from a pre-saved ternary relationship group of institution code, certificate type, and institution public key; and using the second target institution public key to verify the signature of the digital currency data.

[0015] In the above implementation process, by using a ternary relationship group of institution code, certificate type, and institution public key, the public key of the second target institution used for digital currency data verification can be obtained quickly without parsing the institution certificate. This effectively improves the efficiency of obtaining the public key of the second target institution, thereby improving the efficiency of information verification and thus improving the efficiency of digital currency transactions.

[0016] This application embodiment also provides an information verification device, including: an acquisition module, a determination module, and a verification module; the acquisition module is used to acquire the hardware wallet ID and personal certificate of the peer device; the determination module is used to determine the corresponding target organization code based on the hardware wallet ID, and determine the target certificate type as a first type representing a CA certificate; and is used to determine the first target organization public key corresponding to the target organization code and the first type from a pre-stored ternary relationship group of organization code, certificate type, and organization public key based on the target organization code and the target certificate type; the verification module is used to verify the personal certificate using the first target organization public key.

[0017] Furthermore, the device also includes a processing module and a storage module; the acquisition module is further configured to acquire the institution certificates issued by each institution and the institution codes of each institution before acquiring the hardware wallet ID and personal certificate of the peer device; the signature verification module is further configured to verify the signatures of each institution certificate; the processing module is configured to parse the institution certificates that have passed the signature verification to obtain the certificate type and institution public key of each institution certificate; the storage module is configured to associate and store the institution code, certificate type and institution public key of each institution to obtain a ternary relationship group of the institution code, certificate type and institution public key of each institution.

[0018] This application also provides a hardware wallet, including: a processing chip and a storage module; the processing chip is used to execute one or more programs stored in the storage module to implement any of the above-mentioned information verification methods.

[0019] This application embodiment also provides a terminal device, including: a terminal body, an installation position disposed on the terminal body, and the aforementioned hardware wallet; wherein the hardware wallet is installed on the installation position and is communicatively connected to the terminal body.

[0020] This application also provides a readable storage medium that stores one or more programs that can be executed by one or more processors to implement any of the above-described information verification methods. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 A schematic diagram of a three-tiered certificate system provided for existing technologies;

[0023] Figure 2 A flowchart illustrating an information verification method provided in this application embodiment;

[0024] Figure 3 A schematic diagram of a ternary relation group provided in an embodiment of this application;

[0025] Figure 4 A schematic diagram of a typical storage structure for certificates provided for existing technologies;

[0026] Figure 5An interactive schematic diagram of an information verification process provided in an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of the structure of an information verification device provided in an embodiment of this application;

[0028] Figure 7 A schematic diagram of the structure of a more specific information verification device provided in this application embodiment;

[0029] Figure 8 This is a schematic diagram of the structure of a hardware wallet provided in an embodiment of this application. Detailed Implementation

[0030] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0031] Example 1:

[0032] To improve the efficiency of digital currency transactions, this application provides an information verification method. See also... Figure 2 As shown, Figure 2 This is a flowchart illustrating the information verification method provided in the embodiments of this application, including:

[0033] S201: Obtain the hardware wallet ID and personal certificate of the peer device.

[0034] It should be understood that the solutions provided in this application embodiment are applied to hardware wallets. In this application embodiment, a hardware wallet is hardware used to realize digital currency transactions, and it can be implemented in the form of smart cards, USB tokens, etc.

[0035] In practical applications, digital currency transactions require the collaboration of both the payer and the payee, and both the payer and the payee need to verify their identities throughout the entire transaction process.

[0036] In this embodiment, the peer device is relative to the local device. The local device refers to the hardware wallet that executes the solution provided in this embodiment, which can be either the recipient's hardware wallet or the payer's hardware wallet. When the local device is the recipient's hardware wallet, the peer device is the payer's hardware wallet; when the local device is the payer's hardware wallet, the peer device is the recipient's hardware wallet.

[0037] In actual transactions, before obtaining sensitive data such as digital currency, both the payer and payee need to verify their identities, that is, send their hardware wallet ID and personal certificate to the other party for verification.

[0038] In this embodiment, a wireless communication module (such as a Bluetooth module, an NFC (Near Field Communication) module, etc.) can be configured in the hardware wallet to enable direct data interaction between hardware wallets. Alternatively, the hardware wallet can be installed as a peripheral on a corresponding terminal device, using the terminal device as a data intermediary to achieve data interaction between the payer and payee.

[0039] S202: Determine the corresponding target authority code based on the hardware wallet ID, and determine the target certificate type as the first type representing the CA certificate.

[0040] It should be understood that hardware wallets are issued by relevant institutions, such as the Agricultural Bank of China, which has authorization to manage digital currencies. Each institution will assign a unique hardware wallet ID to each issued hardware wallet.

[0041] In this embodiment of the application, the organization code of each organization and the corresponding hardware wallet ID range of each organization can be pre-written into the hardware wallet, so as to determine the target organization code to which the peer device belongs based on the hardware wallet ID.

[0042] Furthermore, it's important to understand that in practical applications, institutions typically issue two types of certificates: CA certificates and expression certificates. CA certificates are primarily used for identity verification, while expression certificates are used for verifying the signature of cryptocurrency-related data (hereinafter referred to as cryptocurrency data) during cryptocurrency transactions.

[0043] In this embodiment of the application, in order to facilitate the hardware wallet in determining the currently required certificate type, it can be pre-configured that: when a personal certificate is received from the peer device, the target certificate type is determined to be the first type representing a CA certificate; when digital currency data is received from the peer device, the target certificate type is determined to be the second type representing an expression certificate.

[0044] In this way, when the hardware wallet obtains the personal certificate of the peer device, it can determine that the required certificate type is the first type representing the CA certificate.

[0045] S203: Based on the target organization code and the target certificate type, determine the target organization code and the first target organization public key corresponding to the first type from the pre-saved ternary relationship group of organization code, certificate type, and organization public key.

[0046] It should be understood that in practical applications, some basic information about the hardware wallet will be configured before it is issued to the user. For example, the institution code for each organization and the range of hardware wallet IDs corresponding to each organization.

[0047] In this embodiment of the application, the ternary relationship group of organization code, certificate type and organization public key can be saved during the configuration of basic information.

[0048] In this embodiment of the application, the organization certificates issued by each organization and the organization codes of each organization can be obtained during the process. Then, the certificates of each organization are verified, and the certificates of each organization that pass the verification are parsed to obtain the certificate type and the organization's public key.

[0049] Then, the organization code, certificate type, and public key of each organization are associated and stored to obtain a ternary relation group of the organization code, certificate type, and public key of each organization.

[0050] It should be understood that in practical applications, certificates from various organizations are typically stored in hardware wallets in TLV format (TLV is a data encoding method where T represents a tag, L represents the length, and V represents the value). The tag records the type of the certificate (for example, a tag value of 0xF8 indicates a CA certificate, and a tag value of 0xF9 indicates an expression certificate). Therefore, in this embodiment, the certificate type of an organization can be obtained from its tag by parsing the organization certificate.

[0051] It should also be understood that, in the embodiments of this application, the ternary relationship group of organization code, certificate type, and organization public key can be referred to... Figure 3 As shown, Figure 3 Each row in the table represents a ternary relation group.

[0052] It should be noted that the current common method for storing certificates is as follows: Figure 4 As shown, both the organization code and certificate are stored in TLV format. In this embodiment, to save storage resources, the organization code, certificate type, and organization public key can be stored in value form only.

[0053] It is worth noting that, in this embodiment of the application, after successfully associating and saving the organization code, certificate type and public key of any organization, the organization certificate of that organization can be deleted, thereby avoiding the invalid occupation of storage resources in the hardware wallet and improving the effective utilization rate of storage resources in the hardware wallet.

[0054] It should be understood that since the authority certificate was verified before being deleted, and the hardware wallet does not need to output the authority certificate to the outside world during subsequent transactions, outputting the authority certificate will not affect the security of the hardware wallet.

[0055] It is also worth noting that, in this embodiment of the application, in order to verify the signatures of each institution's certificate, the root certificate can be obtained first, then the root certificate can be parsed to obtain the root public key in the root certificate, and then the root public key can be used to verify the signatures of each institution's certificate.

[0056] It should be understood that the root certificate described in this application embodiment can be issued by the legal issuing institution of the digital currency. For example, for the digital RMB, the root certificate can be a certificate issued by the People's Bank of China.

[0057] It should be noted that, in this embodiment, the certificate type can be recorded using various preset values. For example, A can be used to represent the first type and B to represent the second type; or 0 can be used to represent the first type and 1 to represent the second type. The specific form of the certificate type recording value is not limited in this embodiment.

[0058] It should be noted that, in this embodiment, the hardware wallet can store the root certificate. Therefore, after the hardware wallet is issued to the user, if a compatible organization needs to be added, the root certificate can be used to verify the certificate of the new organization. After successful verification, the organization code, certificate type, and public key of the new organization are associated and saved. It should be understood that the method for obtaining the organization code, certificate type, and public key of the new organization is the same as described above.

[0059] S204: Verify the signature of the personal certificate using the public key of the first target organization.

[0060] In this embodiment of the application, the personal certificate sent by the peer device will be signed using the private key corresponding to the CA certificate of the issuing authority.

[0061] If the organization to which the first target organization's public key belongs is the same as the organization to which the personal certificate belongs, then the signature verification will be successful, and subsequent operations can proceed.

[0062] It should be understood that in practical applications, subsequent transaction operations will only proceed after both the payer and payee have verified and approved the other party's personal credentials. If either party fails to verify the credentials, the transaction process ends.

[0063] It is important to note that after entering the subsequent transaction process, the payer and payee will interact with data involving digital currencies (such as cryptocurrency strings).

[0064] During this process, after obtaining the cryptocurrency data from the peer device, the hardware wallet determines that the target certificate type is the second type of representation expression certificate. Then, based on the target institution code and target certificate type, it retrieves the second target institution public key corresponding to the institution code and expression certificate from the ternary relationship group of institution code, certificate type, and institution public key. This second target institution public key is then used to verify the cryptocurrency data. If the verification passes, the cryptocurrency data is considered legitimate, and subsequent operations can proceed. If the verification fails, the transaction can be terminated, and an error message will be displayed.

[0065] It should be noted that the digital currency described in this application embodiment can be a virtual currency with monetary attributes, such as digital RMB.

[0066] The information verification method provided in this application pre-stores a ternary relation group consisting of an organization code, certificate type, and organization public key. When personal certificate verification is required, this ternary relation group can be directly searched based on the target organization code and target certificate type to directly obtain the required first target organization public key. Compared to existing information verification processes, this eliminates the need for organization certificate parsing, effectively improving the efficiency of obtaining the first target organization public key, thereby increasing the efficiency of information verification and ultimately improving the efficiency of cryptocurrency transactions.

[0067] Example 2:

[0068] Based on Embodiment 1, this embodiment takes the identity authentication process of the payer and payee in a digital RMB transaction as an example to further illustrate this application.

[0069] See Figure 5 As shown, assuming the payer is a hardware wallet with near-field communication (NFC) capability, and the payee's hardware wallet is set up on a terminal device, the payer interacts with the payee's hardware wallet through the payee's terminal device.

[0070] First, the terminal device initializes the payer for the transaction based on the user's operation, sending the required transaction amount and the current timestamp, among other payer initialization information, to the payer's hardware wallet.

[0071] After receiving the payer's initialization information, the payer's hardware wallet packages its own personal certificate and hardware wallet ID into response data and sends it to the terminal device.

[0072] The terminal device parses the response data and transmits the payer's hardware wallet's personal certificate and hardware wallet ID as the payee's initialization information to its own hardware wallet.

[0073] The recipient's hardware wallet determines the target certificate type to be the first type representing a CA certificate and determines the corresponding target organization code based on the hardware wallet ID. Then, it retrieves the CA certificate public key corresponding to the target organization code and the first type from the pre-saved ternary relationship group of each organization code, certificate type, and organization public key, and uses this CA certificate public key to verify the signature of the payer's personal certificate.

[0074] After successful verification, the user packages their personal certificate and hardware wallet ID into a response data transmission and sends it to the terminal device.

[0075] The terminal device sends the recipient's personal certificate and hardware wallet ID to the payer's hardware wallet.

[0076] The payer's hardware wallet determines that the recipient's target certificate type is the first type representing a CA certificate, and determines the recipient's corresponding target organization code based on the recipient's hardware wallet ID. Then, from the pre-saved ternary relationship group of each organization code, certificate type, and organization public key, it finds the recipient's target organization code and the CA certificate public key corresponding to the first type, and uses the CA certificate public key to verify the recipient's personal certificate.

[0077] If either party fails to verify the signature, the subsequent process will terminate and an error message will be displayed.

[0078] In the above scheme, the ternary relationship group of each institution code, certificate type, and institution public key is configured during the configuration of basic information.

[0079] That is, before distributing hardware wallets to users, the root certificate issued by the People's Bank of China, as well as the institutional certificates and institutional codes issued by various institutions, are obtained. Then, the root certificate is parsed to obtain the root public key.

[0080] The root public key is used to verify the signatures of each organization's certificate. The verified certificates are then parsed to obtain the certificate type and the organization's public key.

[0081] The system associates and stores the organization code, certificate type, and public key of each organization, and deletes the certificates of each organization.

[0082] The above scheme simplifies the process of verifying personal certificates using institutional certificates. It directly retrieves the corresponding institutional public key based on the institutional code and certificate type, eliminating the need to parse the institutional certificate to obtain the public key and then use it for verification. This improves performance. Furthermore, since the institutional certificate is verified before deletion, and the hardware wallet does not need to output the institutional certificate externally during subsequent transactions, outputting the institutional certificate does not compromise the hardware wallet's security.

[0083] Example 3:

[0084] Based on the same inventive concept, this application also provides an information verification device 100 in its embodiments. Please refer to... Figure 6 and Figure 7 As shown, Figure 6 It shows the use of Figure 2 The method shown is an information verification device. It should be understood that the specific functions of device 100 can be found in the description above; to avoid repetition, detailed descriptions are appropriately omitted here. Device 100 includes at least one software function module that can be stored in memory or embedded in the operating system of device 100 in the form of software or firmware. Specifically:

[0085] See Figure 6 As shown, the device 100 includes: an acquisition module 101, a determination module 102, and a signature verification module 103. Wherein:

[0086] The acquisition module 101 is used to acquire the hardware wallet ID and personal certificate of the peer device;

[0087] The determining module 102 is used to determine the corresponding target organization code based on the hardware wallet ID, and to determine the target certificate type as a first type representing a CA certificate; and to determine the first target organization public key corresponding to the target organization code and the first type from a pre-saved ternary relationship group of organization code, certificate type, and organization public key based on the target organization code and the target certificate type.

[0088] The signature verification module 103 is used to verify the personal certificate using the public key of the first target organization.

[0089] In one possible implementation of the embodiments of this application, see [link to relevant documentation]. Figure 7 As shown, the device 100 may further include a processing module 104 and a storage module 105. Wherein:

[0090] The acquisition module 101 is also used to acquire the institution certificates issued by each institution and the institution codes of each institution before acquiring the hardware wallet ID and personal certificate of the peer device;

[0091] The verification module 103 is also used to verify the certificates of each of the institutions.

[0092] The processing module 104 is used to parse the certificates of each institution that have passed the signature verification to obtain the certificate type and institution public key of each certificate.

[0093] The storage module 105 is used to associate and store the institution code, certificate type and institution public key of each institution, so as to obtain a ternary relationship group of the institution code, certificate type and institution public key of each institution.

[0094] In the above feasible implementation, the processing module 104 can also be used to delete the institution's institution certificate after successfully associating and saving the institution code, certificate type and institution public key of any institution.

[0095] In the above feasible implementation, the acquisition module 101 is further used to acquire the root certificate; the signature verification module 103 is specifically used to parse the root certificate, obtain the root public key in the root certificate, and use the root public key to verify the signatures of each of the institution certificates.

[0096] In this embodiment of the application, the determining module 102 is further configured to determine, upon receiving digital currency data sent by the peer device, that the target certificate type is the second type of representation expression certificate; and to determine, based on the target institution code and the target certificate type, the second target institution public key corresponding to the target institution code and the second type from a pre-saved ternary relationship group of institution code, certificate type, and institution public key; the signature verification module 103 is further configured to verify the digital currency data using the second target institution public key.

[0097] It should be understood that, for the sake of brevity, some of the content described in Embodiment 1 will not be repeated in this embodiment.

[0098] Example 4:

[0099] This embodiment provides a hardware wallet, see [link / reference] Figure 8 As shown, it includes a processing chip 801 and a storage module 802. Wherein:

[0100] The processing chip 801 is used to execute one or more programs stored in the storage module 802 to implement the information verification method in Embodiment 1 and / or Embodiment 2.

[0101] Understandable. Figure 8 The structure shown is for illustrative purposes only; hardware wallets may also include more. Figure 8 The more or fewer components shown, or having the same Figure 8 The different configurations shown can include wireless communication modules such as Bluetooth and NFC, or wired communication modules in the form of metal contacts.

[0102] It should be noted that the processing chip 801 in this embodiment can be implemented using various existing chips with data processing capabilities. The storage module 802 can be implemented using various non-volatile memories.

[0103] In this embodiment, the hardware wallet can be implemented in the form of a smart card, a USB security token, etc., and no limitation is imposed in this embodiment.

[0104] In this embodiment, the hardware wallet can independently execute the information verification method in this embodiment, or it can be set in a terminal device to implement the information verification method in this embodiment.

[0105] Therefore, this application also provides a terminal device, which includes: a terminal body, an installation position disposed on the terminal body, and a hardware wallet capable of implementing the information verification method in this application. The hardware wallet is installed on the installation position and is communicatively connected to the terminal body.

[0106] In this embodiment, the installation slot can be configured according to the implementation of the hardware wallet. For example, for a smart card-type hardware wallet, an installation method similar to that of a SIM card can be used to construct the installation slot on the terminal device. For a USB key-type hardware wallet, the installation slot can be constructed by setting a USB interface or other methods.

[0107] This embodiment also provides a readable storage medium, such as a floppy disk, optical disk, hard disk, flash memory, USB flash drive, SD (Secure Digital Memory Card), MMC (Multimedia Card), etc., in which one or more programs implementing the above steps are stored. These one or more programs can be executed by one or more processors to implement the information verification method in Embodiment 1 and / or Embodiment 2. Further details will not be elaborated here.

[0108] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0109] Furthermore, the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0110] Furthermore, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0111] In this document, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, without necessarily requiring or implying any such actual relationship or order between these entities or operations.

[0112] In this article, "multiple" refers to two or more.

[0113] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. An information verification method, characterized in that, Obtain the hardware wallet ID and personal certificate of the peer device; The corresponding target authority code is determined based on the hardware wallet ID, and the target certificate type is determined to be the first type representing a CA certificate; The CA certificate is used for identity verification and signature. Based on the target organization code and the target certificate type, the first target organization public key corresponding to the target organization code and the first type is determined from the pre-saved ternary relationship group of organization code, certificate type, and organization public key; The personal certificate is verified using the public key of the first target organization.

2. The information signature verification method of claim 1, wherein Before obtaining the hardware wallet ID and personal certificate of the peer device, the method further includes: Obtain the institution certificates issued by each institution and the institution codes of each institution; The certificates of each institution are verified and signed, and the certificates of each institution that pass the verification are parsed to obtain the certificate type and institution public key of each certificate; The organization code, certificate type, and public key of each organization are associated and stored to obtain a ternary relation group of the organization code, certificate type, and public key of each organization.

3. The information signature verification method of claim 2, wherein The method further includes: After successfully saving the organization code, certificate type, and public key of any organization, delete the organization certificate of that organization.

4. The information signature verification method of claim 2, wherein Verification and signing of certificates from each of the aforementioned institutions, including: Obtain the root certificate; Parse the root certificate to obtain the root public key within the root certificate; The root public key is used to verify the signatures of each of the aforementioned institution certificates.

5. The information signature verification method according to any one of claims 1 to 4, characterized by, The method further includes: Upon receiving digital currency data from the peer device, the target certificate type is determined to be the second type of representation expression certificate; Based on the target organization code and the target certificate type, the second target organization public key corresponding to the target organization code and the second type is determined from the pre-saved ternary relationship group of organization code, certificate type, and organization public key; The digital currency data is verified using the public key of the second target institution.

6. An information signature verification device, characterized by comprising: include: The module includes an acquisition module, a confirmation module, and a signature verification module. The acquisition module is used to acquire the hardware wallet ID and personal certificate of the peer device; The determining module is used to determine the corresponding target organization code based on the hardware wallet ID, and to determine the target certificate type as a first type representing a CA certificate; And for determining, based on the target institution code and the target certificate type, the first target institution public key corresponding to the first type from a pre-stored ternary relationship group of institution code, certificate type, and institution public key; The CA certificate is used for identity verification and signature. The signature verification module is used to verify the personal certificate using the public key of the first target organization.

7. The information signature verification device of Claim 6, wherein The device also includes a processing module and a storage module; The acquisition module is also used to acquire the institution certificates issued by each institution and the institution codes of each institution before acquiring the hardware wallet ID and personal certificate of the peer device; The signature verification module is also used to verify the signatures of the certificates of each of the institutions. The processing module is used to parse the certificates of each institution that have passed the signature verification to obtain the certificate type and institution public key of each certificate. The storage module is used to associate and store the institution code, certificate type and institution public key of each institution, so as to obtain a ternary relationship group of the institution code, certificate type and institution public key of each institution.

8. A hardware wallet, characterized in that, include: Processing chips and storage modules; The processing chip is used to execute one or more programs stored in the storage module to implement the information verification method as described in any one of claims 1 to 5.

9. A terminal device, comprising: include: The terminal body, the mounting position disposed on the terminal body, and the hardware wallet as described in claim 8; The hardware wallet is installed in the mounting position and communicates with the terminal body.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processing chips to implement the information verification method as described in any one of claims 1 to 5.

Images