Account authentication method, digital resource exchange method, device, equipment and medium

Abstract

The present application provides an account authentication method, a digital resource exchange method, an apparatus, a device and a storage medium, which belong to the field of blockchain technology. The method includes: based on the real-name authentication information of the first user account logged in by the target application, performing real-name authentication and face verification on the first user account; in response to the first user account passing the real-name authentication and the face verification, obtaining the target blockchain identifier; establishing a binding relationship between the first user account and the target blockchain identifier. The above technical solution obtains the target blockchain identifier after the first user account passes the real-name authentication and face verification, so that the target blockchain identifier can represent the second user account in the blockchain system, and finally binds the first user account and the target blockchain identifier, so that the first user account can be authenticated securely.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to an account authentication method, a digital resource exchange method, a device, a equipment and a medium. Background Art

[0002] With the development of Internet technology, a large amount of digital content has been generated, such as articles, audio, images, and videos. NFT (Non-Fungible Token) is a technical means of marking the ownership of non-fungible digital assets based on blockchain technology. It can transform digital content into digital assets, allowing the holder to freely dispose of his NFT assets. When a user account obtains digital assets, the identity information of the user account needs to be authenticated and reviewed. Therefore, how to ensure the security and reliability of the authentication process is a problem that needs to be solved.

[0003] Currently, user accounts are usually authenticated by graphic verification, mobile phone text message verification, etc. However, due to the risk of misappropriation of information for authentication, the security of the authentication process is relatively low. Summary of the invention

[0004] The embodiment of the present application provides an account authentication method, a digital resource exchange method, an apparatus, a device and a medium, which can securely complete the authentication of the first user account by binding the first user account and the target blockchain identifier. The technical solution is as follows:

[0005] In one aspect, an account authentication method is provided, the method comprising:

[0006] Based on the real-name authentication information of the first user account logged in by the target application, perform real-name authentication and face verification on the first user account;

[0007] In response to the first user account passing the real-name authentication and the face verification, obtaining a target blockchain identifier, where the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system;

[0008] A binding relationship between the first user account and the target blockchain identifier is established.

[0009] In some embodiments, the public-private key pair of the second user account is the first public-private key pair of the first user account; and the method further includes:

[0010] Sending a key generation request for the first user account to the blockchain system, and receiving the first public-private key pair returned by the blockchain system;

[0011] Sending a key encryption request to a key management server, the key encryption request carrying a master key of an application background server, the first user account, and the first public-private key pair, the application background server being used to provide background services for the target application;

[0012] The first encrypted string returned by the key management server is stored in the database.

[0013] In some embodiments, the method further comprises:

[0014] Acquire the first encrypted string from the database;

[0015] Sending a key decryption request to the key management server, wherein the key decryption request carries the master key and the first encrypted string;

[0016] Receive the first public-private key pair returned by the key management server.

[0017] In some embodiments, the public-private key pair of the second user account is a second public-private key pair of the first user account; and the method further includes:

[0018] Sending a key generation request for the first user account to the blockchain system, and receiving the second public-private key pair returned by the blockchain system;

[0019] Encrypting the second public-private key pair based on a data key of an application background server to obtain a second encrypted string, wherein the application background server is used to provide background services for the target application;

[0020] The ciphertext of the first user account, the second encrypted string and the data key is stored in a database.

[0021] In some embodiments, the method further comprises:

[0022] Acquire the second encrypted string from the database;

[0023] The second encrypted string is decrypted based on the data key of the application background server to obtain the second public-private key pair.

[0024] In some embodiments, the method further comprises:

[0025] Send a key creation request to the key management server to obtain the master key of the application background server;

[0026] Based on the master key, obtaining the data key and the ciphertext of the data key from the key management server;

[0027] The data key is cached, and the ciphertext of the data key is stored in the database.

[0028] In some embodiments, the public-private key pair of the second user account is a third public-private key pair of the first user account; and the method further includes:

[0029] Sending a key generation request for the first user account to the blockchain system, and receiving the third public-private key pair returned by the blockchain system;

[0030] Encrypting the third public-private key pair based on the key in the configuration file to obtain a third encrypted string;

[0031] The first user account and the third encrypted string are stored in a database.

[0032] In some embodiments, the method further comprises:

[0033] Acquire the third encrypted string from the database;

[0034] The third encrypted string is decrypted based on the key in the configuration file to obtain the third public-private key pair.

[0035] In some embodiments, the public-private key pair of the second user account is a fourth public-private key pair of the first user account; and the method further includes:

[0036] Based on the first user account and the timestamp, generate a data key and a ciphertext of the data key for the first user account;

[0037] Sending a key generation request for the first user account to the blockchain system, and receiving the fourth public-private key pair returned by the blockchain system;

[0038] Encrypting the fourth public-private key pair based on the data key to obtain a fourth encrypted string;

[0039] The ciphertext of the first user account, the fourth encrypted string and the data key is stored in a database.

[0040] In some embodiments, the method further comprises:

[0041] Based on the first user account, obtaining the ciphertext of the fourth encrypted string and the data key from the database;

[0042] Based on the ciphertext of the data key, obtaining the data key;

[0043] The fourth encrypted string is decrypted based on the data key to obtain the fourth public-private key pair.

[0044] In another aspect, a method for exchanging digital resources is provided, the method comprising:

[0045] Displaying a resource exchange page of the target application, wherein the resource exchange page displays at least one digital resource provided by the blockchain system;

[0046] In response to an exchange operation for any digital resource, obtaining a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system;

[0047] Sending a redemption request to the server, wherein the redemption request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier.

[0048] In some embodiments, the blockchain system stores a resource series identifier to which the digital resource identifier of the digital resource belongs;

[0049] The digital resource transfer request is used to instruct the blockchain system to bind the resource series identifier and the donation blockchain identifier.

[0050] On the other hand, a digital resource exchange system is provided, the digital resource exchange system comprising a terminal and a server;

[0051] The terminal is used to display a resource exchange page of the target application, and the resource exchange page displays at least one digital resource provided by the blockchain system;

[0052] The server is used to store the binding relationship between the first user account logged in by the target application and the target blockchain identifier;

[0053] The terminal is further configured to, in response to an exchange operation for any digital resource, obtain a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system;

[0054] The terminal is further used to send a redemption request to the server, wherein the redemption request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier;

[0055] The server is also used to establish a binding relationship between the target blockchain identifier and the target resource identifier.

[0056] On the other hand, an account authentication device is provided, the device comprising:

[0057] An authentication module, configured to perform real-name authentication and face verification on a first user account logged in by a target application based on the real-name authentication information of the first user account;

[0058] A first acquisition module is configured to acquire a target blockchain identifier in response to the first user account passing the real-name authentication and the face verification, where the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system;

[0059] A relationship establishment module is used to establish a binding relationship between the first user account and the target blockchain identifier.

[0060] In some embodiments, the authentication module comprises:

[0061] A determination unit, configured to determine whether the first user account has been bound to a blockchain identifier based on the real-name authentication information;

[0062] An authentication unit is used to perform the real-name authentication and the face verification on the first user account based on the real-name authentication information when the first user account is not bound to a blockchain identifier.

[0063] In some embodiments, the first acquisition module is further used to obtain the target blockchain identifier to which the first user account is bound when the first user account is bound to a blockchain identifier; return the target blockchain identifier to the target application, and cancel the real-name authentication and the face verification for the first user account.

[0064] In some embodiments, the authentication module comprises:

[0065] A verification unit, configured to verify the identity card number in the real-name authentication information based on a blockchain account management service, and obtain a verification result, wherein the verification result is used to indicate whether the identity card number has been registered in the blockchain system;

[0066] An authentication unit, configured to perform the real-name authentication and the face verification on the first user account based on the real-name authentication when the verification result indicates that the identity card number has been registered.

[0067] In some embodiments, the authentication unit is further configured to perform the real-name authentication and the face verification on the first user account based on the real-name authentication if the verification result indicates that the ID card number is not registered;

[0068] The first acquisition module is used to send a registration request to the blockchain system in response to the first user account passing the real-name authentication and the face verification, wherein the registration request is used to instruct the blockchain system to register a blockchain account based on the real-name authentication information; and obtain the target blockchain identifier and the second user account returned by the blockchain system.

[0069] In some embodiments, the apparatus further comprises:

[0070] A request sending module, configured to send an association request to a blockchain system in response to an exchange request for a target digital resource, wherein the exchange request carries the target blockchain identifier and the target resource identifier of the target digital resource, and the association request is used to instruct the blockchain system to associate the target blockchain identifier with the target resource identifier;

[0071] An information return module is used to return binding information to the target application, wherein the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

[0072] In some embodiments, the apparatus further comprises:

[0073] The signature image binding module is used to obtain a signature binding request for a target digital resource, wherein the signature binding request carries a target signature image of the first user account; and bind the target signature image to a target resource identifier of the target digital resource.

[0074] In some embodiments, the apparatus further comprises:

[0075] A signature image review module is used to receive a signature review request from the first user account, and review the signature image carried in the signature review request; in response to the signature image passing the review, store the review result of the signature image, and the review result is used to indicate whether the signature image has passed the review; and return the review result to the target application.

[0076] In some embodiments, the public-private key pair of the second user account is the first public-private key pair of the first user account; and the apparatus further comprises:

[0077] A first request module, configured to send a key generation request for the first user account to the blockchain system, and receive the first public-private key pair returned by the blockchain system;

[0078] A first encryption module is used to send a key encryption request to a key management server, wherein the key encryption request carries a master key of an application background server, the first user account, and the first public-private key pair, and the application background server is used to provide background services for the target application;

[0079] The first storage module is used to store the first encrypted string returned by the key management server in a database.

[0080] In some embodiments, the apparatus further comprises:

[0081] A second acquisition module, used to acquire the first encrypted string from the database;

[0082] A first decryption module, configured to send a key decryption request to the key management server, wherein the key decryption request carries the master key and the first encrypted string;

[0083] The first receiving module is used to receive the first public-private key pair returned by the key management server.

[0084] In some embodiments, the public-private key pair of the second user account is a second public-private key pair of the first user account; and the apparatus further comprises:

[0085] A second request module, configured to send a key generation request for the first user account to the blockchain system, and receive the second public-private key pair returned by the blockchain system;

[0086] A second encryption module, used to encrypt the second public-private key pair based on a data key of an application background server to obtain a second encrypted string, wherein the application background server is used to provide background services for the target application;

[0087] The second storage module is used to store the first user account, the second encrypted string and the ciphertext of the data key corresponding to the data key into a database.

[0088] In some embodiments, the apparatus further comprises:

[0089] A third acquisition module, used to acquire the second encrypted string from the database;

[0090] The second decryption module is used to decrypt the second encrypted string based on the data key of the application background server to obtain the second public-private key pair.

[0091] In some embodiments, the apparatus further comprises:

[0092] The second request module is further used to send a key creation request to the key management server to obtain the master key of the application background server;

[0093] A third acquisition module, configured to acquire the data key and the ciphertext of the data key from the key management server based on the master key;

[0094] The second storage module is further used to cache the data key and store the ciphertext of the data key in the database.

[0095] In some embodiments, the public-private key pair of the second user account is a third public-private key pair of the first user account; and the apparatus further comprises:

[0096] A third request module, configured to send a key generation request for the first user account to the blockchain system, and receive the third public-private key pair returned by the blockchain system;

[0097] A third encryption module, used to encrypt the third public-private key pair based on the key in the configuration file to obtain a third encrypted string;

[0098] The third storage module is used to store the first user account and the third encrypted string in a database.

[0099] In some embodiments, the apparatus further comprises:

[0100] A fourth acquisition module, used to acquire the third encrypted string from the database;

[0101] The third decryption module is used to decrypt the third encrypted string based on the key in the configuration file to obtain the third public-private key pair.

[0102] In some embodiments, the public-private key pair of the second user account is a fourth public-private key pair of the first user account; and the apparatus further comprises:

[0103] A generating module, configured to generate a data key and a ciphertext of the data key of the first user account based on the first user account and the timestamp;

[0104] a fourth request module, configured to send a key generation request for the first user account to the blockchain system, and receive the fourth public-private key pair returned by the blockchain system;

[0105] a fourth encryption module, used to encrypt the fourth public-private key pair based on the data key to obtain a fourth encrypted string;

[0106] The fourth storage module is used to store the ciphertext of the first user account, the fourth encryption string and the data key in a database.

[0107] In some embodiments, the apparatus further comprises:

[0108] a fifth acquisition module, configured to acquire, from the database based on the first user account, the ciphertext of the fourth encrypted string and the data key;

[0109] The fifth acquisition module is further used to acquire the data key based on the ciphertext of the data key;

[0110] The fourth decryption module is used to decrypt the fourth encrypted string based on the data key to obtain the fourth public-private key pair.

[0111] In another aspect, a digital resource exchange device is provided, the device comprising:

[0112] A display module, used to display a resource exchange page of the target application, wherein the resource exchange page displays at least one digital resource provided by the blockchain system;

[0113] an acquisition module, configured to, in response to an exchange operation on any digital resource, acquire a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system;

[0114] A request sending module is used to send an exchange request to a server, wherein the exchange request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier.

[0115] In some embodiments, the acquisition module includes:

[0116] an acquisition unit, configured to, in response to an exchange operation on any digital resource, acquire a target resource identifier of the digital resource, and send a binding information query request to a server, wherein the binding information query request is used to request a query of a blockchain identifier bound to the first user account;

[0117] an authentication unit, configured to, in response to the first user account not being bound to a blockchain identifier, request the server to perform real-name authentication and face verification on the first user account logged into the target application based on the real-name authentication information of the first user account;

[0118] The acquisition unit is further used to obtain the target blockchain identifier returned by the server in response to the first user account passing the real-name authentication and the face verification.

[0119] In some embodiments, the authentication unit is used to send a blockchain account query request to the server based on the real-name authentication information of the first user account in response to the first user account not being bound to a blockchain identifier, and the blockchain account query request is used to query whether the blockchain system has a blockchain account corresponding to the real-name authentication information; in response to the absence of a blockchain account corresponding to the real-name authentication information, request the server to perform real-name authentication and face verification on the first user account for logging in to the target application.

[0120] In some embodiments, the display module is further used to display a resource display page, wherein the resource display page is used to display at least one digital resource that has been redeemed by the first user account;

[0121] The display module is further used to display a signature selection page in response to a signature operation on any digital resource in the resource display page, wherein the signature selection page is used to select a signature image;

[0122] The request sending module is further used to send a signature binding request to the server in response to a selection operation on any signature image, wherein the signature binding request is used to instruct the server to bind the selected target signature image with the digital resource.

[0123] In some embodiments, the apparatus further comprises:

[0124] The display module is further used to display a signature creation page, and the signature creation page is used to create a signature image;

[0125] The request sending module is further used to send a signature review request to the server in response to a signature image creation operation based on the signature creation page, wherein the signature review request carries the signature image created by the signature image creation operation;

