Blockchain account verification method and device, storage medium and equipment
By extending the processing of the private key of a blockchain account and combining it with privacy information and the verification value of the exchange to generate an account fingerprint, the problems of user privacy leakage and low interaction efficiency in blockchain account verification are solved, and efficient and secure user identity verification is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- HANGZHOU RIVTOWER TECH CO LTD
- Filing Date
- 2022-11-21
- Publication Date
- 2026-07-21
AI Technical Summary
The verification process for blockchain accounts suffers from issues such as leakage of user privacy information and low interaction efficiency.
By using privacy information to extend the private key of a blockchain account to obtain an extended private key, and combining the exchange's verification value with the extended public key to generate an account fingerprint, regulatory devices can verify the user's identity without obtaining the blockchain account's private key.
It protects the privacy of user assets, improves the efficiency of the verification process, and reduces the data processing burden on exchanges and regulatory devices.
Smart Images
Figure CN115719228B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of blockchain technology, and in particular to a method, apparatus, storage medium and device for verifying blockchain accounts. Background Technology
[0002] A blockchain account address is a hash string, which typically doesn't directly reveal the account owner's identity. When a user discovers their blockchain account has been stolen or they've encountered fraudulent transactions, they need to prove ownership. This usually requires the user to collaborate with the exchange to provide regulatory agencies with their exchange login account and password (equivalent to providing the user's private key on the exchange), a cumbersome process that exposes their asset ownership credentials. For regulatory agencies, when monitoring suspected illegal blockchain accounts, each instance requires exchange intervention, resulting in low efficiency. Summary of the Invention
[0003] This application provides a method, apparatus, storage medium, and device for verifying blockchain accounts, addressing the problems of easy leakage of user assets and low interaction efficiency when verifying blockchain accounts based on privacy information such as exchange login accounts and passwords. The technical solution is as follows:
[0004] On the one hand, a method for verifying blockchain accounts is provided, the method comprising:
[0005] The monitoring device obtains the user's privacy information and transaction records, and obtains the verification value of the exchange. The transaction records are obtained by signing the transaction content using the user's extended private key. The extended private key is obtained by extending the private key of the blockchain account using the privacy information.
[0006] The monitoring device uses the extended public key corresponding to the extended private key to decrypt the signature of the transaction record and obtain the first account fingerprint in the transaction content. The first account fingerprint is generated in advance based on the user's privacy information, the transaction's verification value and the extended public key.
[0007] The monitoring device generates a second account fingerprint based on the obtained privacy information, the verification value, and the extended public key corresponding to the transaction record;
[0008] If the fingerprint of the first account is the same as the fingerprint of the second account, the monitoring device determines that the user is the holder of the blockchain account.
[0009] In one possible implementation, the monitoring device obtains the user's privacy information and transaction records, including:
[0010] The monitoring device acquires the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records;
[0011] The monitoring device performs a hash calculation on the combination of the identity identifier and the user identifier to obtain the privacy information.
[0012] In one possible implementation, the method further includes: the monitoring device receiving a verification request sent by the user device, the verification request including the identity identifier, the user identifier, and the transaction record;
[0013] The monitoring device obtains the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records, including: the monitoring device reads the identity identifier, the user identifier, and the transaction records from the verification request.
[0014] In one possible implementation, the monitoring device acquires the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records, including:
[0015] The monitoring device acquires the transaction records of the blockchain account to be monitored, and obtains the user's identity identifier based on the transaction records;
[0016] The regulatory device sends a first acquisition request carrying the identity identifier to the exchange device. The first acquisition request is used to instruct the exchange device to send the user identifier corresponding to the identity identifier to the regulatory device.
[0017] The monitoring device receives the user identifier.
[0018] In one possible implementation, when the verification value is periodically updated, obtaining the exchange's verification value includes:
[0019] The monitoring device obtains the timestamp of the transaction record;
[0020] The regulatory device sends a second acquisition request carrying the timestamp to the exchange device. The second acquisition request is used to instruct the exchange device to obtain the verification value corresponding to the timestamp from a preset first mapping table and send the verification value to the regulatory device. The first mapping table stores the correspondence between timestamps and verification values.
[0021] The monitoring device receives the verification value.
[0022] In one possible implementation, when different monitoring devices correspond to different verification values, the method further includes:
[0023] The monitoring equipment obtains its own device identifier;
[0024] The regulatory device sends a third acquisition request carrying the device identifier to the exchange device. The third acquisition request is used to instruct the exchange device to obtain the verification value corresponding to the device identifier from a preset second mapping table and send the verification value to the regulatory device. The second mapping table stores the correspondence between device identifiers and verification values.
[0025] The monitoring device receives the verification value.
[0026] In one possible implementation, the transaction content is obtained by appending the fingerprint of the first account to the transaction data.
[0027] On the one hand, a blockchain account verification device is provided, the device comprising:
[0028] The acquisition module is used to acquire the user's privacy information and transaction records, and to acquire the verification value of the exchange. The transaction records are obtained by signing the transaction content using the user's extended private key. The extended private key is obtained by extending the private key of the blockchain account using the privacy information.
[0029] The decryption module is used to decrypt the signature of the transaction record using the extended public key corresponding to the extended private key, and obtain the first account fingerprint in the transaction content. The first account fingerprint is generated in advance based on the user's privacy information, the verification value of the transaction and the extended public key.
[0030] The generation module is used to generate a second account fingerprint based on the obtained privacy information, the verification value, and the extended public key corresponding to the transaction record;
[0031] The determination module is used to determine that the user is the holder of the blockchain account if the first account fingerprint is the same as the second account fingerprint.
[0032] On the one hand, a computer-readable storage medium is provided, wherein at least one instruction is stored in the storage medium, the at least one instruction being loaded and executed by a processor to implement the blockchain account verification method as described above.
[0033] On one hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, the instruction being loaded and executed by the processor to implement the blockchain account verification method as described above.
[0034] The beneficial effects of the technical solutions provided in this application include at least the following:
[0035] By extending the private key of a blockchain account using privacy information to obtain an extended private key, and then using the privacy information, the exchange's verification value, and the extended public key to generate a first account fingerprint, the transaction content is obtained by appending the first account fingerprint to the transaction data. Finally, the transaction content is signed using the extended private key. The monitoring device only needs to obtain the transaction record, privacy information, and the verification value provided by the exchange to verify whether the second account fingerprint generated based on the privacy information, verification value, and transaction record is the same as the first account fingerprint, thereby determining whether the user is the holder of the blockchain account. During the blockchain account verification process, the monitoring device does not need to obtain the blockchain account's private key, thus preventing the leakage of user assets. Furthermore, the exchange only needs to provide the verification value, and the monitoring device can independently verify the blockchain account through algorithms, improving the efficiency of the interaction.
[0036] User devices can proactively send identity identifiers, user identifiers, and transaction records to regulatory devices, enabling self-providence and facilitating the verification of blockchain accounts by regulatory devices. Attached Figure Description
[0037] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0038] Figure 1 This is a structural block diagram of a blockchain account verification system provided in one embodiment of this application;
[0039] Figure 2 This is a flowchart of a blockchain account verification method provided in one embodiment of this application;
[0040] Figure 3 This is a structural block diagram of a blockchain account verification device provided in one embodiment of this application. Detailed Implementation
[0041] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.
[0042] When the application scenario involves regulatory agencies proactively verifying blockchain accounts, multiple regulatory devices 110 and multiple exchange devices 120 participate in the verification process. When the application scenario involves users voluntarily providing evidence to verify blockchain accounts, multiple regulatory devices 110, multiple exchange devices 120, and multiple user devices 130 participate in the verification process. Figure 1 As shown.
[0043] Regulatory device 110 is an electronic device used by regulatory agencies. When multiple regulatory agencies exist, each agency corresponds to one regulatory device 110. Each regulatory device 110 is equipped with a verification algorithm to verify whether a user is the holder of a blockchain account, that is, whether the user has ownership of the blockchain account.
[0044] Exchange device 120 is an electronic device used for trading. When multiple exchanges exist, each exchange corresponds to one exchange device 120. Each exchange device 120 provides information to regulatory device 110 so that regulatory device 110 can verify blockchain accounts based on that information. It should be noted that the information provided by exchange device 120 does not include the user's blockchain account private key, thus ensuring that the user's assets are not disclosed.
[0045] User device 130 is an electronic device used by a user. When multiple users exist, each user corresponds to one user device 130. Each user device is used to provide information to the monitoring device 110 so that the monitoring device 110 can verify the blockchain account based on that information. It should be noted that the information provided by user device 130 does not include the user's blockchain account private key, thereby ensuring that the user's assets are not disclosed.
[0046] In this embodiment, hierarchical deterministic (HD) wallet technology can be used to extend the private key of the blockchain account using privacy information to obtain an extended private key. That is, private key + privacy information => extended private key.
[0047] For example, when user A transfers money to user B, the actual chain is: user A => the supervised address corresponding to the extended private key => (transfer) user B => the transaction record of the transfer is generated.
[0048] The generation of transaction records may include the following steps:
[0049] (1) Generate user privacy information.
[0050] Specifically, it can obtain the user's identity identifier and the user identifier assigned to the user by the exchange, and perform a hash calculation on the combination of the identity identifier and the user identifier to obtain privacy information. The pseudocode for the calculation logic is: Privacy information = shasum(identity identifier, user identifier); / / shasum is a publicly available hash algorithm, which can be SHA256, SM3, MD5, etc.; the identity identifier can be the user's resident ID card number, mobile phone number, digital biometric information, etc.; the user identifier is a unique identifier assigned to the user by the exchange when the user registers an account on the exchange.
[0051] (2) Generate an extended private key.
[0052] Specifically, the private key and privacy information of the blockchain account can be obtained, and the private key and privacy information can be added together to obtain the extended private key. The pseudocode for the calculation logic is: TransactionPrivateKey = (userPrivateKey + privacy information); / / TransactionPrivateKey is the extended private key, and userPrivateKey is the private key of the blockchain account.
[0053] (3) Generate account fingerprint.
[0054] Specifically, the verification value, privacy information, and extended public key of the exchange can be obtained. An account fingerprint generation algorithm is then used to calculate the account fingerprint using these three elements. The pseudocode for the calculation logic is: Account Fingerprint = Account Fingerprint Generation Algorithm(Verification Value + Privacy Information + TransactionPrivateKey.Public Key); / / The account fingerprint generation algorithm can be a publicly available hash algorithm.
[0055] (4) Generate transaction details.
[0056] The transaction content is obtained by appending the account fingerprint to the transaction data. The pseudocode for the calculation logic is: Transaction content = Transaction content.data + Account fingerprint; / / Transaction content.data is the transaction data.
[0057] (5) Generate transaction records.
[0058] Specifically, the extended private key and transaction content can be obtained, and the transaction content can be signed using the extended private key. The pseudocode for the calculation logic is: Transaction record = TransactionPrivateKey.sign(transaction content).
[0059] After generating transaction records using the above method, the monitoring device can verify the blockchain account based on privacy information, transaction records, and verification values. See details below. Figure 2 The example shown.
[0060] Please refer to Figure 2 It illustrates a flowchart of a blockchain account verification method provided in one embodiment of this application, which can be applied to [various applications]. Figure 1 The monitoring device shown. The verification method for this blockchain account may include:
[0061] Step 201: The monitoring device obtains the user's privacy information and transaction records, and obtains the verification value of the exchange. The transaction records are obtained by signing the transaction content using the user's extended private key. The extended private key is obtained by extending the private key of the blockchain account using the privacy information.
[0062] Specifically, the acquisition of user privacy information and transaction records by the monitoring device may include: the monitoring device acquiring the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records; the monitoring device performing a hash calculation on the combination of the identity identifier and the user identifier to obtain the privacy information. The calculation method for the privacy information is the same as the calculation method described above, and will not be repeated in this embodiment.
[0063] In practical applications, users can initiate the verification process for blockchain accounts by providing evidence themselves, or regulatory agencies can initiate the verification process for blockchain accounts proactively. The following sections will explain these two triggering methods.
[0064] The first triggering method is: the monitoring device receives a verification request sent by the user device, which includes an identity identifier, a user identifier, and transaction records; the monitoring device reads the identity identifier, user identifier, and transaction records from the verification request.
[0065] The second triggering method is as follows: the regulatory device obtains the transaction records of the blockchain account to be monitored, and obtains the user's identity identifier based on the transaction records; the regulatory device sends a first acquisition request carrying the identity identifier to the exchange device, which instructs the exchange device to send the user identifier corresponding to the identity identifier to the regulatory device; the regulatory device receives the user identifier.
[0066] Among them, the regulatory equipment can obtain the user's identity identifier based on big data analysis, and then obtain the user's identifier from the exchange equipment based on the identity identifier.
[0067] In this embodiment, the exchange can periodically update the verification value, making it time-sensitive and avoiding the problem of the verification value becoming permanently valid after being leaked. In this case, the monitoring device needs to obtain the verification value corresponding to the timestamp of the transaction record.
[0068] Specifically, the regulatory device obtains the timestamp of the transaction record; the regulatory device sends a second acquisition request carrying the timestamp to the exchange device, the second acquisition request being used to instruct the exchange device to obtain the verification value corresponding to the timestamp from a preset first mapping table, and send the verification value to the regulatory device, the first mapping table storing the correspondence between timestamps and verification values; the regulatory device receives the verification value.
[0069] In this embodiment, the exchange can set different verification values for different regulatory agencies. This avoids the problem of verification value leakage caused by sharing the same verification value, and also avoids the problem of other verification values becoming invalid due to the expiration of one verification value. In this case, the regulatory device needs to obtain the verification value corresponding to its own device identifier.
[0070] Specifically, the regulatory device obtains its own device identifier; the regulatory device sends a third acquisition request carrying the device identifier to the exchange device, the third acquisition request being used to instruct the exchange device to obtain the verification value corresponding to the device identifier from a preset second mapping table, and send the verification value to the regulatory device, the second mapping table storing the correspondence between device identifiers and verification values; the regulatory device receives the verification value.
[0071] Step 202: The monitoring device uses the extended public key corresponding to the extended private key to decrypt the signature of the transaction record and obtain the first account fingerprint in the transaction content. The first account fingerprint is generated in advance based on the user's privacy information, the transaction's verification value and the extended public key.
[0072] For ease of distinction, in this embodiment, the account fingerprint in the transaction record is referred to as the first account fingerprint, and the account fingerprint calculated by the monitoring device is referred to as the second account fingerprint.
[0073] The monitoring device can use the extended public key to decrypt the signature of the transaction record and obtain the first account fingerprint appended to the transaction data from the obtained transaction content.
[0074] Step 203: The monitoring device generates a second account fingerprint based on the obtained privacy information, verification value, and extended public key corresponding to the transaction record.
[0075] The pseudocode for calculating the second account fingerprint is: Second account fingerprint = Generating account fingerprint algorithm (verification value + privacy information + TransactionPrivateKey.public key).
[0076] Step 204: If the fingerprint of the first account is the same as that of the second account, the monitoring device determines that the user is the holder of the blockchain account.
[0077] The monitoring device can compare the first account fingerprint in the transaction record with the generated second account fingerprint. If the first account fingerprint is the same as the second account fingerprint, it is determined that the user is the holder of the blockchain account; if the first account fingerprint is different from the second account fingerprint, it is determined that the user is not the holder of the blockchain account.
[0078] In this embodiment, transaction records are publicly available to all parties, identity identifiers are shared among users, exchanges, and regulatory agencies, verification values are shared between exchanges and regulatory agencies, and user identifiers are shared among users, exchanges, and regulatory agencies. Regulatory agencies can verify blockchain accounts based on these four types of information without obtaining the blockchain account's private key, thus preventing unauthorized manipulation of user assets and protecting user privacy. Furthermore, exchange equipment does not need to provide all raw data, and regulatory equipment does not need to acquire, analyze, and verify all raw data, reducing the data processing burden on both exchange and regulatory equipment.
[0079] In summary, the blockchain account verification method provided in this application extends the private key of the blockchain account using privacy information to obtain an extended private key. Then, it generates a first account fingerprint using the privacy information, the exchange's verification value, and the extended public key. The first account fingerprint is appended to the transaction data to obtain the transaction content. Finally, the extended private key is used to sign the transaction content. The monitoring device only needs to obtain the transaction record, privacy information, and the verification value provided by the exchange to verify whether the second account fingerprint generated based on the privacy information, verification value, and transaction record is the same as the first account fingerprint, thereby determining whether the user is the holder of the blockchain account. During the blockchain account verification process, the monitoring device does not need to obtain the blockchain account's private key, thus preventing the leakage of user assets. Furthermore, the exchange only needs to provide the verification value, and the monitoring device can independently verify the blockchain account through algorithms, improving the efficiency of the interaction.
[0080] User devices can proactively send identity identifiers, user identifiers, and transaction records to regulatory devices, enabling self-providence and facilitating the verification of blockchain accounts by regulatory devices.
[0081] Please refer to Figure 3 The diagram illustrates a structural block diagram of a blockchain account verification device according to an embodiment of this application. The blockchain account verification device may include:
[0082] The acquisition module 310 is used to acquire the user's privacy information and transaction records, and to acquire the verification value of the exchange. The transaction records are obtained by signing the transaction content using the user's extended private key. The extended private key is obtained by extending the private key of the blockchain account using the privacy information.
[0083] The decryption module 320 is used to decrypt the signature of the transaction record using the extended public key corresponding to the extended private key, and obtain the first account fingerprint in the transaction content. The first account fingerprint is generated in advance based on the user's privacy information, the transaction's verification value and the extended public key.
[0084] The generation module 330 is also used to generate a second account fingerprint based on the obtained privacy information, verification value and extended public key corresponding to the transaction record;
[0085] The determination module 340 is used to determine that the user is the holder of the blockchain account if the fingerprint of the first account is the same as the fingerprint of the second account.
[0086] In an optional embodiment, the acquisition module 310 is further configured to:
[0087] Obtain the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records;
[0088] The privacy information is obtained by hashing the combination of identity identifier and user identifier.
[0089] In an optional embodiment, the acquisition module 310 is further configured to:
[0090] Receive a verification request sent by a user equipment, which includes an identity identifier, a user identifier, and a transaction record;
[0091] Read the identity identifier, user identifier, and transaction record from the verification request.
[0092] In an optional embodiment, the acquisition module 310 is further configured to:
[0093] Obtain the transaction records of the blockchain accounts that need to be monitored, and obtain the user's identity identifier based on the transaction records;
[0094] Send a first acquisition request carrying an identity identifier to the exchange equipment, the first acquisition request being used to instruct the exchange equipment to send the user identifier corresponding to the identity identifier to the regulatory equipment;
[0095] Receive user identifier.
[0096] In an optional embodiment, when the verification value is updated periodically, the acquisition module 310 is further configured to:
[0097] Get the timestamp of the transaction record;
[0098] Send a second retrieval request carrying a timestamp to the exchange device. The second retrieval request is used to instruct the exchange device to retrieve the verification value corresponding to the timestamp from a preset first mapping table and send the verification value to the regulatory device. The first mapping table stores the correspondence between timestamps and verification values.
[0099] Receive verification value.
[0100] In an optional embodiment, when different regulatory devices correspond to different verification values, the acquisition module 310 is further configured to:
[0101] Obtain its own device identifier;
[0102] A third acquisition request carrying a device identifier is sent to the exchange device. The third acquisition request is used to instruct the exchange device to obtain the verification value corresponding to the device identifier from a preset second mapping table and send the verification value to the regulatory device. The second mapping table stores the correspondence between device identifiers and verification values.
[0103] Receive verification value.
[0104] In an optional embodiment, the transaction content is obtained by appending the first account fingerprint to the transaction data.
[0105] In summary, the blockchain account verification device provided in this application extends the private key of the blockchain account using privacy information to obtain an extended private key. Then, it generates a first account fingerprint using the privacy information, the exchange's verification value, and the extended public key. The first account fingerprint is appended to the transaction data to obtain the transaction content. Finally, the extended private key is used to sign the transaction content. The monitoring device only needs to obtain the transaction record, privacy information, and the verification value provided by the exchange to verify whether the second account fingerprint generated based on the privacy information, verification value, and transaction record is the same as the first account fingerprint, thereby determining whether the user is the holder of the blockchain account. During the blockchain account verification process, the monitoring device does not need to obtain the blockchain account's private key, thus preventing the leakage of user assets. Furthermore, the exchange only needs to provide the verification value, and the monitoring device can independently verify the blockchain account through algorithms, improving the efficiency of the interaction.
[0106] User devices can proactively send identity identifiers, user identifiers, and transaction records to regulatory devices, enabling self-providence and facilitating the verification of blockchain accounts by regulatory devices.
[0107] One embodiment of this application provides a computer-readable storage medium storing at least one instruction, which is loaded and executed by a processor to implement the blockchain account verification method described above.
[0108] One embodiment of this application provides a computer device including a processor and a memory, wherein the memory stores at least one instruction, which is loaded and executed by the processor to implement the blockchain account verification method described above.
[0109] It should be noted that the blockchain account verification device provided in the above embodiments is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the blockchain account verification device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the blockchain account verification device and the blockchain account verification method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process is detailed in the method embodiments, which will not be repeated here.
[0110] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.
[0111] The above description is not intended to limit the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application should be included within the protection scope of the embodiments of this application.
Claims
1. A method for verifying a blockchain account, characterized in that, The method includes: The monitoring device obtains the user's privacy information and transaction records, and obtains the verification value of the exchange. The transaction records are obtained by signing the transaction content using the user's extended private key. The extended private key is obtained by extending the private key of the blockchain account using the privacy information. The monitoring device uses the extended public key corresponding to the extended private key to decrypt the signature of the transaction record and obtain the first account fingerprint in the transaction content. The first account fingerprint is generated in advance based on the user's privacy information, the transaction's verification value and the extended public key. The monitoring device generates a second account fingerprint based on the obtained privacy information, the verification value, and the extended public key corresponding to the transaction record; If the fingerprint of the first account is the same as the fingerprint of the second account, then the monitoring device determines that the user is the holder of the blockchain account; The monitoring device obtains the user's privacy information and transaction records, including: the monitoring device obtains the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records; the monitoring device performs a hash calculation on the combination of the identity identifier and the user identifier to obtain the privacy information; When the verification value is updated periodically, obtaining the verification value from the exchange includes: the regulatory device obtaining the timestamp of the transaction record; the regulatory device sending a second acquisition request carrying the timestamp to the exchange device, the second acquisition request being used to instruct the exchange device to obtain the verification value corresponding to the timestamp from a preset first mapping table, and sending the verification value to the regulatory device, the first mapping table storing the correspondence between timestamps and verification values; and the regulatory device receiving the verification value.
2. The blockchain account verification method according to claim 1, characterized in that, The method further includes: the monitoring device receiving a verification request sent by the user device, the verification request including the identity identifier, the user identifier, and the transaction record; The monitoring device obtains the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records, including: the monitoring device reads the identity identifier, the user identifier, and the transaction records from the verification request.
3. The blockchain account verification method according to claim 1, characterized in that, The monitoring device acquires the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records, including: The monitoring device acquires the transaction records of the blockchain account to be monitored, and obtains the user's identity identifier based on the transaction records; The regulatory device sends a first acquisition request carrying the identity identifier to the exchange device. The first acquisition request is used to instruct the exchange device to send the user identifier corresponding to the identity identifier to the regulatory device. The monitoring device receives the user identifier.
4. The blockchain account verification method according to claim 1, characterized in that, When different monitoring devices correspond to different verification values, the method further includes: The monitoring equipment obtains its own device identifier; The regulatory device sends a third acquisition request carrying the device identifier to the exchange device. The third acquisition request is used to instruct the exchange device to obtain the verification value corresponding to the device identifier from a preset second mapping table and send the verification value to the regulatory device. The second mapping table stores the correspondence between device identifiers and verification values. The monitoring device receives the verification value.
5. The method for verifying a blockchain account according to any one of claims 1 to 4, characterized in that, The transaction content is obtained by appending the fingerprint of the first account to the transaction data.
6. A blockchain account verification device, characterized in that, The device includes: The acquisition module is used to acquire the user's privacy information and transaction records, and to acquire the verification value of the exchange. The transaction records are obtained by signing the transaction content using the user's extended private key. The extended private key is obtained by extending the private key of the blockchain account using the privacy information. The decryption module is used to decrypt the signature of the transaction record using the extended public key corresponding to the extended private key, and obtain the first account fingerprint in the transaction content. The first account fingerprint is generated in advance based on the user's privacy information, the verification value of the transaction and the extended public key. The generation module is used to generate a second account fingerprint based on the obtained privacy information, the verification value, and the extended public key corresponding to the transaction record; The determination module is used to determine that the user is the holder of the blockchain account if the first account fingerprint is the same as the second account fingerprint. The acquisition module is further configured to: acquire the user's identity identifier, the user identifier assigned to the user by the exchange, and the user's transaction records; perform a hash calculation on the combination of the identity identifier and the user identifier to obtain the privacy information; When the verification value is updated periodically, the acquisition module is further configured to: acquire the timestamp of the transaction record; send a second acquisition request carrying the timestamp to the exchange device, the second acquisition request being used to instruct the exchange device to acquire and send the verification value corresponding to the timestamp from a preset first mapping table, the first mapping table storing the correspondence between timestamps and verification values; and receive the verification value.
7. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, which is loaded and executed by a processor to implement the blockchain account verification method as described in any one of claims 1 to 5.
8. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one instruction that is loaded and executed by the processor to implement the blockchain account verification method as described in any one of claims 1 to 5.