[0126] The receiving module is used to receive the review result returned by the server based on the signature review request, and the review result is used to indicate whether the signature image has passed the review.

[0127] In some embodiments, the apparatus further comprises:

[0128] A resource donation module, configured to display a resource donation page in response to a donation operation on any digital resource in the resource display page;

[0129] The request sending module is also used to send a digital resource transfer request to the blockchain system in response to the donation blockchain identifier input based on the resource donation page, and the digital resource transfer request is used to instruct the blockchain system to bind the digital resource identifier of the digital resource with the donation blockchain identifier.

[0130] In some embodiments, the blockchain system stores a resource series identifier to which the digital resource identifier of the digital resource belongs; the digital resource transfer request is used to instruct the blockchain system to bind the resource series identifier with the donation blockchain identifier.

[0131] On the other hand, a computer device is provided, which includes a processor and a memory, wherein the memory is used to store at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the account authentication method in the embodiment of the present application.

[0132] On the other hand, a computer device is provided, which includes a processor and a memory, wherein the memory is used to store at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the digital resource redemption method in the embodiment of the present application.

[0133] On the other hand, a computer-readable storage medium is provided, in which at least one computer program is stored. The at least one computer program is loaded and executed by a processor to implement an account authentication method as in an embodiment of the present application.

[0134] On the other hand, a computer-readable storage medium is provided, in which at least one computer program is stored. The at least one computer program is loaded and executed by a processor to implement a method for exchanging digital resources as in an embodiment of the present application.

[0135] On the other hand, a computer program is provided. When the computer program is executed by a processor, the account authentication method provided in various optional implementations of the above aspects is implemented.

[0136] On the other hand, a computer program is provided, which, when executed by a processor, implements the digital resource exchange method provided in various optional implementations of the above-mentioned various aspects.

[0137] The embodiment of the present application provides a solution for account authentication, which can perform real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account in the target application, and then after passing the above authentication, obtain the public-private key pair of the second user account based on the blockchain system, encrypt the second user account to obtain the target blockchain identifier, so that the target blockchain identifier can represent the second user account, and finally, by binding the first user account and the target blockchain identifier, the first user account can be securely authenticated. BRIEF DESCRIPTION OF THE DRAWINGS

[0138] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0139] Figure 1 is a schematic diagram of a digital resource exchange system provided according to an embodiment of the present application;

[0140] Figure 2 is a flow chart of an account authentication method provided according to an embodiment of the present application;

[0141] Figure 3 is a flow chart of a digital resource exchange method provided according to an embodiment of the present application;

[0142] Figure 4 It is an interactive flow chart of a digital resource exchange method provided according to an embodiment of the present application;

[0143] Figure 5 is a schematic diagram of a resource exchange page provided according to an embodiment of the present application;

[0144] Figure 6 is a schematic diagram of a real-name authentication page provided according to an embodiment of the present application;

[0145] Figure 7 is a schematic diagram of another real-name authentication page provided according to an embodiment of the present application;

[0146] Figure 8 is a schematic diagram of an account authentication process provided according to an embodiment of the present application;

[0147] Fig. 9 is a schematic diagram of another account authentication process provided according to an embodiment of the present application;

[0148] Fig.10 is a schematic diagram of a face verification process provided according to an embodiment of the present application;

[0149] Fig.11 It is a schematic diagram of a blockchain identification binding process provided according to an embodiment of the present application;

[0150] Fig.12 is a schematic diagram of another face recognition process provided according to an embodiment of the present application;

[0151] Fig.13 is a schematic diagram of a target blockchain identifier provided according to an embodiment of the present application;

[0152] Fig.14 is a schematic diagram of establishing a binding relationship according to an embodiment of the present application;

[0153] Fig.15 It is a schematic diagram of a process for encrypting a public-private key pair according to an embodiment of the present application;

[0154] Fig.16It is a schematic diagram of another process of encrypting a public-private key pair according to an embodiment of the present application;

[0155] Fig.17 It is a schematic diagram of another process of encrypting a public-private key pair according to an embodiment of the present application;

[0156] Fig.18 It is a schematic diagram of another process of encrypting a public-private key pair according to an embodiment of the present application;

[0157] Fig.19 is a schematic diagram of a signature creation page provided according to an embodiment of the present application;

[0158] Fig. 20 is a schematic diagram of a signature image review process provided according to an embodiment of the present application;

[0159] Fig.21 is a relationship diagram provided according to an embodiment of the present application;

[0160] Fig. 22 It is a mapping relationship diagram provided according to an embodiment of the present application;

[0161] Fig.23 is a schematic diagram of transferring digital resources according to an embodiment of the present application;

[0162] Fig.24 It is a schematic diagram of a process of querying a blockchain identifier according to an embodiment of the present application;

[0163] Fig.25 It is a schematic diagram of a solution architecture provided according to an embodiment of the present application;

[0164] Fig.26 is a block diagram of an account authentication device provided according to an embodiment of the present application;

[0165] Fig. 27 is a block diagram of another account authentication device provided according to an embodiment of the present application;

[0166] Fig.28 is a block diagram of a digital resource exchange device provided according to an embodiment of the present application;

[0167] Fig.29 is a block diagram of another digital resource exchange device provided according to an embodiment of the present application;

[0168] Fig.30 is a structural block diagram of a terminal provided according to an embodiment of the present application;

[0169] Fig.31 It is a structural diagram of a server provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0170] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0171] In this application, the terms "first", "second", etc. are used to distinguish identical or similar items with basically the same effects and functions. It should be understood that there is no logical or temporal dependency between "first", "second", and "nth", nor is there any limitation on quantity and execution order.

[0172] In the present application, the term "at least one" means one or more, and the term "plurality" means two or more.

[0173] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the real-name authentication information, user account, blockchain identifier and digital resource identifier involved in this application are all obtained with full authorization.

[0174] The following is an explanation of the terms used in this application.

[0175] Blockchain is a technology system jointly maintained by multiple parties, using cryptography to ensure transmission and access security, and capable of achieving consistent data storage, tamper-proof, and non-repudiation. Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, the platform product service layer, and the application service layer.

[0176] The underlying blockchain platform can include processing modules such as user management, basic services, smart contracts, and operation management. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining the generation of public and private key pairs (account management), key management, and the maintenance of the corresponding relationship between the user's real identity and the blockchain address (authority management), etc., and, under authorization, supervises and audits the transactions of certain real identities and provides risk control rule configuration (risk control audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests, and records valid requests to storage after consensus is reached. For a new business request, the basic service first adapts the interface for parsing and authentication (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus management) The smart contract module is responsible for the registration and issuance of contracts, as well as contract triggering and contract execution. Developers can define the contract logic in a programming language and publish it to the blockchain (contract registration). According to the logic of the contract terms, the key or other events are called to trigger the execution and complete the contract logic. It also provides the function of contract upgrade and cancellation. The operation management module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation and real-time status visualization output of the product during the product release process, such as alarm, network management, and node equipment health status management.

[0177] The platform product service layer provides the basic capabilities and implementation framework of typical applications. Developers can superimpose business features based on these basic capabilities to complete the blockchain implementation of business logic. The application service layer provides application services based on blockchain solutions for business participants to use.

[0178] NFT (Non-Fungible Token) represents unique and indivisible digital resources on the blockchain.

[0179] NFT chain (Non-Fungible Token blockchain) is a blockchain system that supports the issuance, trading, circulation, and management of NFT meta-commodities.

[0180] NFT meta-artifact is a non-homogeneous digital resource with a unique identifier that is generated and issued based on consortium blockchain technology, has passed content compliance review, and can only be owned by blockchain users who have passed real-name authentication.

[0181] NFT metadata is information used to describe the properties of NFT meta-products. NFT metadata includes the NFT meta-product’s logo, uniform resource identifier, author name, summary, signature, etc.

[0182] Digital resource transfer refers to the atomic ledger data status change on the blockchain and the record of its process and results.

[0183] Digital resources can also be called digital assets, which can be issued, circulated, and stored on the blockchain and used to complete the rights and interests of resource settlement business.

[0184] SDK (Software Development Kit) is a collection of development tools used by software engineers to create application software for specific software packages, software frameworks, hardware platforms, operating systems, etc. Generally speaking, SDK is the SDK used to develop application programs. It can simply provide some files of application program interfaces for a certain programming language, but it may also include complex hardware that can communicate with some embedded systems. General tools include utilities for debugging and other purposes. SDK also often includes sample code, supporting technical notes or other supporting documents to clarify doubts for basic reference materials.

[0185] AES (Advanced Encryption Standard) is a block encryption standard.

[0186] A 302 redirect is also called a temporary move, or a temporary redirect. It is an instruction to a web browser to display a different network address than the one the browser was asked to display. It is used when a web page undergoes a short-term network address change. A temporary redirect is a server-side redirect that can be correctly handled by search engine spiders.

[0187] The following explains the implementation environment of the embodiments of the present application.

[0188] The solution provided in the embodiment of the present application can be applied to the digital resource exchange system. Figure 1 is a schematic diagram of a digital resource exchange system provided according to an embodiment of the present application. Figure 1 , the digital resource system includes a terminal 101 and a server 102.

[0189] The terminal 101 and the server 102 can be connected directly or indirectly via wired or wireless communication, which is not limited in this application.

[0190] In some embodiments, the terminal 101 is a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, an intelligent voice interaction device, a smart home appliance, a vehicle-mounted terminal, etc., but is not limited thereto. The terminal 101 is installed and runs an application that supports the exchange of digital resources. The application may be a social application, an information flow application, a browser application, a video application, or an audio application, etc. Those skilled in the art may know that the number of the above-mentioned terminals 101 may be more or less. For example, the above-mentioned terminal 101 may be only one, or the above-mentioned terminal 101 may be dozens or hundreds, or more. The embodiment of the present application does not limit the number of terminals and device types.

[0191] In some embodiments, the server 102 is an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Server 102 includes an application background server, an authentication server, and a blockchain system server. Among them, the application background server is used to provide a background server for the application installed on the terminal 101, the authentication server is used to provide real-name authentication and face verification services, and the blockchain system server is used to provide digital resource exchange services based on blockchain. In some embodiments, the server 102 undertakes the main computing work, and the terminal 101 undertakes the secondary computing work; or, the server 102 undertakes the secondary computing work, and the terminal 101 undertakes the main computing work; or, the server 102 and the terminal 101 use a distributed computing architecture for collaborative computing.

[0192] In an embodiment of the present application, the terminal 101 is used to display a resource exchange page of the target application, and the resource exchange page displays at least one digital resource provided by the blockchain system. The server 102 is used to store the binding relationship between the first user account logged in by the target application and the target blockchain identifier. The terminal 101 is also used to obtain the target resource identifier of the digital resource and the target blockchain identifier bound to the first user account logged in by the target application in response to the exchange operation of any digital resource, and the target blockchain identifier is based on the public-private key pair of the second user account in the blockchain system, and the second user account is encrypted. The terminal 101 is also used to send an exchange request to the server 102, and the exchange request is used to instruct the server 102 to establish a binding relationship between the target blockchain identifier and the target resource identifier. The server 102 is also used to establish a binding relationship between the target blockchain identifier and the target resource identifier.

[0193] The account authentication method provided in the embodiment of the present application can be executed by a computer device, which can be configured as a terminal or a server. When the computer device is configured as a terminal, the terminal is used as the execution subject to implement the technical solution provided in the embodiment of the present application; when the computer device is configured as a server, the server is used as the execution subject to implement the technical solution provided in the embodiment of the present application; the technical solution provided in the present application can also be implemented through the interaction between the terminal and the server, which is not limited in the embodiment of the present application. Figure 2 is a flowchart of an account authentication method provided according to an embodiment of the present application, such as Figure 2 As shown, in the embodiment of the present application, the example of execution by the server is used for explanation. The account authentication method includes the following steps:

[0194] 201. The server performs real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account logged in by the target application.

[0195] In the embodiment of the present application, the server is Figure 1 The target application is an application installed and running in the terminal 101, and the target application is a social application, an information flow application, a browser application, a video application, or an audio application. The first user account is a user account logged in by the target application in the terminal 101. The user can send the real-name authentication information of the first user account to the server 102 through the target application, and the server can perform real-name authentication and face verification on the first user account based on the real-name authentication information.

[0196] 202. In response to the first user account passing the real-name authentication and the face verification, the server obtains a target blockchain identifier, where the target blockchain identifier is encrypted based on a public-private key pair of a second user account in the blockchain system and obtained by encrypting the second user account.

[0197] In an embodiment of the present application, when the first user account passes the real-name authentication and face verification, it means that there is no security risk for the first user account at present, and the server can obtain the target blockchain identifier from the blockchain system. The target blockchain identifier corresponds to the second user account in the blockchain system, and the first user account is a unique account obtained by a natural person through real-name registration in the blockchain system. The target blockchain identifier is a string of characters, which can also be called a blockchain address. The blockchain system can encrypt the second user account through the public and private key pair of the second user account to obtain the target blockchain identifier. Among them, the second user account has multiple sets of public and private key pairs, and different public and private key pairs correspond to different types of applications, that is, the public and private key pairs that generate the target blockchain identifier correspond to the target application. Among them, the blockchain system is used to store NFT resources.

[0198] 203. The server establishes a binding relationship between the first user account and the target blockchain identifier.

[0199] In the embodiment of the present application, since the target blockchain identifier is obtained based on the second user account, is unique and associated with the target application, after obtaining the target blockchain identifier, the server can bind the first user account and the target blockchain identifier and store the binding relationship between the first user account and the target blockchain identifier. Since the first user account can represent the identity of the user in the target application, that is, the first user account belongs to a certain user, the affiliation relationship between the target blockchain identifier and the user is established by binding the first user account and the target blockchain identifier.

[0200] The embodiment of the present application provides a solution for account authentication, which can perform real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account in the target application, and then after passing the above authentication, obtain the public-private key pair of the second user account based on the blockchain system, encrypt the second user account to obtain the target blockchain identifier, so that the target blockchain identifier can represent the second user account, and finally, by binding the first user account and the target blockchain identifier, the first user account can be securely authenticated.

[0201] The digital resource exchange method provided in the embodiment of the present application can be executed by a computer device, which can be configured as a terminal or a server. When the computer device is configured as a terminal, the terminal is used as the execution subject to implement the technical solution provided in the embodiment of the present application; when the computer device is configured as a server, the server is used as the execution subject to implement the technical solution provided in the embodiment of the present application; the technical solution provided in the present application can also be implemented through the interaction between the terminal and the server, which is not limited in the embodiment of the present application. Figure 3 is a flow chart of a digital resource exchange method provided according to an embodiment of the present application, such as Figure 3 As shown, in the embodiment of the present application, the method for exchanging digital resources is described by taking the execution by the terminal as an example. The method comprises the following steps:

[0202] 301. The terminal displays a resource exchange page of the target application, where the resource exchange page displays at least one digital resource provided by the blockchain system.

[0203] In the embodiment of the present application, the terminal is Figure 1The terminal 101 shown. A target application is installed and running in the terminal, and the target application is a social application, a video application, or an audio application, etc. The target application includes a resource exchange page, through which a user can exchange at least one digital resource provided by the blockchain system. The digital resource is a video resource, a music resource, or an image resource, etc., which is not limited in the embodiments of the present application. For example, the blockchain system is an NFT chain, and the digital resource is an NFT meta-item generated based on the NFT chain. The blockchain system includes NFT metadata.

[0204] 302. In response to an exchange operation for any digital resource, the terminal obtains a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is encrypted based on a public-private key pair of a second user account in the blockchain system.

[0205] In an embodiment of the present application, a user can trigger the exchange of any digital resource in the resource exchange page through an exchange operation. In response to the detected exchange operation, the terminal obtains the target resource identifier of the digital resource, and the target resource identifier is used to uniquely identify the digital resource in the blockchain system. Among them, the target resource identifier is included in the resource information of the digital resource, and the resource information includes the display image, profile information and target resource identifier of the digital resource. The terminal can obtain the target blockchain identifier bound to the first user account from the server. The server stores the binding relationship between the first user account and the target blockchain identifier. Among them, the source of the target blockchain identifier and the method of determining the binding relationship are shown in the above steps 202 and 203, which will not be repeated here.

[0206] 303. The terminal sends an exchange request to the server, where the exchange request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier.

[0207] In an embodiment of the present application, the terminal can send a redemption request carrying a target blockchain identifier and a target resource identifier to the server to request the server to bind the target blockchain identifier with the target resource identifier, thereby establishing a subordinate relationship in which the target resource identifier is subordinate to the target blockchain identifier. The redemption request can be sent after the resource transfer is completed or before the resource transfer is performed. Resource transfer refers to transferring other resources required for redeeming the above-mentioned digital resources from the account of the first user account.

[0208] An embodiment of the present application provides a method for exchanging digital resources. When exchanging digital resources on a resource exchange page based on a target application, a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in to the target application are obtained, and a server is requested to establish a binding relationship between the target blockchain identifier and the target resource identifier, so that the first user account can indirectly associate the digital resources in the blockchain system through the target blockchain identifier to realize the exchange of digital resources, thereby ensuring that the process of the first user account in obtaining digital assets is safe and reliable.

[0209] Above Figure 2 and Figure 3 The main processes of the digital resource exchange method and the account authentication method provided in the embodiment of the present application are shown as an example. The following is a further description of the above scheme provided in the embodiment of the present application based on the scenario of exchanging digital resources in the blockchain system. Figure 4 is an interactive flow chart of a digital resource exchange method provided according to an embodiment of the present application, such as Figure 4 As shown, in the embodiment of the present application, the interaction between the terminal and the server is taken as an example for explanation. The method comprises the following steps:

[0210] 401. The terminal displays a resource exchange page of the target application, where the resource exchange page displays at least one digital resource provided by the blockchain system.

[0211] In the embodiment of the present application, the terminal is Figure 1 The terminal 101 shown, the target application includes a resource exchange page, see step 201 for details, which will not be repeated here. The resource exchange page is used to display at least one digital resource provided by the blockchain system, and the at least one digital resource can be exchanged through other resources, such as points or virtual gold coins.

[0212] For example, the target application is a video playback application, and the digital resource is an electronic card. Figure 5 is a schematic diagram of a resource exchange page provided according to an embodiment of the present application. Figure 5 As shown, the resource exchange page is an exchange page for a certain electronic card, and the resource exchange page displays the resource information of the electronic card, and the resource information includes a display image: "XX Commemorative Card", the name of the electronic card "YY Video Playback Application XX Commemorative Card", the description information of the electronic card: "Card Details", the value of the electronic card: "ZZZ" and an exchange control. By clicking on the exchange control, the exchange operation of the digital resource can be triggered. It should be noted that the resource exchange page can also display display images of multiple digital resources. In response to the triggering operation of the display image of any digital resource, the resource exchange page displays the resource information of the triggered digital resource.

[0213] 402. In response to an exchange operation for any digital resource, the terminal obtains a target resource identifier of the digital resource and sends a binding information query request to the server, where the binding information query request is used to request a query for a blockchain identifier bound to the first user account.

[0214] In the embodiment of the present application, the first user account is the user account currently logged in by the target application. Since the digital resource is a resource in the blockchain system, the user can only redeem the digital resource if he has an account registered in the blockchain system. When the terminal detects an exchange operation for any digital exchange resource, it obtains the target resource identifier of the digital resource from the local, and then sends a binding information query request to the server to query whether the first user account currently logged in by the target application is bound to the blockchain identifier.

[0215] Among them, when the first user account has been bound to a blockchain identifier, the server stores the binding relationship between the first user account and the bound target blockchain identifier, the server executes step 403, and the terminal can obtain the target blockchain identifier returned by the server; when the first user account is not bound to a blockchain identifier, the server can return a no query response, and the terminal can execute step 403 to send the real-name authentication information of the first user account to the server to generate and bind the target blockchain identifier for the first user account.

[0216] 403. When the first user account has been bound to a blockchain identifier, the server returns the target blockchain identifier to the terminal and cancels the real-name authentication and face verification of the first user account.

[0217] In the embodiment of the present application, the server stores the binding relationship between the user account and the blockchain identifier. For any user account, the server can query the blockchain identifier bound to the user account based on the above binding relationship. Therefore, if the first user account has been bound to a blockchain identifier, the server can obtain the target blockchain identifier bound to the first user account based on the stored binding relationship, return the target blockchain identifier to the target application on the terminal, and then no longer perform the subsequent real-name authentication and face verification steps, which can save terminal and server resources and improve the efficiency of resource exchange.

[0218] 404. In response to the first user account not being bound to a blockchain identifier, the terminal requests the server to perform real-name authentication and face verification on the first user account logged into the target application based on the real-name authentication information of the first user account.

[0219] In an embodiment of the present application, when the terminal determines that the first user account is not bound to a blockchain identifier according to the response returned by the server, it can request the server to perform real-name authentication and face verification on the first user account. The terminal can send the real-name authentication information of the first user account to the server, so that the server can perform real-name authentication and face verification on the first user account based on the real-name authentication information. Among them, the real-name authentication information includes ID number, name, mobile phone number, and face verification video. The real-name authentication process is divided into two stages. The first stage is identity authentication, which is used to verify the ID number, name and mobile phone number; the second stage is face verification, which is used to perform face recognition and liveness verification based on the face verification video.

[0220] For example, taking the input of real-name authentication information based on the real-name authentication page displayed on the terminal as an example, Figure 6 Schematic diagram of a real-name authentication page provided according to an embodiment of the present application. Figure 6 The figure shows the process of the first stage of authentication. Figure 6 In (a), the Figure 6 (a) in the figure shows the avatar frame 601 set by the first user account in the target application, the first user account 602, the mobile phone number 603 bound to the first user account, the name input box 604, the ID number input box 605 and the verification control 606. Among them, the name input box 604 is used to enter the name, the ID number input box 605 is used to enter the ID number, and the verification control 606 is used to display after being triggered. Figure 6 (b) in . Figure 6 (b) is used for mobile phone number verification. Figure 6 (b) in the figure shows the current account information 607, the mobile phone number to be verified 608, the verification code input control 609, the verification code acquisition control 610, the confirmation control 611, the cancel control 612 and the change mobile phone number control 613. Among them, the verification code input control 609 is used to input the verification code, the verification code acquisition control 610 is used to send the verification code to the mobile phone number to be verified 608 after being triggered, the confirmation control 611 is used to send the real-name authentication information to the server after being triggered, the cancel control 612 is used to cancel the authentication process after being triggered, and the change mobile phone number control 613 is used to display the verification code after being triggered. Figure 6 (c) in . Figure 6 (c) is used to change the bound mobile phone number. Figure 6 (c) in FIG. 6 shows an avatar frame 601, a first user account 602, a mobile phone number 603 bound to the first user account, a binding change control 614, and a return control 615. The binding change control 614 is used to display a page for binding a new mobile phone number after being triggered. The page is the same as Figure 6The return control 615 is used to return after being triggered. Figure 6 It should be noted that if the first user account is not bound to a mobile phone number, then Figure 6 (a) in the example does not display the mobile phone number 603, but displays "mobile phone number is not bound". The verification control 606 is replaced with the verification binding control 606. The verification binding control 606 is used to display after being triggered. Figure 6 (d) in. Figure 6 (d) is used to bind a mobile phone number. Figure 6 (d) in the figure shows the current account information 607, the verification code input control 609, the verification code acquisition control 610, the confirmation control 611, the cancel control 612 and the number input control 616. The number input control 616 is used to input the mobile phone number to be bound. It should be noted that in the process of verifying the mobile phone number, human-machine verification can also be added, such as dragging a slider to complete the puzzle, inputting a graphic verification code, selecting a specific type of image, etc., to avoid non-human batch authentication.

[0221] For example, still taking the input of real-name authentication information based on the real-name authentication page displayed on the terminal as an example, Figure 7 A schematic diagram of another real-name authentication page provided according to an embodiment of the present application. Figure 7 The following figure shows the process of the second stage of authentication. Figure 7 In (a), the Figure 7 (a) in FIG. 1 shows an authorization control 701, which is used to start face verification after being triggered. Figure 7 (b) in . Figure 7 (b) in the figure shows a viewfinder 702, a countdown control 703 and a verification prompt message 704. Based on the viewfinder 702, a face verification video can be acquired.

[0222] It should be noted that, for the sake of convenience of description, the embodiment of the present application refers to the ID number, name, mobile phone number and face verification video as real-name authentication information, and the two-stage verification process is described in the same step. In actual application, the terminal can first interact with the server to perform the first stage of authentication. If the first stage fails to pass the authentication, a prompt message is displayed to prompt. After the first stage of authentication is completed, the second stage of authentication is performed.

[0223] 405. The server performs real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account logged in by the target application.

[0224] In an embodiment of the present application, the server is able to receive the real-name authentication information sent by the terminal, perform real-name authentication on the first user account based on information such as the ID card number, name, and mobile phone number in the real-name authentication information, and then perform face verification based on the face verification video in the real-name authentication information.

[0225] In some embodiments, when the server performs real-name authentication on the first user account, it can also confirm whether the ID number has been registered in the blockchain system based on the ID number in the real-name authentication information. The server can verify the ID number in the real-name authentication information based on the blockchain account management service to obtain a verification result, which is used to indicate whether the ID number has been registered in the blockchain system. In the case where the verification result indicates that the ID number is not registered, the real-name authentication is performed based on the ID number and name in the real-name authentication information with the mobile phone number, and the face verification is performed based on the face verification video in the real-name authentication information. The server executes steps 406 and 407 to obtain the target blockchain identifier. In the case where the verification result indicates that the ID number has been registered, the real-name authentication is performed based on the ID number and name in the real-name authentication information with the mobile phone number, and the face verification is performed based on the face verification video in the real-name authentication information. In response to the first user account passing the real-name authentication and the face verification, the server submits an association request to the blockchain system, which is used to request the blockchain system to associate the first user account with the second user account, and the second user account is a blockchain account registered based on the above-mentioned ID number in the blockchain system. The server receives the target user identifier returned by the blockchain system. The target blockchain identifier is obtained by encrypting the second user account based on the public and private key pair of the second user account in the blockchain system. By verifying whether the ID number has been registered in the blockchain system, repeated registration in the blockchain system can be avoided, thereby ensuring that the ID number corresponds to the blockchain account in the blockchain system.

[0226] 406. In response to the first user account passing the real-name authentication and the face verification, the server sends a registration request to the blockchain system, where the registration request is used to instruct the blockchain system to register the blockchain account based on the real-name authentication information.

[0227] In the embodiment of the present application, if the real-name authentication information of the first user account has passed both the real-name authentication and the face authentication, indicating that the first user account does not have a risk, the server can send a registration request to the blockchain system, and the registration request carries the ID number, name, and mobile phone number in the real-name authentication information. The blockchain system can register a blockchain account based on the real-name authentication information and obtain a second user account that uniquely corresponds to the ID number.

[0228] 407. The server obtains the target blockchain identifier and the second user account returned by the blockchain system. The target blockchain identifier is obtained by encrypting the second user account based on the public-private key pair of the second user account in the blockchain system.

[0229] In an embodiment of the present application, the server can receive a registration response returned by the blockchain system, the registration response including the second user account and the target blockchain identifier. After registering the second user account, the blockchain system can encrypt the second user account based on the public-private key pair corresponding to the target application to obtain the target blockchain identifier corresponding to the first user account in the target application. The public-private key pair of the second user account is generated by the blockchain system based on the SDK.

[0230] In some embodiments, the blockchain system generates different public-private key pairs for different types of applications, and the public-private key pair of the second user account is the public-private key pair corresponding to the target application to which the first user account belongs. In the above manner, the generated blockchain identifier is uniquely corresponding to the application, so that the same blockchain account can be bound to user accounts in different applications through different blockchain identifiers, which improves the diversity of blockchain identifiers and facilitates separate management.

[0231] In some embodiments, the blockchain system generates different public-private key pairs for different ID numbers, and the public-private key pair of the second user account is the public-private key pair corresponding to the ID number in the real-name authentication information. The above method enables the second user account to correspond to a unique blockchain identifier, which is convenient for unified management. Of course, the blockchain system can also generate different public-private key pairs for different first user accounts, which will not be repeated here.

[0232] 408. The server establishes a binding relationship between the first user account and the target blockchain identifier, and returns the target blockchain identifier to the terminal.

[0233] In an embodiment of the present application, after obtaining the target blockchain identifier, the server can bind the first user account and the target blockchain identifier, and then return the target blockchain identifier to the terminal for display by the terminal.

[0234] It should be noted that, in order to make the authentication and registration process described in the above steps 404 to 408 easier to understand, see Figure 8 , Figure 8 Schematic diagram of an account authentication process provided according to an embodiment of the present application. Figure 8As shown, it includes steps 801 to 805. 801. The first user account submits real-name authentication information. 802. Based on the three elements of ID card number, name and mobile phone number in the real-name authentication information, real-name authentication is performed. If the real-name authentication fails, return to step 801; if the real-name authentication passes, execute 803. 803. Based on the face verification video in the real-name authentication information, face verification is performed. If the face verification fails, return to step 801; if the face verification passes, execute step 804. 804. Register a second user account in the blockchain system and bind the target blockchain identifier of the first user account. 805. Manage the binding relationship between the first user account and the target blockchain identifier.

[0235] It should be noted that the above steps 404 to 408 exemplarily illustrate the process of the server performing account authentication and returning the target blockchain identifier. In the above process, the server is the application background server of the target application, and the application background server performs real-name authentication and face verification as an example. In some embodiments, the above real-name authentication and face verification process is implemented by a third-party authentication server, and the application background server can call the interface of the authentication server. To make the process easier to understand, see Fig. 9 As shown, Fig. 9 FIG. 1 is a schematic diagram of another account authentication process provided according to an embodiment of the present application. Fig. 9As shown, it includes steps 901 to 915. 901. The terminal displays a real-name authentication page, which is used to enter real-name authentication information. 902. The terminal sends the first user account, ID number and name to the universal gateway interface of the application background server. 903. The application background server requests the blockchain account management service to verify the first user account and ID number based on the universal gateway interface. 904. The application background server verifies whether the first user account is bound to a blockchain identifier based on the blockchain account management server. If the blockchain identifier is not bound, further verify whether the ID number has been bound to other user accounts and registered blockchain accounts. 905. The application background server returns the verification result to the universal gateway interface based on the blockchain account management service, and returns the verification result to the terminal based on the universal gateway interface. If the first user account has been bound to a blockchain identifier, the verification result is the target blockchain identifier bound to the first user account; if the ID number has been bound to other user accounts, the verification result is a prompt that the ID number is unavailable; if the ID number has not registered a blockchain account, the verification result is an indication that the ID number has not registered a blockchain account. 906. In the case where the ID card number has not been registered for a blockchain account, the application background server sends login status information to the blockchain account management service based on the universal gateway interface, and the login status information includes the first user account. 907. The application background server calls the security component based on the blockchain account management service to verify the security policy. 908. The application background server executes the security component policy based on the security component, and the security component policy is used to verify the identity information. 909. The application background server returns the security component return code to the blockchain account management service based on the security component, and the security component return code is used to determine whether the verification is passed. 910. The application background server determines whether the verification is passed based on the blockchain account management service. 911. If the verification is not passed, the application background server returns the verification information to the universal gateway interface based on the blockchain account management service. 912. The application background server sends the verification information to the terminal based on the universal gateway interface, and the terminal displays the verification information on the real-name authentication page to prompt re-verification. 913. In the case where the first user account is not bound to a mobile phone number, the real-name authentication page in the terminal jumps to display the mobile phone binding page based on the security component. 914. The terminal displays the binding result on the real-name authentication page. 915. When the first user account has been bound to the mobile phone number, the terminal requests a verification code to be sent and displays the received verification code.

[0236] If the verification is successful, the face verification process will be executed. Fig.10 is a schematic diagram of a face verification process provided according to an embodiment of the present application, see Fig.10As shown, it includes steps 1001 to 1020. 1001. The application background server locks the real-name authentication process based on the blockchain account management service, so as to ensure that the terminal cannot submit a new real-name authentication process when the current real-name authentication process is not completed. 1002. The application background server requests the first user account to bind the mobile phone number based on the blockchain account management service, and the terminal displays the mobile phone binding page. 1003. The terminal returns the bound mobile phone number to the application background server based on the mobile phone binding page. It should be noted that if the first user account has been bound to the mobile phone number, it is not necessary to perform the above steps 1002 and 1003. 1004. The application background server requests the authentication server to verify the consistency of the mobile phone number, ID card number and name based on the blockchain account management service. 1005. The authentication server returns the verification result to the blockchain account management service of the application background server. 1006. If the verification result is inconsistent, the application background server returns an inconsistent error to the terminal. 1007. Based on the blockchain account management service, the application backend server sends real-name authentication information to the authentication server, and the real-name authentication information includes the ID number, name, first user account, order number (orderNo) and signature authentication parameter (signTicket). Among them, the order number is generated by the authentication server, and the signature authentication parameter is used to request the generation of a signature. 1008. The authentication server returns the user account identifier (h5faceid), the order number and the domain name (optimalDomain) used when starting face verification to the application backend server. 1009. The application backend server sends the login authentication ticket (accessToken) and the first user account to the authentication server. Among them, the login authentication ticket is generated by the authentication server. 1010. The authentication server returns the face verification authentication parameter (nonceTicket) to the application backend server, and the face verification authentication parameter is valid once. 1011. Based on the blockchain account management service, the application backend server determines the authentication signature according to the authentication signature function, and the input of the authentication signature function is the application identifier, order number, first user account, version number, user account identifier, face verification authentication parameter and one-time parameter (nonce). 1012. The application backend server caches the real-name authentication information based on the blockchain account management service, which includes the ID number, name, mobile phone number and order number. 1013. The application backend server returns the user account identifier, order number, one-time parameters, signature and domain name to the terminal based on the blockchain account management service. 1014. The terminal requests access to the face verification page provided by the authentication server. 1015. The authentication server obtains the face verification address redirected by 302. 1016. The authentication server returns the face verification address redirected by 302 to the terminal. 1017. The terminal jumps to the face verification page. 1018. The authentication server collects the face verification video based on the face verification page.1019. The authentication server obtains the face verification video submitted by the face verification page. 1020. The authentication server returns the face verification result to the terminal. It should be noted that the redirection and verification process of the face verification in the above steps 1013 to 1019 can be found in . Fig.12 shown.

[0237] If the face verification is passed, the process of registering a blockchain account and binding a blockchain ID will be executed. Fig.11 This is a schematic diagram of a blockchain identification binding process provided according to an embodiment of the present application, see Fig.11As shown, it includes steps 1101 to 1118. 1101. The terminal sends the face verification result, order number, signature and first user account to the application background server. 1102. The application background server performs signature verification, which is used to verify whether the signature in the terminal request is consistent with the encrypted signature. If the signature verification fails, execute 1103; if the signature verification succeeds, execute 1104. 1103. The application background server returns the signature verification failure to the terminal. 1104. The application background server obtains the cached ID number, name and order number, and performs order number verification. The order number verification is used to verify whether the order number sent by the terminal is consistent with the cached order number. If the order number verification fails, execute 1105; if the order number verification succeeds, execute 1106. 1105. The application background server returns the order number verification failure to the terminal. 1106. The application background server performs ID number verification, which is used to verify whether the ID number has been registered with a blockchain system account. If it has been registered, execute 1107; if it has not been registered, execute 1108. 1107. The application background server returns to the terminal that the ID number has been registered for the blockchain system account. 1108. The application background server requests the blockchain system server to generate a public-private key pair for the ID number based on the SDK, and the public-private key pair is encrypted by AES256 and stored in redis. 1109. The application background server sends the application identification, application key (appkey), the public-private key pair of the application, the ID number, the name and the mobile phone number to the blockchain system server. 1110. The blockchain system server performs real-name registration and obtains the unique user identification (UID, User Identification) of the natural person in the blockchain system, that is, the second user account. 1111. The blockchain system server returns the second user account to the application background server. 1112. If the registration fails, the application background server returns the registration failure to the terminal. 1113. The application background server sends the application identification, application key (appkey), the public-private key pair of the ID number and the second user account to the blockchain system server. 1114. The blockchain system server generates a blockchain address corresponding to the second user account, that is, the target blockchain identifier. 1115. The blockchain system server returns the target blockchain identifier to the application background server. 1116. The application background server binds the first user account and the target blockchain identifier. If the binding fails, execute 1117; if the binding succeeds, execute 1118. 1117. The application background server returns a binding failure to the terminal. 1118. The application background server stores the binding relationship between the first user account, the ID number, and the target blockchain identifier.

[0238] Fig.12 FIG. 1 is a schematic diagram of another face recognition process provided according to an embodiment of the present application. Fig.12As shown, it includes steps 1201 to 1229. 1201. The authentication server refreshes the login authentication ticket (accessToken) based on the proxy service. 1202. The authentication server sends the application identifier (appID), key (secret) and authorization type (grantType) to the authentication server background based on the proxy service. 1203. The authentication server returns the login authentication ticket and expiration time (expireTime) to the proxy service based on the authentication server background. 1204. The authentication server sends the application identifier and login authentication ticket to the authentication server background based on the proxy service. 1205. The authentication server returns the signature authentication parameters and expiration time to the proxy service based on the authentication server background. 1206. The authentication server caches the signature authentication parameters and expiration time in the redis database. 1207. The terminal sends the ID number, name and mobile phone number to the application background server based on the real-name authentication page. 1208. The application background server generates a signature based on the blockchain account management service. 1209. The application background server sends the real-name authentication information and signature to the authentication server based on the blockchain account management service. 1210. The authentication server returns the user account identifier, order number, and domain name used when starting face verification to the application background server based on the authentication server background. 1211. The application background server sends the application identifier, login authentication ticket, and first user account to the authentication server based on the blockchain account management service. 1212. The authentication server returns the face verification authentication parameters to the application background server based on the authentication server background. 1213. The application background server generates a signature based on the blockchain account management service. 1214. The application background server caches the first user account, real-name authentication information, and order number in the redis database. 1215. The application background server returns the user account identifier, order number, one-time parameters, signature, and domain name to the terminal based on the blockchain account management service. 1216. The terminal calls the face verification service, redirects the face verification address, and sends the signature and callback face verification address. 1217. The authentication server performs signature verification based on the authentication server background. 1218. The authentication server returns the address of the face verification page after 302 redirection to the terminal based on the authentication server background. 1219. The terminal is redirected to the face verification page provided by the authentication server. 1220. The authentication server collects the face verification video based on the face verification page. 1221. The authentication server uploads the face verification video to the authentication server backend based on the face verification page. 1222. The authentication server verifies the login status, performs face comparison and liveness detection based on the authentication server backend, and obtains the verification result. 1223. The authentication server returns the face verification result with signature to the face verification page based on the authentication server backend. 1224. The authentication server returns the face verification result to the terminal based on the face verification page.1225. The terminal sends the face verification result, order number and signature to the application background server. 1226. The application background server performs signature verification based on the blockchain account management service. 1227. The application background server obtains the cached real-name authentication information and order number from the redis database. 1228. The application background server performs order number verification based on the blockchain account management service. 1229. The application background server returns the verification result to the terminal based on the blockchain account management service.

[0239] 409. The terminal obtains the target blockchain identifier returned by the server and displays the target blockchain identifier.

[0240] In an embodiment of the present application, the terminal is able to receive the target blockchain identifier returned by the server and then display the target blockchain identifier.

[0241] For example, Fig.13 is a schematic diagram of a target blockchain identifier provided according to an embodiment of the present application. Fig.13 As shown, the terminal displays a pop-up window on the resource exchange page, which displays a prompt message 1301 including a target blockchain identifier and an exchange control 1302. The exchange control is used to send an exchange request to the server after being triggered.

[0242] 410. The terminal sends an exchange request to the server, where the exchange request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier.

[0243] In an embodiment of the present application, the terminal can send an exchange request to the server, and the exchange request carries a target blockchain identifier and a target resource identifier.

[0244] 411. In response to the redemption request for the target digital resource, the server sends an association request to the blockchain system, where the association request is used to instruct the blockchain system to associate the target blockchain identifier with the target resource identifier.

[0245] In an embodiment of the present application, the server is able to receive a redemption request for a target digital resource sent by a terminal, and then generate an association request based on the redemption request. The server sends the association request to the blockchain system, and the association request carries a target blockchain identifier and a target resource identifier.

[0246] It should be noted that the server can establish and store the binding relationship between the target blockchain identifier and the resource identifiers of multiple digital resources, thereby establishing the affiliation relationship between the target blockchain identifier and the digital resource identifiers of the digital resources. Fig.14 As shown, Fig.14 FIG. 1 is a schematic diagram of establishing a binding relationship according to an embodiment of the present application. Fig.14As shown, based on the social account 1401, the target application is logged in to obtain the first user account 1402. After real-name authentication based on the real-name authentication information 1403 of the first user account, the second user account 1404 is registered in the blockchain system. Based on the blockchain SDK 1405, a public-private key pair 1406 corresponding to the ID number can be generated. The second user account is encrypted based on the public-private key pair 1406 to obtain the target blockchain identifier 1407. The server can establish a binding relationship between the first user account 1402 and the target blockchain identifier 1407. The server can also establish a binding relationship between the target blockchain identifier 1407 and the digital resource identifier 1408. It should be noted that the server stores the following relationships: the corresponding relationship between the first user account and the public-private key pair; the corresponding relationship between the first user account and the target blockchain identifier and the ID number; the binding relationship between the target blockchain identifier and the first user account; the binding relationship between the ID number and the first user account. It should be noted that the above-mentioned public-private key pair 1406 can be generated and managed by the blockchain system based on KMS (Key Management Service).

[0247] It should be noted that after obtaining the public-private key pair 1406, the server can also encrypt and store the public-private key pair 1406. The encryption and decryption methods include remote encryption and decryption methods based on KMS, local encryption and decryption methods based on KMS, and encryption and decryption methods based on AES256.

[0248] In some embodiments, the server uses a remote encryption and decryption method based on KMS to process the public-private key pair 1406. Among them, the public-private key pair of the second user account is the first public-private key pair of the first user account. The server is an application background server, which is used to provide background services for the target application. The server encrypts the first public-private key pair in the following manner: sending a key generation request for the first user account to the blockchain system, and receiving the first public-private key pair returned by the blockchain system. Then, a key encryption request is sent to the key management server, and the key encryption request carries the master key of the application background server, the first user account, and the first public-private key pair. Finally, the first encrypted string returned by the key management server is stored in the database. Among them, the database is used to provide data storage services for the application background server. The key management server is used to provide KMS. The master key is generated by the application background server based on KMS and is unique. The server decrypts the first encrypted string in the following manner: obtaining the first encrypted string from the database. Then, a key decryption request is sent to the key management server, and the key decryption request carries the master key and the first encrypted string. Finally, the first public-private key pair returned by the key management server is received. By encrypting and decrypting the first public-private key pair of the first user account remotely based on a key management server, the security of the first public-private key pair can be improved. Since the application background server does not need to perform the encryption and decryption process, the computing resources of the application background server can be saved.

[0249] For example, Fig.15 Schematic diagram of a process for encrypting a public-private key pair according to an embodiment of the present application. Fig.15As shown, the following steps are included: 1501. The application background server requests the key management server to create a master key. 1502. The key management server creates a master key and returns the master key to the application background server. 1503. The application background server stores the master key in the database. 1504. The application background server requests the blockchain system server to generate a public-private key pair for the first user account. 1505. The blockchain system server returns the first public-private key pair of the first user account to the application background server. 1506. The application background server sends a key encryption request carrying the master key, the first user account, and the public key in the first public-private key pair to the key management server. 1507. The key management server encrypts the public key in the first public-private key pair to obtain the public key ciphertext in the first encrypted string. 1508. The key management server returns the public key ciphertext in the first encrypted string to the application background server. 1509. The application background server sends a key encryption request carrying the master key, the first user account, and the private key in the first public-private key pair to the key management server. 1510. The key management server encrypts the private key in the first public-private key pair to obtain the private key ciphertext in the first encrypted string. 1511. The key management server returns the private key ciphertext in the first encrypted string to the application background server. 1512. The application background server stores the public key ciphertext in the database. 1513. The application background server stores the private key ciphertext in the database. 1514. The application background server obtains the master key from the database based on the first user account. 1515. The application background server obtains the public key ciphertext and the private key ciphertext in the first encrypted string from the database based on the first user account. 1516. The application background server sends a key decryption request carrying the master key and the public key ciphertext and the private key ciphertext in the first encrypted string to the key management server. 1517. The key management server decrypts the public key ciphertext and the private key ciphertext respectively to obtain the public key and the private key in the first public-private key pair. 1518. The key management server returns the public key and the private key in the first public-private key pair to the application background server.

[0250] In some embodiments, the server uses a local encryption and decryption method based on KMS to process the public-private key pair 1406. Among them, the public-private key pair of the second user account is the second public-private key pair of the first user account. The server is an application background server, which is used to provide background services for the target application. The server encrypts the second public-private key pair in the following way: send a key generation request for the first user account to the blockchain system, and receive the second public-private key pair returned by the blockchain system. Then, the second public-private key pair is encrypted based on the data key of the application background server to obtain a second encrypted string. Finally, the first user account, the second encrypted string, and the ciphertext of the data key corresponding to the data key are stored in the database. Among them, the database is used to provide data storage services for the application background server. The server decrypts the second encrypted string in the following way: obtain the second encrypted string from the database, decrypt the second encrypted string based on the data key of the application background server, and obtain the second public-private key pair. Among them, the data key and the ciphertext of the data key are obtained based on the master key of the application background server. The data key and the ciphertext of the data key are obtained in the following way: the application background server sends a key creation request to the key management server to obtain the master key of the application background server. Then, based on the master key, the data key and the ciphertext of the data key are obtained from the key management server. Finally, the data key is cached and the ciphertext of the data key is stored in the database. By adopting the local decryption method to encrypt and decrypt the second public-private key pair of the first user account, the application background server can realize the encryption and decryption of the second public-private key pair locally, which can improve the security of the second public-private key pair and the efficiency of encryption and decryption.

[0251] For example, Fig.16 is a schematic diagram of another process for encrypting a public-private key pair according to an embodiment of the present application. Fig.16As shown, the following steps are included: 1601. The application background server requests the key management server to create a master key. 1602. The key management server creates a master key and returns the master key to the application background server. 1603. Based on the master key, the application background server requests the key management server for the data key and the ciphertext of the data key. 1604. The key management server returns the data key and the ciphertext of the data key to the application background server. 1605. The application background server stores the ciphertext of the data key in the database. 1606. The application background server obtains the data key from the key management server based on the ciphertext of the data key. 1607. The application background server caches the data key. 1608. The application background server sends a key generation request for the first user account to the blockchain system server. 1609. The blockchain system server returns the second public-private key pair to the application background server. 1610. The application background server encrypts the public key and the private key in the second public-private key pair based on the data key to obtain a second encrypted string, which includes the public key ciphertext and the private key ciphertext. Among them, the application background server uses AES256 for encryption. 1611. The application background server stores the first user account, the second encrypted string, and the ciphertext of the data key corresponding to the data key in the database. 1612. The application background server obtains the second encrypted string from the database based on the first user account. 1613. The application background server decrypts the second encrypted string based on the data key to obtain a second public-private key pair.

[0252] In some embodiments, the server uses a shared key to process the public-private key pair 1406. Among them, the public-private key pair of the second user account is the third public-private key pair of the first user account. The server is an application background server, which is used to provide background services for the target application. The server encrypts the third public-private key pair by sending a key generation request for the first user account to the blockchain system and receiving the third public-private key pair returned by the blockchain system. Then, the third public-private key pair is encrypted based on the key in the configuration file to obtain a third encrypted string. Finally, the first user account and the third encrypted string are stored in a database. Among them, the database is used to provide data storage services for the application background server. The server decrypts the third encrypted string by obtaining the third encrypted string from the database, decrypting the third encrypted string based on the key in the configuration file, and obtaining the third public-private key pair. By using a shared key to perform local encryption and decryption of the third public-private key pair of the first user account, the key can be pulled into the memory through the configuration file, thereby improving the security of the third public-private key pair and the efficiency of encryption and decryption.

[0253] For example, Fig.17 is a schematic diagram of another process for encrypting a public-private key pair according to an embodiment of the present application. Fig.17As shown, the following steps are included: 1701. The application background server generates a globally shared key based on a script command, and the key is written into a configuration file. Among them, the key in the configuration file is generated based on AES256 technology. 1702. The application background server sends a key generation request for the first user account to the blockchain system server. 1703. The blockchain system server returns a third public-private key pair to the application background server. 1704. The application background server reads the key from the configuration file. 1705. The application background server encrypts the public key and the private key in the third public-private key pair based on the key in the configuration file to obtain a third encrypted string, which includes a public key ciphertext and a private key ciphertext. Among them, the application background server uses AES256 for encryption. 1706. The application background server stores the first user account and the third encrypted string in the database. 1707. The application background server obtains the third encrypted string from the database based on the first user account. 1708. The application background server reads the key from the configuration file. 1709. The application backend server decrypts the public key ciphertext and the private key ciphertext in the third encryption string based on the key in the configuration file, and obtains the public key and the private key in the third public-private key pair.

[0254] In some embodiments, the server processes the public-private key pair 1406 by isolating the keys of the user accounts. Among them, the public-private key pair of the second user account is the fourth public-private key pair of the first user account. The server is an application background server, which is used to provide background services for the target application. The server encrypts the fourth public-private key pair in the following manner: based on the first user account and the timestamp, the data key and the ciphertext of the data key of the first user account are generated. Then, a key generation request for the first user account is sent to the blockchain system, and the fourth public-private key pair returned by the blockchain system is received. Then, the fourth public-private key pair is encrypted based on the data key to obtain a fourth encrypted string. Finally, the first user account, the fourth encrypted string and the ciphertext of the data key are stored in a database. Among them, the database is used to provide data storage services for the application background server. The server decrypts the fourth encrypted string in the following manner: based on the first user account, the ciphertext of the fourth encrypted string and the data key is obtained from the database, and then, based on the ciphertext of the data key, the data key is obtained. Finally, the fourth encrypted string is decrypted based on the data key to obtain a fourth public-private key pair. By isolating the data keys of different user accounts, it can be applied to scenarios with high security requirements. In addition, the encryption and decryption process can be completed locally on the application background server, which can improve the efficiency of encryption and decryption.

[0255] For example, Fig.18 is a schematic diagram of another process for encrypting a public-private key pair according to an embodiment of the present application. Fig.18As shown, it includes the following steps: 1801. The application background server generates the data key and the ciphertext of the data key of the first user account based on the first user account and the timestamp through the master key generation module. 1802. The application background server requests the blockchain system server to generate a public-private key pair for the first user account. 1803. The blockchain system server returns the fourth public-private key pair of the first user account to the application background server. 1804. The application background server encrypts the public key and the private key in the fourth public-private key pair based on the data key to obtain a fourth encrypted string, which includes a public key ciphertext and a private key ciphertext. Among them, the application background server uses AES256 for encryption. 1805. The application background server stores the first user account, the fourth encrypted string and the ciphertext of the data key in the database. 1806. The application background server obtains the ciphertext of the fourth encrypted string and the data key from the database based on the first user account. 1807. The application background server obtains the data key based on the ciphertext of the data key. 1808. The application backend server decrypts the public key ciphertext and the private key ciphertext in the fourth encryption string based on the data key, respectively, to obtain the public key and the private key in the fourth public-private key pair.

[0256] 412. The server returns binding information to the terminal, where the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

[0257] In an embodiment of the present application, the server receives an association response returned by the blockchain system based on the association request, and the association response is used to indicate that a binding relationship between the target blockchain identifier and the target resource identifier has been established. The server generates binding information based on the association response and returns the binding information to the target application in the terminal.

[0258] 413. The terminal displays a resource display page, where the resource display page is used to display at least one digital resource that has been redeemed by the first user account.

[0259] In the embodiment of the present application, the user can view the redeemed digital resources through the resource display page. In response to the digital resource viewing operation, the terminal displays the resource display page.

[0260] It should be noted that the step numbers in the embodiments of the present application are for ease of description and do not limit the order in which the steps are executed. Step 413 can be executed before step 401, can be executed after step 412, and can be executed at any time between step 401 and step 412, and the embodiments of the present application do not limit this.

[0261] 414. In response to a signature operation on any digital resource in the resource display page, the terminal displays a signature selection page, where the signature selection page is used to select a signature image.

[0262] In an embodiment of the present application, a user can sign a redeemed digital resource by using a signature image. Each digital resource in the resource display page corresponds to a signature control, and the user triggers the signature operation of the digital resource by triggering the signature control of any digital resource. Based on the detection of the signature operation, the terminal can display a signature selection page, which displays at least one signature image to be selected. Of course, the user can also create a new signature image based on the signature selection page.

[0263] In some embodiments, a user can create a signature image based on a signature creation page. The terminal displays a signature creation page, which is used to create a signature image. In response to a signature image creation operation based on the signature creation page, the terminal sends a signature review request of a first user account to a server, and the signature review request carries the signature image created by the signature image creation operation. Correspondingly, the server receives the signature review request of the first user account and reviews the signature image carried by the signature review request. In response to the signature image passing the review, the server stores the review result of the signature image, and the review result is used to indicate whether the signature image has passed the review. The server returns the review result to the target application in the terminal. The terminal receives the review result returned by the server based on the signature review request. The above method can not only enable users to customize signature images, but also prevent users from using non-compliant signature images, thereby improving the efficiency of users in creating signature images, and signature images have diversity.

[0264] For example, Fig.19 is a schematic diagram of a signature creation page provided according to an embodiment of the present application. Fig.19 As shown, the signature creation page displays prompt information 1901, signature area 1902, confirmation control 1903 and skip control 1904. Among them, signature area 1902 is used to enter the signature, confirmation control 1903 is used to submit the signature image for review after being triggered, and skip control 1904 is used to skip the signing step.

[0265] 415. In response to the selection operation of any signature image, the terminal sends a signature binding request to the server, where the signature binding request is used to instruct the server to bind the selected target signature image with the digital resource.

[0266] In an embodiment of the present application, the terminal can send a signature binding request to the server, and the signature binding request carries the target signature image selected by the selection operation and the target resource identifier of the target digital resource.

[0267] In some embodiments, the target signature image is an image that has not been reviewed. The terminal uploads the target signature image and requests the server to review the target signature image by sending a signature binding request.

[0268] For example, see Fig. 20 As shown, Fig. 20 FIG. 1 is a schematic diagram of a signature image review process provided according to an embodiment of the present application. Fig. 20 As shown, it includes the following steps: 2001. The terminal displays the signature selection page and receives the locally generated signature image. 2002. The terminal uploads the signature image to the server. 2003. The server stores the signature image based on the image upload service and returns the image address of the signature image to the terminal. 2004. The terminal sends the first user account, the target resource identifier and the image address to the server. 2005. The server generates a unique message identifier based on the resource background service. The message identifier consists of the timestamp of the current time, the first user account and the target resource identifier encrypted by md5: hdid=timestamp-vuid-md5(nftID), where hdid represents the message identifier, timestamp represents the timestamp of the current time, vuid represents the first user account, md5() represents md5 encryption processing, and nftID represents the target resource identifier. 2006. The server caches the signature information of the target resource identifier in the redis database, and the default state is unreviewed. 2007. Based on the resource background service, the server submits the first user account, target resource identifier, message identifier and image address to the image review service for review. 2008. Based on the image review service, the server returns the review result to the resource background service. 2009. Based on the resource background service, the server returns the review result to the terminal, which is displayed on the signature selection page by the terminal. 2010. Based on the image review service, the server calls the review result according to the message identifier. 2011. Based on the resource background service, the server parses the message identifier to obtain the first user account and the target resource identifier encrypted by MD5. 2012. Based on the resource background service, the server obtains the review information of the signature image of the first user account corresponding to the message identifier according to the first user account, the message identifier and the target resource identifier encrypted by MD5. Receive the message identifier encrypted by MD5, the image address and the review status corresponding to the target resource identifier. 2013. Based on the resource background server, the server determines whether the message identifier is consistent. 2014. If not consistent, return directly. 2015. If they are consistent, the server updates the audit status in the signature information and obtains the result of the updated status. 2016. The server returns the result to the terminal.

[0269] It should be noted that the signature information is stored in the form of a hashmap:

[0270] hash:vuid:

[0271] md5(nftID1): (md5(hdid1)+pic_url1+status1)

[0272] md5(nftID2): (md5(hdid2)+pic_url2+status2)

[0273] Among them, pic_url indicates the image address, and status indicates the review status.

[0274] It should be noted that when the message identifiers are consistent, the server obtains the audit status based on the audit result status. The audit result status is represented by checkstatus, checkstatus==0, indicating that the audit status = unaudited (under review); checkstatus==1, indicating that the audit status = audit passed, and the key of the latest audited signature image needs to be updated; checkstatus==2, indicating that the audit status = audit failed.

[0275] 416. The server obtains a signature binding request for the target digital resource, where the signature binding request carries the target signature image of the first user account.

[0276] In an embodiment of the present application, the server can parse the signature binding request of the target digital resource to obtain the target resource identifier and target signature image of the target digital resource.

[0277] 417. The server binds the target signature image with the target digital resource.

[0278] In the embodiment of the present application, the server can establish the target resource identifier of the target signature image and the target digital resource.

[0279] It should be noted that in order to make the relationship between the first user account, the target blockchain identifier and the digital resource identifier in the embodiment of the present application easier to understand, see Fig.21 As shown, Fig.21 is a relationship diagram provided according to an embodiment of the present application. Fig.21 , the first user account 2101 can represent the user, and after real-name authentication, the authenticity of the user's identity is guaranteed. There is a two-way binding relationship between the target blockchain identifier 2102 and the first user account 2101. After exchanging the digital resource, the first user account 2101 can establish a binding relationship between the first user account and the digital resource identifier 2103 of the digital resource by adding a signature image to the digital resource. In the blockchain system, after the first user account 2101 exchanges the digital resource, a binding relationship between the digital resource identifier of the digital resource and the target blockchain identifier can be established.

[0280] It should be noted that users can redeem digital resources through applications provided by different platforms, and the user's ID number in the blockchain system uniquely corresponds to a blockchain account. The blockchain system can assign different blockchain identifiers to the user accounts in applications on different platforms. Fig. 22 As shown, Fig. 22 is a mapping relationship diagram provided according to an embodiment of the present application. Fig. 22 As shown, user X is a natural person who has registered user accounts on platforms A, B, and C. When real-name authentication is performed through the application of any platform, the blockchain application layer determines that the natural person corresponds to the same blockchain account in the blockchain system. Based on the underlying chain of the blockchain system, according to the blockchain account and the public and private key pairs corresponding to different platforms, blockchain identifiers corresponding to different platforms can be generated.

[0281] It should be noted that after the first user account obtains the digital resource through redemption, it can also give the digital resource it already owns to other user accounts. In response to the gift operation of any digital resource in the resource display page, the terminal displays the resource gift page. In response to the gift blockchain identifier input based on the resource gift page, a digital resource transfer request is sent to the blockchain system, and the digital resource transfer request is used to instruct the blockchain system to bind the digital resource identifier of the digital resource with the gift blockchain identifier. In some embodiments, the blockchain system stores the resource series identifier to which the digital resource identifier of the digital resource belongs, and the above-mentioned digital resource transfer request is used to instruct the blockchain system to bind the resource series identifier with the gift blockchain identifier. By providing the resource gift function, digital resources can be circulated between user accounts, thereby improving the circulation efficiency of digital resources.

[0282] For example, see Fig.23 As shown, Fig.23 FIG. 1 is a schematic diagram of transferring digital resources according to an embodiment of the present application. Fig.23As shown, different natural persons correspond to different blockchain accounts in the blockchain system. For any blockchain account, the blockchain account can be bound to the blockchain identifier registered by the corresponding natural person based on different business providers. After the blockchain account is encrypted based on the public and private key pair corresponding to the business provider, the corresponding blockchain identifier is obtained. The blockchain identifier is bound to a unique resource series identifier, and the resource series identifier is bound to at least one digital resource identifier. For example, if a movie has a unique resource series identifier in the blockchain system, and the movie is limited to 400 copies, then the resource series identifier corresponds to 400 digital resource identifiers. After the user account redeems the movie, the blockchain identifier of the user account is bound to the resource series identifier, and the resource series identifier is bound to one or more digital resource identifiers, which is the same as the number redeemed by the user account. When a user account gives the redeemed digital resources to other user accounts, the ownership of the digital resources will be transferred, see Fig.23 The digital resources in the identifier are 4 and 6.

[0283] It should be noted that the terminal can query the blockchain identifier bound to the user account. Fig.24 As shown, Fig.24 1 is a flowchart of querying a blockchain identifier according to an embodiment of the present application. Fig.24 As shown, the following steps are included: 2401. The terminal sends a blockchain identifier query request to the application background server. 2402. The application background server obtains the first user account based on the logged-in account. 2403. The application background server sends a query request to the database. 2404. The database queries the blockchain identifier of the first user account. 2405. The database returns the blockchain identifier and binding status of the first user account to the application background server. 2406. The application background server determines the binding status. 2407. If the binding status is bound, the blockchain identifier of the first user account and the binding status are returned to the terminal as bound. 2408. If the binding status is the default status, the application background server sends a status query request to the blockchain system server. 2409. The blockchain system server returns the binding status to the application background server. 2410. The application background server updates the binding status stored in the database. 2411. If the updated binding status is bound, the two-way binding relationship between the identity information, the first user account and the blockchain identifier is stored in the database. 2412. If the updated binding status is binding failure, clear the blockchain identifier of the first user account in the database. 2413. Return the updated binding status to the terminal. 2414. When the first binding is successful, synchronize the digital resource identifier. 2415. Report the real-name authentication information of the first user account to the authentication information management server.

[0284] It should be noted that in order to make the solution architecture provided in the embodiment of the present application easier to understand, see Fig.25 As shown, Fig.25 Schematic diagram of a solution architecture provided according to an embodiment of the present application. Fig.25 As shown, the solution architecture includes a front end 2501, an access layer 2502, a business back end 2503, basic services 2504, and a data storage service 2505. Among them, the front end 2501 includes a digital resource interface 25011, a digital resource display page 25012, a digital resource exchange page 25013, a digital resource reservation page 25014, a real-name authentication page 25015, a user account information page 25016, and a digital resource back end management page 25017. The access layer 2502 includes an application access layer 25021, a general gateway layer 25022, and a digital resource back end layer 25023. The business back end 2503 includes an item service 25031 in the application, a digital resource page management service 25032, a digital resource exchange service 25033, a digital resource reservation service 25034, an account registration service 25035, a user account management service 25036, and a back end management service 25037. Among them, the item service 25031 in the application is used to provide an item list. The digital resource page management service 25032 is used to provide a digital resource list, digital resource details and digital resource exchange records. The digital resource exchange service 25033 is used for digital resource price display, digital resource transfer and digital resource gifting. The digital resource reservation service 25034 is used for sharing, displaying details, helping and making reservations. The account registration service 25035 is used for face verification, binding blockchain identifiers and obtaining blockchain identifiers. The user account management service 25036 is used to display the item list, item transfer records, signature review and blockchain identifier of the user account. The background management service 25037 is used to declare resource sequences, publish digital resources and manage digital resources. The basic service 2504 is used to bind mobile phone numbers 25041, account authorization 25042, login status verification 25043, graphic code verification 25044 and provide security components 25045. The basic service 2504 also includes an interface 25046 for connecting to third-party authentication services and blockchain systems. The data storage service 2505 includes at least one database, such as DB, REDIS, etc.

[0285] In an embodiment of the present application, by using the real-name authentication information of the first user account in the target application, the first user account can be authenticated by real name and face verification, and then after passing the above authentication, the public-private key pair of the second user account based on the blockchain system is obtained, and the target blockchain identifier obtained by encrypting the second user account is made so that the target blockchain identifier can represent the second user account. Finally, by binding the first user account and the target blockchain identifier, the authentication of the first user account can be completed securely.

[0286] Fig.26 is a block diagram of an account authentication device provided according to an embodiment of the present application. The device is used to execute the steps in the above account authentication method, see Fig.26 The device includes: an authentication module 2601, a first acquisition module 2602 and a relationship establishment module 2603.

[0287] The authentication module 2601 is used to perform real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account logged in by the target application;

[0288] A first acquisition module 2602 is configured to acquire a target blockchain identifier in response to the first user account passing the real-name authentication and the face verification, where the target blockchain identifier is encrypted based on a public-private key pair of a second user account in the blockchain system.

[0289] The relationship establishing module 2603 is used to establish a binding relationship between the first user account and the target blockchain identifier.

[0290] In some embodiments, Fig. 27 is a block diagram of another account authentication device provided according to an embodiment of the present application, see Fig. 27 , the authentication module 2601, comprises:

[0291] A determination unit 2701 is used to determine whether the first user account has been bound to a blockchain identifier based on the real-name authentication information;

[0292] The authentication unit 2702 is used to perform the real-name authentication and the face verification on the first user account based on the real-name authentication information when the first user account is not bound to a blockchain identifier.

[0293] In some embodiments, the first acquisition module 2602 is also used to obtain the target blockchain identifier bound to the first user account when the first user account is bound to a blockchain identifier; return the target blockchain identifier to the target application, and cancel the real-name authentication and face verification of the first user account.

[0294] In some embodiments, see Fig. 27 , the authentication module 2601, comprises:

[0295] A verification unit 2703 is used to verify the ID card number in the real-name authentication information based on the blockchain account management service to obtain a verification result, which is used to indicate whether the ID card number has been registered in the blockchain system;

[0296] The authentication unit 2702 is used to perform the real-name authentication and the face verification on the first user account based on the real-name authentication when the verification result indicates that the identity card number has been registered.

[0297] In some embodiments, the authentication unit 2702 is further configured to perform the real-name authentication and the face verification on the first user account based on the real-name authentication when the verification result indicates that the ID card number is not registered;

[0298] The first acquisition module 2602 is used to send a registration request to the blockchain system in response to the first user account passing the real-name authentication and the face verification, where the registration request is used to instruct the blockchain system to register the blockchain account based on the real-name authentication information; and obtain the target blockchain identifier and the second user account returned by the blockchain system.

[0299] In some embodiments, see Fig. 27 , the device further comprises:

[0300] A request sending module 2604 is used to send an association request to the blockchain system in response to an exchange request for a target digital resource, wherein the exchange request carries the target blockchain identifier and the target resource identifier of the target digital resource, and the association request is used to instruct the blockchain system to associate the target blockchain identifier with the target resource identifier;

[0301] The information return module 2605 is used to return binding information to the target application, where the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

[0302] In some embodiments, see Fig. 27 , the device further comprises:

[0303] The signature image binding module 2606 is used to obtain a signature binding request for a target digital resource, the signature binding request carrying the target signature image of the first user account; and bind the target signature image to the target resource identifier of the target digital resource.

[0304] In some embodiments, see Fig. 27 , the device further comprises:

[0305] The signature image review module 2607 is used to receive the signature review request of the first user account, and review the signature image carried in the signature review request; in response to the signature image passing the review, store the review result of the signature image, and the review result is used to indicate whether the signature image has passed the review; and return the review result to the target application.

[0306] In some embodiments, the public-private key pair of the second user account is the first public-private key pair of the first user account; see Fig. 27 The device also includes: a public-private key pair management module 2608, which is used to send a key generation request for the first user account to the blockchain system, and receive the first public-private key pair returned by the blockchain system; send a key encryption request to the key management server, the key encryption request carries the master key of the application background server, the first user account and the first public-private key pair, and the application background server is used to provide background services for the target application; and store the first encrypted string returned by the key management server in the database.

[0307] In some embodiments, see Fig. 27 The public-private key pair management module 2608 is also used to obtain the first encrypted string from the database; send a key decryption request to the key management server, the key decryption request carries the master key and the first encrypted string; and receive the first public-private key pair returned by the key management server.

[0308] In some embodiments, the public-private key pair of the second user account is the second public-private key pair of the first user account; see Fig. 27 , the device further comprises:

[0309] The public-private key pair management module 2608 is used to send a key generation request for the first user account to the blockchain system, and receive the second public-private key pair returned by the blockchain system; encrypt the second public-private key pair based on the data key of the application background server to obtain a second encrypted string, and the application background server is used to provide background services for the target application; and store the first user account, the second encrypted string, and the ciphertext of the data key corresponding to the data key in the database.

[0310] In some embodiments, see Fig. 27 The public-private key pair management module 2608 is further used to obtain the second encrypted string from the database; decrypt the second encrypted string based on the data key of the application background server to obtain the second public-private key pair.

[0311] In some embodiments, see Fig. 27 The public-private key pair management module 2608 is also used to send a key creation request to the key management server to obtain the master key of the application background server; based on the master key, obtain the data key and the ciphertext of the data key from the key management server; cache the data key, and store the ciphertext of the data key in the database.

[0312] In some embodiments, the public-private key pair of the second user account is the third public-private key pair of the first user account; see Fig. 27 , the device further comprises:

[0313] The public-private key pair management module 2608 is used to send a key generation request for the first user account to the blockchain system, receive the third public-private key pair returned by the blockchain system; encrypt the third public-private key pair based on the key in the configuration file to obtain a third encrypted string; and store the first user account and the third encrypted string in a database.

[0314] In some embodiments, see Fig. 27 The public-private key pair management module 2608 is further used to obtain the third encrypted string from the database; decrypt the third encrypted string based on the key in the configuration file to obtain the third public-private key pair.

[0315] In some embodiments, the public-private key pair of the second user account is the fourth public-private key pair of the first user account; see Fig. 27 , the device further comprises:

[0316] The public-private key pair management module 2608 is used to generate a data key and a ciphertext of the data key for the first user account based on the first user account and the timestamp; send a key generation request for the first user account to the blockchain system, and receive the fourth public-private key pair returned by the blockchain system; encrypt the fourth public-private key pair based on the data key to obtain a fourth encrypted string; and store the first user account, the fourth encrypted string, and the ciphertext of the data key in a database.

[0317] In some embodiments, see Fig. 27 The public-private key pair management module 2608 is also used to obtain the fourth encrypted string and the ciphertext of the data key from the database based on the first user account; obtain the data key based on the ciphertext of the data key; and decrypt the fourth encrypted string based on the data key to obtain the fourth public-private key pair.

[0318] The embodiment of the present application provides a solution for account authentication, which can perform real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account in the target application, and then after passing the above authentication, obtain the public-private key pair of the second user account based on the blockchain system, encrypt the second user account to obtain the target blockchain identifier, so that the target blockchain identifier can represent the second user account, and finally, by binding the first user account and the target blockchain identifier, the first user account can be securely authenticated.

[0319] It should be noted that: the account authentication device provided in the above embodiment only uses the division of the above functional modules as an example when performing account authentication. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the account authentication device provided in the above embodiment and the account authentication method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0320] Fig.28 is a block diagram of a digital resource exchange device provided according to an embodiment of the present application. The device is used to execute the steps in the above-mentioned digital resource exchange method, see Fig.28 The device includes: a display module 2801, an acquisition module 2802 and a request sending module 2803.

[0321] Display module 2801, used to display a resource exchange page of a target application, where the resource exchange page displays at least one digital resource provided by the blockchain system;

[0322] An acquisition module 2802 is used to obtain, in response to an exchange operation on any digital resource, a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is encrypted by using a public-private key pair of a second user account in the blockchain system;

[0323] The request sending module 2803 is used to send an exchange request to the server, where the exchange request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier.

[0324] In some embodiments, Fig.29 is a block diagram of another digital resource exchange device provided according to an embodiment of the present application, see Fig.29 As shown, the acquisition module 2802 includes:

[0325] The acquisition unit 2901 is used to obtain a target resource identifier of the digital resource in response to an exchange operation on any digital resource, and send a binding information query request to the server, where the binding information query request is used to request a blockchain identifier bound to the first user account;

[0326] The authentication unit 2902 is configured to, in response to the first user account not being bound to a blockchain identifier, request the server to perform real-name authentication and face verification on the first user account logged into the target application based on the real-name authentication information of the first user account;

[0327] The acquisition unit 2901 is also used to obtain the target blockchain identifier returned by the server in response to the first user account passing the real-name authentication and the face verification.

[0328] In some embodiments, see Fig.29 As shown, the authentication unit 2902 is used to send a blockchain account query request to the server based on the real-name authentication information of the first user account in response to the first user account not being bound to the blockchain identifier, and the blockchain account query request is used to query whether there is a blockchain account corresponding to the real-name authentication information in the blockchain system; in response to the absence of a blockchain account corresponding to the real-name authentication information, request the server to perform real-name authentication and face verification on the first user account for logging in to the target application.

[0329] In some embodiments, the display module 2801 is further used to display a resource display page, where the resource display page is used to display at least one digital resource that has been redeemed by the first user account;

[0330] The display module 2801 is further used to display a signature selection page in response to a signature operation on any digital resource in the resource display page, and the signature selection page is used to select a signature image;

[0331] The request sending module 2803 is also used to send a signature binding request to the server in response to a selection operation on any signature image, and the signature binding request is used to instruct the server to bind the selected target signature image with the digital resource.

[0332] In some embodiments, see Fig.29 As shown, the device also includes:

[0333] The display module 2801 is also used to display a signature creation page, where the signature creation page is used to create a signature image;

[0334] The request sending module 2803 is further used to send a signature review request to the server in response to a signature image creation operation based on the signature creation page, wherein the signature review request carries the signature image created by the signature image creation operation;

[0335] The receiving module 2804 is used to receive the review result returned by the server based on the signature review request, and the review result is used to indicate whether the signature image has passed the review.

[0336] In some embodiments, see Fig.29 As shown, the device also includes:

[0337] The resource donation module 2805 is used to display a resource donation page in response to a donation operation on any digital resource in the resource display page;

[0338] The request sending module 2803 is also used to send a digital resource transfer request to the blockchain system in response to the donation blockchain identifier input based on the resource donation page, and the digital resource transfer request is used to instruct the blockchain system to bind the digital resource identifier of the digital resource with the donation blockchain identifier.

[0339] In some embodiments, the blockchain system stores a resource series identifier to which the digital resource identifier of the digital resource belongs; the digital resource transfer request is used to instruct the blockchain system to bind the resource series identifier with the donation blockchain identifier.

[0340] An embodiment of the present application provides a method for exchanging digital resources. When exchanging digital resources on a resource exchange page based on a target application, a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in to the target application are obtained, and a server is requested to establish a binding relationship between the target blockchain identifier and the target resource identifier, so that the first user account can indirectly associate the digital resources in the blockchain system through the target blockchain identifier to realize the exchange of digital resources, thereby ensuring that the process of the first user account in obtaining digital assets is safe and reliable.

[0341] It should be noted that: the digital resource exchange device provided in the above embodiment only uses the division of the above functional modules as an example when exchanging digital resources. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the digital resource exchange device and the digital resource exchange method embodiment provided in the above embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0342] In the embodiments of the present application, the computer device can be configured as a terminal or a server. When the computer device is configured as a terminal, the terminal can be used as the execution subject to implement the technical solution provided in the embodiments of the present application. When the computer device is configured as a server, the server can be used as the execution subject to implement the technical solution provided in the embodiments of the present application. The technical solution provided in the present application can also be implemented through interaction between the terminal and the server. The embodiments of the present application are not limited to this.

[0343] When a computer device is configured as a terminal, Fig.30 It is a structural block diagram of a terminal 3000 provided according to an embodiment of the present application.

[0344] Typically, the terminal 3000 includes: a processor 3001 and a memory 3002 .

[0345] The processor 3001 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 3001 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 3001 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 3001 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 3001 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0346] The memory 3002 may include one or more computer-readable storage media, which may be non-transitory. The memory 3002 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 3002 is used to store at least one computer program, which is used to be executed by the processor 3001 to implement the method for exchanging digital resources provided in the method embodiment of the present application.

[0347] In some embodiments, the terminal 3000 may further optionally include: a peripheral device interface 3003 and at least one peripheral device. The processor 3001, the memory 3002 and the peripheral device interface 3003 may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface 3003 via a bus, a signal line or a circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 3004, a display screen 3005, a camera assembly 3006, an audio circuit 3007 and a power supply 3008.

[0348] The peripheral device interface 3003 may be used to connect at least one peripheral device related to I / O (Input / Output) to the processor 3001 and the memory 3002. In some embodiments, the processor 3001, the memory 3002, and the peripheral device interface 3003 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 3001, the memory 3002, and the peripheral device interface 3003 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

[0349] The radio frequency circuit 3004 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 3004 communicates with the communication network and other communication devices through electromagnetic signals. The radio frequency circuit 3004 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals into electrical signals. In some embodiments, the radio frequency circuit 3004 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, and the like. The radio frequency circuit 3004 can communicate with other terminals through at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks (2G, 3G, 4G and 5G), a wireless local area network and / or a WiFi (Wireless Fidelity) network. In some embodiments, the radio frequency circuit 3004 may also include circuits related to NFC (Near Field Communication), which is not limited in this application.

[0350] The display screen 3005 is used to display a UI (User Interface). The UI may include graphics, text, icons, videos, and any combination thereof. When the display screen 3005 is a touch display screen, the display screen 3005 also has the ability to collect touch signals on the surface or above the surface of the display screen 3005. The touch signal can be input to the processor 3001 as a control signal for processing. At this time, the display screen 3005 can also be used to provide virtual buttons and / or virtual keyboards, also known as soft buttons and / or soft keyboards. In some embodiments, the display screen 3005 can be one, set on the front panel of the terminal 3000; in other embodiments, the display screen 3005 can be at least two, respectively set on different surfaces of the terminal 3000 or in a folding design; in other embodiments, the display screen 3005 can be a flexible display screen, set on a curved surface or a folding surface of the terminal 3000. Even, the display screen 3005 can also be set to a non-rectangular irregular figure, that is, a special-shaped screen. The display screen 3005 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0351] The camera assembly 3006 is used to capture images or videos. In some embodiments, the camera assembly 3006 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal, and the rear camera is disposed on the back of the terminal. In some embodiments, there are at least two rear cameras, which are any one of a main camera, a depth of field camera, a wide-angle camera, and a telephoto camera, so as to realize the fusion of the main camera and the depth of field camera to realize the background blur function, the fusion of the main camera and the wide-angle camera to realize the panoramic shooting and VR (Virtual Reality) shooting function or other fusion shooting functions. In some embodiments, the camera assembly 3006 may also include a flash. The flash may be a monochrome temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cold light flash, which can be used for light compensation at different color temperatures.

[0352] The audio circuit 3007 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals and input them into the processor 3001 for processing, or input them into the radio frequency circuit 3004 to achieve voice communication. For the purpose of stereo acquisition or noise reduction, there may be multiple microphones, which are respectively arranged at different parts of the terminal 3000. The microphone may also be an array microphone or an omnidirectional acquisition microphone. The speaker is used to convert the electrical signal from the processor 3001 or the radio frequency circuit 3004 into sound waves. The speaker may be a traditional film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can not only convert the electrical signal into sound waves audible to humans, but also convert the electrical signal into sound waves inaudible to humans for purposes such as ranging. In some embodiments, the audio circuit 3007 may also include a headphone jack.

[0353] The power supply 3008 is used to power various components in the terminal 3000. The power supply 3008 can be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power supply 3008 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery charged through a wired line, and a wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0354] In some embodiments, the terminal 3000 further includes one or more sensors 3009 . The one or more sensors 3009 include, but are not limited to: an acceleration sensor 3010 , a gyroscope sensor 3011 , a pressure sensor 3012 , an optical sensor 3013 , and a proximity sensor 3014 .

[0355] The acceleration sensor 3010 can detect the magnitude of acceleration on the three coordinate axes of the coordinate system established by the terminal 3000. For example, the acceleration sensor 3010 can be used to detect the components of gravity acceleration on the three coordinate axes. The processor 3001 can control the display screen 3005 to display the user interface in a horizontal view or a vertical view according to the gravity acceleration signal collected by the acceleration sensor 3010. The acceleration sensor 3010 can also be used for collecting game or user motion data.

[0356] The gyro sensor 3011 can detect the body direction and rotation angle of the terminal 3000, and the gyro sensor 3011 can cooperate with the acceleration sensor 3011 to collect the user's 3D actions on the terminal 3000. The processor 3001 can implement the following functions based on the data collected by the gyro sensor 3011: motion sensing (such as changing the UI according to the user's tilt operation), image stabilization during shooting, game control, and inertial navigation.

[0357] The pressure sensor 3012 can be set on the side frame of the terminal 3000 and / or the lower layer of the display screen 3005. When the pressure sensor 3012 is set on the side frame of the terminal 3000, it can detect the user's holding signal of the terminal 3000, and the processor 3001 performs left and right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 3012. When the pressure sensor 3012 is set on the lower layer of the display screen 3005, the processor 3001 controls the operability controls on the UI interface according to the user's pressure operation on the display screen 3005. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

[0358] The optical sensor 3013 is used to collect the ambient light intensity. In one embodiment, the processor 3001 can control the display brightness of the display screen 3005 according to the ambient light intensity collected by the optical sensor 3013. Specifically, when the ambient light intensity is high, the display brightness of the display screen 3005 is increased; when the ambient light intensity is low, the display brightness of the display screen 3005 is reduced. In another embodiment, the processor 3001 can also dynamically adjust the shooting parameters of the camera assembly 3006 according to the ambient light intensity collected by the optical sensor 3013.

[0359] The proximity sensor 3014, also called a distance sensor, is usually arranged on the front panel of the terminal 3000. The proximity sensor 3014 is used to collect the distance between the user and the front of the terminal 3000. In one embodiment, when the proximity sensor 3014 detects that the distance between the user and the front of the terminal 3000 is gradually decreasing, the processor 3001 controls the display screen 3005 to switch from the screen-on state to the screen-off state; when the proximity sensor 3014 detects that the distance between the user and the front of the terminal 3000 is gradually increasing, the processor 3001 controls the display screen 3005 to switch from the screen-off state to the screen-on state.

[0360] Those skilled in the art will understand that Fig.30 The structure shown in the figure does not constitute a limitation on the terminal 3000, and the terminal 3000 may include more or fewer components than those shown in the figure, or combine certain components, or adopt a different component arrangement.

[0361] When a computer device is configured as a server, Fig.31It is a structural diagram of a server provided according to an embodiment of the present application. The server 3100 may have relatively large differences due to different configurations or performances, and may include one or more processors (Central Processing Units, CPU) 3101 and one or more memories 3102, wherein the memory 3102 stores at least one computer program, and the at least one computer program is loaded and executed by the processor 3101 to implement the account authentication method provided by the above-mentioned various method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output, and the server may also include other components for implementing device functions, which will not be repeated here.

[0362] The embodiment of the present application also provides a computer-readable storage medium, in which at least one computer program is stored, and the at least one computer program is loaded and executed by a processor of a computer device to implement the operation performed by the computer device in the solution of the above embodiment. For example, the computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, etc.

[0363] An embodiment of the present application also provides a computer program, which, when executed by a processor, implements the account authentication method provided in the above-mentioned various optional implementations, or, when executed by a processor, implements the digital resource redemption method provided in the above-mentioned various optional implementations.

[0364] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0365] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. An account authentication method, characterized in that: The method comprises: Based on the real-name authentication information of the first user account logged in by the target application, perform real-name authentication and face verification on the first user account; In response to the first user account passing the real-name authentication and the face verification, obtaining a target blockchain identifier, where the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system; Establishing a binding relationship between the first user account and the target blockchain identifier; The method further comprises: In response to a redemption request for a target digital resource, sending an association request to the blockchain system, the redemption request carrying the target blockchain identifier and the target resource identifier of the target digital resource, the association request being used to instruct the blockchain system to associate the target blockchain identifier with the target resource identifier; Return binding information to the target application, where the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

2. The method according to claim 1, characterized in that: The performing real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account logged in by the target application includes: Based on the real-name authentication information, determining whether the first user account has been bound to a blockchain identifier; When the first user account is not bound to a blockchain identifier, the real-name authentication and the face verification are performed on the first user account based on the real-name authentication information.

3. The method according to claim 2, characterized in that The method further comprises: If the first user account has been bound to a blockchain identifier, obtaining a target blockchain identifier to which the first user account has been bound; The target blockchain identifier is returned to the target application, and the real-name authentication and the face verification for the first user account are canceled.

4. The method according to claim 1, characterized in that: The performing real-name authentication and face verification on the first user account based on the real-name authentication information of the first user account logged in by the target application includes: Based on the blockchain account management service, verify the ID card number in the real-name authentication information to obtain a verification result, wherein the verification result is used to indicate whether the ID card number has been registered in the blockchain system; When the verification result indicates that the ID number has been registered, the real-name authentication and the face verification are performed on the first user account based on the real-name authentication information.

5. The method according to claim 4, characterized in that The method further comprises: If the verification result indicates that the ID card number is not registered, performing the real-name authentication and the face verification on the first user account based on the real-name authentication information; The step of obtaining a target blockchain identifier in response to the first user account passing the real-name authentication and the face verification includes: In response to the first user account passing the real-name authentication and the face verification, sending a registration request to the blockchain system, wherein the registration request is used to instruct the blockchain system to register a blockchain account based on the real-name authentication information; Obtain the target blockchain identifier and the second user account returned by the blockchain system.

6. The method according to claim 1, characterized in that The method further comprises: Obtaining a signature binding request for the target digital resource, wherein the signature binding request carries a target signature image of the first user account; The target signature image is bound to the target resource identifier of the target digital resource.

7. The method according to claim 1, characterized in that The method further comprises: receiving a signature review request from the first user account, and reviewing the signature image carried in the signature review request; In response to the signature image passing the review, storing the review result of the signature image, wherein the review result is used to indicate whether the signature image has passed the review; The audit result is returned to the target application.

8. The method according to claim 1, characterized in that The public-private key pair of the second user account is the first public-private key pair of the first user account; the method further includes: Sending a key generation request for the first user account to the blockchain system, and receiving the first public-private key pair returned by the blockchain system; Sending a key encryption request to a key management server, the key encryption request carrying a master key of an application background server, the first user account, and the first public-private key pair, the application background server being used to provide background services for the target application; The first encrypted string returned by the key management server is stored in the database.

9. The method according to claim 8, characterized in that The method further comprises: Acquire the first encrypted string from the database; Sending a key decryption request to the key management server, wherein the key decryption request carries the master key and the first encrypted string; Receive the first public-private key pair returned by the key management server.

10. The method according to claim 1, characterized in that The public-private key pair of the second user account is a second public-private key pair of the first user account; the method further includes: Sending a key generation request for the first user account to the blockchain system, and receiving the second public-private key pair returned by the blockchain system; Encrypting the second public-private key pair based on a data key of an application background server to obtain a second encrypted string, wherein the application background server is used to provide background services for the target application; The ciphertext of the first user account, the second encrypted string and the data key is stored in a database.

11. The method according to claim 10, characterized in that The method further comprises: Acquire the second encrypted string from the database; The second encrypted string is decrypted based on the data key of the application background server to obtain the second public-private key pair.

12. The method according to claim 10, characterized in that The method further comprises: Send a key creation request to the key management server to obtain the master key of the application background server; Based on the master key, obtaining the data key and the ciphertext of the data key from the key management server; The data key is cached, and the ciphertext of the data key is stored in the database.

13. The method according to claim 1, characterized in that The public-private key pair of the second user account is a third public-private key pair of the first user account; and the method further includes: Sending a key generation request for the first user account to the blockchain system, and receiving the third public-private key pair returned by the blockchain system; Encrypting the third public-private key pair based on the key in the configuration file to obtain a third encrypted string; The first user account and the third encrypted string are stored in a database.

14. The method according to claim 13, characterized in that The method further comprises: Acquire the third encrypted string from the database; The third encrypted string is decrypted based on the key in the configuration file to obtain the third public-private key pair.

15. The method according to claim 1, characterized in that The public-private key pair of the second user account is a fourth public-private key pair of the first user account; the method further includes: Based on the first user account and the timestamp, generate a data key and a ciphertext of the data key for the first user account; Sending a key generation request for the first user account to the blockchain system, and receiving the fourth public-private key pair returned by the blockchain system; Encrypting the fourth public-private key pair based on the data key to obtain a fourth encrypted string; The ciphertext of the first user account, the fourth encrypted string and the data key is stored in a database.

16. The method according to claim 15, characterized in that The method further comprises: Based on the first user account, obtaining the ciphertext of the fourth encrypted string and the data key from the database; Based on the ciphertext of the data key, obtaining the data key; The fourth encrypted string is decrypted based on the data key to obtain the fourth public-private key pair.

17. A method for exchanging digital resources, characterized in that: The method comprises: Displaying a resource exchange page of the target application, wherein the resource exchange page displays at least one digital resource provided by the blockchain system; In response to an exchange operation for any digital resource, obtaining a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system; A redemption request is sent to a server, so that the server responds to the redemption request, sends an association request to the blockchain system, and returns binding information to the target application; the redemption request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier, the redemption request carries the target blockchain identifier and the target resource identifier, the association request is used to instruct the blockchain system to associate the target blockchain identifier and the target resource identifier, and the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

18. The method according to claim 17, characterized in that The step of obtaining, in response to an exchange operation on any digital resource, a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application includes: In response to an exchange operation for any digital resource, obtaining a target resource identifier of the digital resource, and sending a binding information query request to the server, wherein the binding information query request is used to request a blockchain identifier bound to the first user account; In response to the first user account not being bound to a blockchain identifier, based on the real-name authentication information of the first user account, requesting the server to perform real-name authentication and face verification on the first user account logged into the target application; In response to the first user account passing the real-name authentication and the face verification, obtaining the target blockchain identifier returned by the server.

19. The method according to claim 18, characterized in that The requesting the server to perform real-name authentication and face verification on the first user account for logging into the target application based on the real-name authentication information of the first user account includes: In response to the first user account not being bound to a blockchain identifier, based on the real-name authentication information of the first user account, sending a blockchain account query request to the server, wherein the blockchain account query request is used to query whether the blockchain system has a blockchain account corresponding to the real-name authentication information; In response to the absence of a blockchain account corresponding to the real-name authentication information, requesting the server to perform real-name authentication and face verification on the first user account logged in to the target application.

20. The method according to claim 17, characterized in that The method further comprises: Displaying a resource display page, wherein the resource display page is used to display at least one digital resource that has been redeemed by the first user account; In response to a signature operation on any digital resource in the resource display page, displaying a signature selection page, the signature selection page being used to select a signature image; In response to a selection operation on any signature image, a signature binding request is sent to the server, wherein the signature binding request is used to instruct the server to bind the selected target signature image with the digital resource.

21. The method according to claim 20, characterized in that The method further comprises: In response to a donation operation on any digital resource in the resource display page, displaying a resource donation page; In response to the donation blockchain identifier input based on the resource donation page, a digital resource transfer request is sent to the blockchain system, and the digital resource transfer request is used to instruct the blockchain system to bind the digital resource identifier of the digital resource with the donation blockchain identifier.

22. The method according to claim 17, characterized in that The method further comprises: Displaying a signature creation page, wherein the signature creation page is used to create a signature image; In response to a signature image creation operation based on the signature creation page, sending a signature review request to the server, wherein the signature review request carries the signature image created by the signature image creation operation; Receive a review result returned by the server based on the signature review request, where the review result is used to indicate whether the signature image has passed the review.

23. The method according to claim 21, characterized in that The blockchain system stores a resource series identifier to which the digital resource identifier of the digital resource belongs; The digital resource transfer request is used to instruct the blockchain system to bind the resource series identifier and the donation blockchain identifier.

24. A digital resource exchange system, characterized in that: The digital resource exchange system includes a terminal and a server; The terminal is used to display a resource exchange page of the target application, and the resource exchange page displays at least one digital resource provided by the blockchain system; The server is used to store the binding relationship between the first user account logged in by the target application and the target blockchain identifier; The terminal is further used to, in response to an exchange operation for any digital resource, obtain a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system; The terminal is further used to send an exchange request to the server, wherein the exchange request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier, and the exchange request carries the target blockchain identifier and the target resource identifier; The server is further configured to send an association request to the blockchain system in response to the exchange request, wherein the association request is used to instruct the blockchain system to associate the target blockchain identifier with the target resource identifier; The server is also used to establish a binding relationship between the target blockchain identifier and the target resource identifier, and return binding information to the target application, wherein the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

25. An account authentication device, characterized in that: The device comprises: An authentication module, configured to perform real-name authentication and face verification on a first user account logged in by a target application based on the real-name authentication information of the first user account; A first acquisition module is configured to acquire a target blockchain identifier in response to the first user account passing the real-name authentication and the face verification, where the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system; A relationship establishment module, used to establish a binding relationship between the first user account and the target blockchain identifier; The device also includes: A request sending module, configured to send an association request to the blockchain system in response to an exchange request for a target digital resource, wherein the exchange request carries the target blockchain identifier and the target resource identifier of the target digital resource, and the association request is used to instruct the blockchain system to associate the target blockchain identifier with the target resource identifier; An information return module is used to return binding information to the target application, wherein the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

26. The device according to claim 25, characterized in that The authentication module comprises: A determination unit, configured to determine whether the first user account has been bound to a blockchain identifier based on the real-name authentication information; An authentication unit is used to perform the real-name authentication and the face verification on the first user account based on the real-name authentication information when the first user account is not bound to a blockchain identifier.

27. The device according to claim 26, characterized in that The first acquisition module is further used to obtain the target blockchain identifier to which the first user account is bound when the first user account is bound to a blockchain identifier; return the target blockchain identifier to the target application, and cancel the real-name authentication and face verification for the first user account.

28. The device according to claim 25, characterized in that The authentication module comprises: A verification unit, used to verify the identity card number in the real-name authentication information based on the blockchain account management service to obtain a verification result, wherein the verification result is used to indicate whether the identity card number has been registered in the blockchain system; An authentication unit is used to perform the real-name authentication and the face verification on the first user account based on the real-name authentication information when the verification result indicates that the identity card number has been registered.

29. The device according to claim 28, characterized in that The authentication unit is further configured to perform the real-name authentication and the face verification on the first user account based on the real-name authentication information when the verification result indicates that the identity card number is not registered; The first acquisition module is used to send a registration request to the blockchain system in response to the first user account passing the real-name authentication and the face verification, wherein the registration request is used to instruct the blockchain system to register a blockchain account based on the real-name authentication information; and obtain the target blockchain identifier and the second user account returned by the blockchain system.

30. The device according to claim 25, characterized in that The device also includes: The signature image binding module is used to obtain a signature binding request for the target digital resource, wherein the signature binding request carries the target signature image of the first user account; and bind the target signature image to the target resource identifier of the target digital resource.

31. The device according to claim 25, characterized in that The device also includes: A signature image review module is used to receive a signature review request from the first user account, and review the signature image carried in the signature review request; in response to the signature image passing the review, store the review result of the signature image, and the review result is used to indicate whether the signature image has passed the review; and return the review result to the target application.

32. The device according to claim 25, characterized in that The public-private key pair of the second user account is the first public-private key pair of the first user account; the device further includes: A first request module, configured to send a key generation request for the first user account to the blockchain system, and receive the first public-private key pair returned by the blockchain system; A first encryption module is used to send a key encryption request to a key management server, wherein the key encryption request carries a master key of an application background server, the first user account, and the first public-private key pair, and the application background server is used to provide background services for the target application; The first storage module is used to store the first encrypted string returned by the key management server in a database.

33. The device according to claim 32, characterized in that The device also includes: A second acquisition module, used to acquire the first encrypted string from the database; A first decryption module, configured to send a key decryption request to the key management server, wherein the key decryption request carries the master key and the first encrypted string; The first receiving module is used to receive the first public-private key pair returned by the key management server.

34. The device according to claim 25, characterized in that The public-private key pair of the second user account is a second public-private key pair of the first user account; the device further includes: A second request module, configured to send a key generation request for the first user account to the blockchain system, and receive the second public-private key pair returned by the blockchain system; A second encryption module, used to encrypt the second public-private key pair based on a data key of an application background server to obtain a second encrypted string, wherein the application background server is used to provide background services for the target application; The second storage module is used to store the ciphertext of the first user account, the second encryption string and the data key in a database.

35. The device according to claim 34, characterized in that The device also includes: A third acquisition module, used to acquire the second encrypted string from the database; The second decryption module is used to decrypt the second encrypted string based on the data key of the application background server to obtain the second public-private key pair.

36. The device according to claim 34, characterized in that The second request module is further used to send a key creation request to the key management server to obtain the master key of the application background server; A third acquisition module, configured to acquire the data key and the ciphertext of the data key from the key management server based on the master key; The second storage module is further used to cache the data key and store the ciphertext of the data key in the database.

37. The device according to claim 25, characterized in that The public-private key pair of the second user account is a third public-private key pair of the first user account; the device further includes: A third request module, configured to send a key generation request for the first user account to the blockchain system, and receive the third public-private key pair returned by the blockchain system; A third encryption module, used to encrypt the third public-private key pair based on the key in the configuration file to obtain a third encrypted string; The third storage module is used to store the first user account and the third encrypted string in a database.

38. The device according to claim 37, characterized in that The device also includes: A fourth acquisition module, used to acquire the third encrypted string from the database; The third decryption module is used to decrypt the third encrypted string based on the key in the configuration file to obtain the third public-private key pair.

39. The device according to claim 25, characterized in that The public-private key pair of the second user account is a fourth public-private key pair of the first user account; and the device further includes: A generating module, configured to generate a data key and a ciphertext of the data key of the first user account based on the first user account and the timestamp; a fourth request module, configured to send a key generation request for the first user account to the blockchain system, and receive the fourth public-private key pair returned by the blockchain system; a fourth encryption module, used to encrypt the fourth public-private key pair based on the data key to obtain a fourth encrypted string; The fourth storage module is used to store the ciphertext of the first user account, the fourth encryption string and the data key in a database.

40. The device according to claim 39, characterized in that The device also includes: a fifth acquisition module, configured to acquire, from the database based on the first user account, the ciphertext of the fourth encrypted string and the data key; The fifth acquisition module is further used to acquire the data key based on the ciphertext of the data key; The fourth decryption module is used to decrypt the fourth encrypted string based on the data key to obtain the fourth public-private key pair.

41. A digital resource exchange device, characterized in that: The device comprises: A display module, used to display a resource exchange page of the target application, wherein the resource exchange page displays at least one digital resource provided by the blockchain system; an acquisition module, configured to, in response to an exchange operation on any digital resource, acquire a target resource identifier of the digital resource and a target blockchain identifier bound to a first user account logged in by the target application, wherein the target blockchain identifier is obtained by encrypting the second user account based on a public-private key pair of the second user account in the blockchain system; A request sending module, used to send an exchange request to a server, so that the server responds to the exchange request, sends an association request to the blockchain system and returns binding information to the target application; the exchange request is used to instruct the server to establish a binding relationship between the target blockchain identifier and the target resource identifier, the exchange request carries the target blockchain identifier and the target resource identifier, the association request is used to instruct the blockchain system to associate the target blockchain identifier and the target resource identifier, and the binding information is used to indicate that the target blockchain identifier has been bound to the target resource identifier.

42. The device according to claim 41, characterized in that The acquisition module comprises: an acquisition unit, configured to, in response to an exchange operation on any digital resource, acquire a target resource identifier of the digital resource, and send a binding information query request to the server, wherein the binding information query request is used to request a query of a blockchain identifier bound to the first user account; an authentication unit, configured to, in response to the first user account not being bound to a blockchain identifier, request the server to perform real-name authentication and face verification on the first user account logged into the target application based on the real-name authentication information of the first user account; The acquisition unit is further used to obtain the target blockchain identifier returned by the server in response to the first user account passing the real-name authentication and the face verification.

43. The device according to claim 42, characterized in that The authentication unit is configured to, in response to the first user account not being bound to a blockchain identifier, send a blockchain account query request to the server based on the real-name authentication information of the first user account, wherein the blockchain account query request is used to query whether the blockchain system has a blockchain account corresponding to the real-name authentication information; In response to the absence of a blockchain account corresponding to the real-name authentication information, requesting the server to perform real-name authentication and face verification on the first user account logged in to the target application.

44. The device according to claim 41, characterized in that The device also includes: The display module is further used to display a resource display page, wherein the resource display page is used to display at least one digital resource that has been redeemed by the first user account; The display module is further used to display a signature selection page in response to a signature operation on any digital resource in the resource display page, wherein the signature selection page is used to select a signature image; The request sending module is further used to send a signature binding request to the server in response to a selection operation on any signature image, wherein the signature binding request is used to instruct the server to bind the selected target signature image with the digital resource.

45. The device according to claim 44, characterized in that The device also includes: A resource donation module, configured to display a resource donation page in response to a donation operation on any digital resource in the resource display page; The request sending module is also used to send a digital resource transfer request to the blockchain system in response to the donation blockchain identifier input based on the resource donation page, and the digital resource transfer request is used to instruct the blockchain system to bind the digital resource identifier of the digital resource with the donation blockchain identifier.

46. ​​The device according to claim 41, characterized in that The device also includes: The display module is further used to display a signature creation page, and the signature creation page is used to create a signature image; The request sending module is further used to send a signature review request to the server in response to a signature image creation operation based on the signature creation page, wherein the signature review request carries the signature image created by the signature image creation operation; The receiving module is used to receive the review result returned by the server based on the signature review request, and the review result is used to indicate whether the signature image has passed the review.

47. The device according to claim 45, characterized in that The blockchain system stores a resource series identifier to which the digital resource identifier of the digital resource belongs; The digital resource transfer request is used to instruct the blockchain system to bind the resource series identifier and the donation blockchain identifier.

48. A computer device, characterized in that: The computer device includes a processor and a memory, the memory is used to store at least one computer program, the at least one computer program is loaded by the processor and executes the account authentication method described in any one of claims 1 to 16, or the at least one computer program is loaded by the processor and executes the digital resource redemption method described in any one of claims 17 to 23.

49. A computer-readable storage medium, characterized in that The computer-readable storage medium is used to store at least one computer program, and the at least one computer program is used to execute the account authentication method described in any one of claims 1 to 16, or the at least one computer program is used to execute the digital resource redemption method described in any one of claims 17 to 23.

50. A computer program product comprising a computer program, characterized in that When the computer program is executed by the processor, it implements the account authentication method as described in any one of claims 1 to 16, or, when the computer program is executed by the processor, it implements the digital resource exchange method as described in any one of claims 17 to 23.

Images