Data processing method and device based on block chain and readable storage medium

Abstract

The embodiment of the invention provides a data processing method and device based on a block chain and a readable storage medium. The method comprises the steps of obtaining receiving account information corresponding to a resource transfer event in a resource client; the receiving account information comprises a receiving block chain address of the receiving object and a receiving account system name of the to-be-verified object; the receiving account system name comprises a receiving system prefix and a receiving system suffix; the receiving system suffix is used for representing a receiving service organization to which the object to be verified belongs, and the receiving system prefix is used for representing the object to be verified in the receiving service organization; obtaining a verification result aiming at the receiving block chain address and the receiving account system name; the verification result is obtained by verifying the receiving block chain address and the receiving account system name; and if the verification result indicates that the to-be-verified object is the same as the receiving object, generating transaction data for the resource transfer event, and sending the transaction data to a block chain node in the block chain. The security of the digital assets can be improved.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a data processing method, device, and readable storage medium based on blockchain. Background Art

[0002] As digital assets gain more and more consensus, more and more objects will implement digital asset resource transfer events through resource clients. Existing resource transfer events can obtain the receiving blockchain address of the receiving object, and transfer the digital assets of the sending object to the receiving object through the receiving blockchain address.

[0003] However, the existing resource transfer event cannot verify the received blockchain address. If the received blockchain address is wrong (for example, input error), the digital asset may be transferred to the wrong recipient. For example, the resource transfer event hopes to transfer the digital asset to recipient 1, but because the receiving blockchain address of recipient 1 and the receiving blockchain address of recipient 2 are very similar, the receiving blockchain address of recipient 2 may be obtained by mistake, thereby transferring the digital asset of the sender to recipient 2. Therefore, the existing resource transfer event may cause errors in resource transfer, thereby reducing the security of digital assets. Summary of the invention

[0004] The embodiments of the present application provide a blockchain-based data processing method, device, and readable storage medium, which can improve the security of digital assets.

[0005] On the one hand, an embodiment of the present application provides a data processing method based on blockchain, including:

[0006] Obtain the receiving account information corresponding to the resource transfer event in the resource client; the resource transfer event is used to instruct the sending object corresponding to the resource client to transfer the digital assets to the receiving object; the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified; the receiving account system name includes the receiving system prefix and the receiving system suffix; the receiving system suffix is ​​used to indicate the receiving business organization to which the object to be verified belongs, and the receiving system prefix is ​​used to indicate the object to be verified in the receiving business organization;

[0007] Obtaining the verification result for the receiving blockchain address and the receiving account system name; the verification result is obtained by verifying the receiving blockchain address and the receiving account system name;

[0008] If the verification result indicates that the object to be verified is the same as the receiving object, transaction data for the resource transfer event is generated and sent to the blockchain node in the blockchain so that the blockchain node processes the transaction data on the chain.

[0009] On the one hand, an embodiment of the present application provides a data processing device based on blockchain, including:

[0010] An information acquisition module is used to obtain the receiving account information corresponding to the resource transfer event in the resource client; the resource transfer event is used to instruct the sending object corresponding to the resource client to transfer the digital assets to the receiving object; the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified; the receiving account system name includes a system prefix and a system suffix; the system suffix is ​​used to indicate the business organization to which the object to be verified belongs, and the system prefix is ​​used to indicate the object to be verified in the business organization;

[0011] An information verification module is used to obtain a verification result for a receiving blockchain address and a receiving account system name; the verification result is obtained by verifying the receiving blockchain address and the receiving account system name;

[0012] The resource transfer module is used to generate transaction data for the resource transfer event if the verification result indicates that the object to be verified is the same as the receiving object, and send the transaction data to the blockchain node in the blockchain so that the blockchain node can process the transaction data on the chain.

[0013] Among them, the information verification module is specifically used to send the received blockchain address to the resource server corresponding to the resource client; the resource server is used to obtain the query account system name corresponding to the received blockchain address from the resource database;

[0014] The information verification module is specifically used to receive the query account system name returned by the resource server, compare the query account system name with the received account system name, and if the query account system name and the received account system name are the same, generate a verification result indicating that the object to be verified is the same as the received object;

[0015] The information verification module is specifically used to generate a verification result for indicating that the object to be verified is different from the receiving object if the query account system name and the receiving account system name are different.

[0016] The resource client includes the sending account information of the sending object;

[0017] The device also includes:

[0018] An account generation module is used to generate a sending blockchain account corresponding to the sending object in the resource client;

[0019] An account generation module is used to obtain a sending blockchain address corresponding to a sending blockchain account and a sending account system name corresponding to the sending blockchain account; the sending account system name includes a sending system prefix and a sending system suffix; the sending system suffix is ​​used to indicate the sending business organization to which the sending object belongs, and the sending system prefix is ​​used to indicate the sending object in the sending business organization;

[0020] The information determination module is used to determine the sending blockchain address and the sending account system name as the sending account information; the sending account information has the function of providing the sending object with the function of initiating a resource transfer event.

[0021] Wherein, the sending blockchain account includes the blockchain public key associated with the sending object;

[0022] The account generation module is specifically used to encode the blockchain public key and generate the sending blockchain address corresponding to the sending blockchain account;

[0023] The account generation module is specifically used to obtain the candidate account system name input by the sending object, authenticate the sending object and the candidate account system name, and obtain the authentication result;

[0024] The account generation module is specifically used to determine the candidate account system name as the sending account system name corresponding to the sending blockchain account if the authentication result indicates that the authentication is successful.

[0025] The account generation module is specifically used to obtain the candidate account system name input by the sending object; the candidate account system name includes a candidate system prefix and a candidate system suffix;

[0026] An account generation module, specifically used to perform a first authentication on a sending object and a candidate system suffix, and if the sending object belongs to a candidate business organization represented by the candidate system suffix, generate a first authentication result for indicating a successful authentication, and if the sending object does not belong to the candidate business organization represented by the candidate system suffix, generate a first authentication result for indicating a failed authentication;

[0027] An account generation module is specifically used to perform a second authentication on the candidate system prefix, and if the candidate business organization represented by the candidate system suffix does not include the account system name whose system prefix is ​​the candidate system prefix, a second authentication result is generated to indicate a successful authentication, and if the candidate business organization represented by the candidate system suffix includes the account system name whose system prefix is ​​the candidate system prefix, a second authentication result is generated to indicate a failed authentication;

[0028] The account generation module is specifically used to generate an authentication result representing a successful authentication if both the first authentication result and the second authentication result indicate a successful authentication, and to generate an authentication result representing a failed authentication if either the first authentication result or the second authentication result indicates a failed authentication.

[0029] Among them, the resource transfer module is specifically used to obtain the blockchain account list corresponding to the sending object from the resource server corresponding to the resource client, and display the blockchain account list in the resource client; the blockchain account list includes H blockchain accounts corresponding to the sending object; H is a positive integer; the H blockchain accounts include the sending blockchain account;

[0030] The resource transfer module is specifically used to respond to a selection operation on the blockchain account list and obtain a sending blockchain account selected by the selection operation; the sending blockchain account includes a blockchain private key associated with the sending object;

[0031] The resource transfer module is specifically used to generate transaction data for resource transfer events, sign the transaction data through the blockchain private key, obtain signature data, and splice the signature data into the transaction data;

[0032] The resource transfer module is specifically used to send transaction data carrying signature data to the blockchain node in the blockchain, so that the blockchain node verifies the transaction data carrying signature data.

[0033] The information acquisition module is specifically used to respond to the resource transfer operation for the resource client and display the resource transfer area corresponding to the resource transfer event in the resource client;

[0034] The information acquisition module is specifically used to respond to the input operation on the resource transfer area and display the input receiving account information in the resource transfer area.

[0035] The information acquisition module is specifically used to respond to the scanning operation of the shared QR code, and display the receiving blockchain address and system name input area corresponding to the resource transfer event in the resource client; the shared QR code is shared by the receiving object to the sending object;

[0036] The information acquisition module is specifically used to respond to the input operation on the system name input area and display the input receiving account system name in the system name input area; the receiving account system name and the receiving blockchain address are used to constitute the receiving account information corresponding to the resource transfer event.

[0037] The device further comprises:

[0038] A verification failure module, used to display a verification failure prompt in the resource client if the verification result indicates that the object to be verified is not the same as the received object;

[0039] The verification failure module is used to display an updated resource transfer area corresponding to the resource transfer event in the resource client based on the verification failure prompt; the updated resource transfer area is used to instruct the sending object to re-enter the receiving account information.

[0040] Among them, the sending system suffix includes sending system sub-suffixes corresponding to S levels respectively; S is an integer greater than 1; the sending system sub-suffix corresponding to the highest level among the S levels is used to indicate the sending business organization to which the sending object belongs; the sending system sub-suffixes corresponding to the S-1 levels except the highest level among the S levels are used to indicate the sending sub-business organizations to which the sending object belongs in the sending business organization; the sending sub-business organizations corresponding to the S-1 levels have a subordinate relationship.

[0041] Among them, the resource server corresponding to the resource client is used to store the sending account information; the resource server is used to receive the data acquisition request sent by the blockchain node corresponding to the sending business organization; the data acquisition request is used to obtain the account information corresponding to the object in the sending business organization, the object in the sending business organization includes the sending object, and the account information corresponding to the object in the sending business organization includes the sending account information; the resource server is also used to perform authority detection on the blockchain node corresponding to the sending business organization to obtain the authority detection result; if the authority detection result indicates that the blockchain node corresponding to the sending business organization has the authority to obtain the account information corresponding to the object in the sending business organization, then the resource server is also used to return the account information corresponding to the object in the sending business organization to the blockchain node corresponding to the sending business organization.

[0042] An embodiment of the present application provides a computer device, including: a processor and a memory;

[0043] The processor is connected to the memory, wherein the memory is used to store a computer program. When the computer program is executed by the processor, the computer device executes the method provided in the embodiment of the present application.

[0044] On the one hand, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program is suitable for being loaded and executed by a processor so that a computer device having the processor executes the method provided by the embodiment of the present application.

[0045] In one aspect, an embodiment of the present application provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the computer device executes the method provided in the embodiment of the present application.

[0046] In an embodiment of the present application, a computer device can obtain the receiving account information corresponding to the resource transfer event in the resource client. Among them, the resource transfer event is used to indicate that the sending object corresponding to the resource client transfers the digital asset to the receiving object, and the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified; the receiving account system name includes a receiving system prefix and a receiving system suffix, and the receiving system suffix is ​​used to indicate the receiving business organization to which the object to be verified belongs, and the receiving system prefix is ​​used to indicate the object to be verified in the receiving business organization. Further, the computer device can obtain the verification result for the receiving blockchain address and the receiving account system name. If the verification result indicates that the object to be verified is the same as the receiving object, transaction data for the resource transfer event is generated, and the transaction data is sent to the blockchain node in the blockchain, so that the blockchain node processes the transaction data on the chain. It can be seen that the embodiment of the present application can simultaneously obtain the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified, and determine whether the object to be verified and the receiving object are the same by verifying the results of the receiving blockchain address and the receiving account system name, so as to realize confirmation of the receiving blockchain address when transferring resources through the receiving blockchain address (that is, confirming whether the obtained receiving blockchain address is the blockchain address of the object to be verified). In this way, when the receiving blockchain address is entered incorrectly, it can be determined that the receiving account system name and the receiving blockchain address belong to different objects, so that the digital assets will not be transferred from the sending object to the receiving object (that is, no errors will occur in the resource transfer), thereby improving the security of the digital assets. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are 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 paying creative work.

[0048] Figure 1 It is a structural diagram of a network architecture provided by an embodiment of the present application;

[0049] Figure 2 This is a schematic diagram of a scenario for data interaction provided by an embodiment of the present application;

[0050] Figure 3 It is a flowchart of a data processing method based on blockchain provided in an embodiment of the present application;

[0051] Figure 4 This is a schematic diagram of a scenario for obtaining receiving account information provided by an embodiment of the present application;

[0052] Figure 5a This is a schematic diagram of a scenario for obtaining a verification result provided by an embodiment of the present application;

[0053] Figure 5b This is a schematic diagram of a scenario for obtaining a verification result provided by an embodiment of the present application;

[0054] Figure 6 This is a schematic diagram of a scenario showing a verification failure prompt provided by an embodiment of the present application;

[0055] Figure 7 It is a flowchart of a data processing method based on blockchain provided in an embodiment of the present application;

[0056] Figure 8 It is a flowchart of a data processing method based on blockchain provided in an embodiment of the present application;

[0057] Fig. 9 This is a schematic diagram of a scenario for obtaining account information provided by an embodiment of the present application;

[0058] Fig.10 It is a structural schematic diagram of a blockchain-based data processing device provided in an embodiment of the present application;

[0059] Fig.11 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0061] Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. 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, platform product service layer, and application service layer.

[0062] For details, see Figure 1 , Figure 1 Schematic diagram of a network architecture provided by an embodiment of the present application. Figure 1The network architecture shown may include a blockchain network 100a, a terminal device cluster 100b, and a resource server 100c. The blockchain network 100a may include one or more blockchain nodes, and the number of blockchain nodes in the blockchain network 100a is not limited here. Figure 1 As shown, the multiple blockchain nodes may specifically include blockchain node 110a, blockchain node 110b, blockchain node 110c, ..., blockchain node 110n; in order to ensure information intercommunication within blockchain network 100a, each blockchain node in blockchain network 100a may be directly or indirectly connected to the network through wired or wireless communication (for example, there may be a network connection between blockchain node 110a and blockchain node 110b), so that blockchain nodes may interact with each other through network connection (for example, block transmission); blockchain node 110a, blockchain node 110b, blockchain node 110c, ..., blockchain node 110n may be directly or indirectly connected to resource server 100c through wired or wireless communication, so that each blockchain node may interact with resource server 100c through network connection. Among them, the blockchain node may be a server connected to blockchain network 100a, or a terminal device connected to blockchain network 100a, and the specific form of the blockchain node is not limited here.

[0063] It is understandable that each blockchain node in the blockchain network 100a can receive data to be uploaded to the chain sent by off-chain devices (e.g., resource server 100c and terminal devices in terminal device cluster 100b) when performing normal operations, and generate blocks based on the received data to be uploaded to the chain, and then upload the blocks to the chain. It is understandable that the collection and processing of relevant data (e.g., receiving account information, sending account information) in this application should be strictly in accordance with the requirements of relevant national laws and regulations when applied in examples, and the informed consent or separate consent of the subject of personal information should be obtained, and subsequent data use and processing should be carried out within the scope of authorization of laws and regulations and the subject of personal information.

[0064] The terminal device cluster 100b may specifically include one or more terminal devices, and the number of terminal devices in the terminal device cluster 100b is not limited here. Figure 1As shown, the multiple terminal devices may specifically include a terminal device 120a, a terminal device 120b, ..., a terminal device 120m; in order to ensure information intercommunication within the terminal device cluster 100b, each terminal device in the terminal device cluster 100b may be directly or indirectly connected to a network through a wired or wireless communication (for example, a network connection may exist between the terminal device 120a and the terminal device 120b), so that the terminal devices may exchange data through the network connection; the terminal device 120a, the terminal device 120b, ..., the terminal device 120m may be directly or indirectly connected to a resource server 100c through a wired or wireless communication, so that each terminal device may exchange data with the resource server 100c through the network connection. At the same time, the terminal device cluster 100b and the blockchain network 100a can be directly or indirectly connected to the network through wired or wireless communication, so that the terminal devices in the terminal device cluster 100b and the blockchain nodes in the blockchain network 100a can exchange data through the network connection. For example, there can be a network connection between the terminal device 120b in the terminal device cluster 100b and the blockchain node 110a in the blockchain network 100a.

[0065] The terminal devices in the embodiments of the present application may include: smart phones, tablet computers, laptop computers, desktop computers, intelligent voice interaction devices, smart home appliances (e.g., smart TVs), wearable devices, vehicle terminals, aircraft, and other smart terminals with data processing functions. It should be understood that each terminal device in the terminal device cluster 100b may be installed with an application client with data processing functions. When the application client runs in each terminal device, it can be respectively connected to the above-mentioned Figure 1 Data is exchanged between the resource servers 100c shown. Among them, the application client may specifically include: a car client, a smart home client, an entertainment client (e.g., a game client), a multimedia client (e.g., a video client), a payment client (i.e., a payment application), and an information client (e.g., a news client), a resource client, a decentralized application client (Decentralized Application, DAPP), a browser, etc. Among them, the application client may be a sub-client integrated in a client (e.g., a browser), and the application client may also be an independent client (e.g., a resource client). The embodiment of the present application does not limit the type of the application client.

[0066] Among them, the server in the embodiment of the present application (for example, resource server 100c) can be 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.

[0067] For ease of understanding, the embodiment of the present application is described by taking the application client as a resource client as an example. Among them, the resource client can be the front end, the resource server 100c can be the background corresponding to the front end, and the terminal device can realize data interaction between the resource client and the resource server 100c (for example, the terminal device can send account information to the resource server 100c through the resource client, and the resource server 100c can return the verification result to the resource client in the terminal device), and the resource server 100c can be used to store the blockchain private key, blockchain address (i.e., blockchain account address) and account system name in the resource client. Among them, the blockchain address is a blockchain asset account identifier formed by converting a key generated by an asymmetric encryption algorithm according to certain rules, which can be used to receive blockchain assets, that is, the blockchain address can be used for on-chain identity identification on the blockchain network.

[0068] The resource client can be used to keep the user's account private key on the blockchain (i.e., the blockchain private key). The blockchain can identify the user's identity through the blockchain private key, and the user's digital assets are managed through the blockchain private key. The blockchain private key can be used to sign and confirm the operation (for example, a resource transfer event, which can also be called a digital asset transfer). The signed transaction can be sent by the resource client to the blockchain node. Only the correct transaction will be executed by the blockchain. The forged signature blockchain will be rejected and prompted to fail. Among them, the terminal device can send the signed transaction directly to the blockchain node; the terminal device can also send the signed transaction to the resource server 100c so that the resource server 100c forwards the signed transaction to the blockchain node; the terminal device can also generate a signed transaction through the resource server 100c and forward the signed transaction to the blockchain node.

[0069] It should be understood that the resource client can be a hardware device or a software program. The resource client can be used to implement the resource management business function, and based on the resource management business function, realize the communication connection with the decentralized application client (referred to as decentralized application, decentralized application can be a blockchain application) to realize the user's authorized login and other related operations. Among them, the resource client is a tool for managing and storing user digital assets, initiating transactions, and participating in voting. For example, digital assets can be transferred to other accounts based on the resource client, and digital assets transferred from other accounts can be received based on the resource client. With the widespread deployment of various decentralized applications on the blockchain, the activities of users on the blockchain have increased. When using decentralized applications, general users can use blockchain key management tools (i.e. resource clients) to log in. Among them, digital assets refer to new intangible assets issued, registered, stored, held, transferred or traded based on blockchain technology. These intangible assets exist in a specific system in a digital form as a digital identification of value or rights.

[0070] It should be understood that the embodiment of the present application provides a decentralized account system based on blockchain, which can introduce an account system name (the account system name can include a system prefix and a system suffix) based on the blockchain address, so that the blockchain address and the account system name can be used simultaneously in the resource transfer event (including the sending blockchain address and the sending account system name of the sending object in the resource transfer event, and the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified. The sending blockchain address and the sending account system name can be collectively referred to as the sending account information, and the receiving blockchain address and the receiving account system name can be collectively referred to as the receiving account information). The accuracy of the resource transfer event can be ensured through the blockchain address and the account system name.

[0071] Optionally, the embodiment of the present application does not limit the number of blockchain networks, and one or more blockchain networks may include blockchain network 100a. Accordingly, one or more blockchain networks may include a blockchain private key, a blockchain address, and an account system name, that is, the embodiment of the present application may simultaneously introduce a blockchain private key, a blockchain address, and an account system name in one or more blockchain networks.

[0072] For easier understanding, see Figure 2 , Figure 2 Schematic diagram of a scenario for data interaction provided by an embodiment of the present application. Figure 2 The terminal device 20a shown may be the above Figure 1 In the corresponding embodiment, any terminal device (eg, terminal device 120b) in the terminal device cluster 100b, the terminal device 20a may be installed with a resource client; Figure 2 The blockchain network 20b shown can be the above Figure 1 The blockchain network 100a in the corresponding embodiment and the blockchain nodes 21a, 21b, ..., 21c in the blockchain network 20b can all be the above Figure 1 Any blockchain node in the blockchain network 100a of the corresponding embodiment.

[0073] like Figure 2 The terminal device 20a shown can initiate a resource transfer event in the resource client. The participants of the resource transfer event may include a sender (i.e., a sending object) and a receiver (i.e., a receiving object). The resource transfer event is used to instruct the sending object to transfer the digital asset to the receiving object. The sending object may be an object corresponding to the terminal device 20a, and the receiving object may be an object corresponding to a terminal device other than the terminal device 20a. In this embodiment of the present application, users may be referred to as objects.

[0074] The resource transfer event may involve the sending account information and receiving account information of the sending object. The sending account information is the account information of the sending object in the resource client, and the receiving account information is the account information obtained by the terminal device 20a in the resource client. The receiving account information may include the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified. The object to be verified may be the same as the receiving object, or the object to be verified may be different from the receiving object. The sending account information may include the sending blockchain address of the sending object and the sending account system name of the sending object.

[0075] It can be understood that the sending account system name may include a system prefix (i.e., the sending system prefix) and a system suffix (i.e., the sending system suffix), the sending system suffix is ​​used to indicate the sending business organization to which the sending object belongs, and the sending system prefix is ​​used to indicate the sending object in the sending business organization; Figure 2 As shown, the receiving account system name may include a system prefix (i.e., the receiving system prefix) and a system suffix (i.e., the receiving system suffix), the receiving system suffix is ​​used to indicate the receiving business organization to which the object to be verified belongs, and the receiving system prefix is ​​used to indicate the object to be verified in the receiving business organization. Among them, the sending business organization and the receiving business organization may be the same business organization (i.e., the sending object and the receiving object belong to the same business organization), or may be different business organizations (i.e., the sending object and the receiving object belong to different business organizations), and this application does not limit this.

[0076] like Figure 2As shown, the terminal device 20a can obtain the verification result for the received blockchain address and the received account system name (i.e., the verification result for the received account information), and the verification result is obtained by verifying the received blockchain address and the received account system name. Among them, the terminal device 20a can verify the received blockchain address and the received account system name, and the resource server corresponding to the resource client (not shown in the figure) can also verify the received blockchain address and the received account system name.

[0077] Further, if the verification result indicates that the object to be verified is the same as the receiving object (i.e., the receiving blockchain address and the receiving account system name belong to the same object), the terminal device 20a can generate transaction data for the resource transfer event, and send the transaction data to the blockchain node (e.g., blockchain node 21a) in the blockchain network (referred to as blockchain) 20b, so that the blockchain node 21a processes the transaction data on the chain. Optionally, if the verification result indicates that the object to be verified is different from the receiving object (i.e., the receiving blockchain address and the receiving account system name do not belong to the same object), the terminal device 20a does not need to generate transaction data for the resource transfer event.

[0078] Among them, the terminal device 20a can send the transaction data directly to the blockchain node 21a in the blockchain network 20b; optionally, the terminal device 20a can also send the transaction data to the resource server (not shown in the figure) corresponding to the resource client, so that the resource server (not shown in the figure) can forward the transaction data to the blockchain node 21a in the blockchain network 20b.

[0079] It can be seen that the embodiment of the present application can use the receiving blockchain address of the sending object and the receiving account system name of the object to be verified at the same time in the resource transfer event, ensuring that when the receiving blockchain address and the receiving account system name belong to the same object (that is, the object to be verified is the same as the receiving object), the digital asset is transferred from the sending object to the receiving object. In this way, when an error occurs in the receiving blockchain address, the receiving blockchain address and the receiving account system name do not belong to the same object (that is, the object to be verified is not the same as the receiving object), the present application will not transfer the digital asset from the sending object to the receiving object, thereby improving the security of the digital asset.

[0080] For further information, see Figure 3 , Figure 3 is a flowchart of a data processing method based on blockchain provided by an embodiment of the present application. The data processing method based on blockchain can be executed by a terminal device, which can be the above-mentioned Figure 1Any terminal device in the terminal device cluster 100b of the corresponding embodiment (for example, terminal device 120a). The data processing method based on blockchain may include the following steps S101-S103:

[0081] Step S101, obtaining receiving account information corresponding to a resource transfer event in a resource client;

[0082] The resource transfer event is used to indicate that the sending object corresponding to the resource client transfers the digital assets to the receiving object; the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified, and the receiving account system name includes the receiving system prefix and the receiving system suffix. The receiving system suffix is ​​used to indicate the receiving business organization to which the object to be verified belongs, and the receiving system prefix is ​​used to indicate the object to be verified in the receiving business organization. The receiving system prefix and the receiving system suffix can be connected by a connection string, for example, the connection string can be ".".

[0083] Optionally, the receiving system suffix may include receiving system sub-suffixes corresponding to P levels, where P may be an integer greater than 1, and the P receiving system sub-suffixes may be connected by a connection string; the receiving system sub-suffix corresponding to the highest level among the P levels is used to indicate the receiving business organization to which the receiving object belongs, and the receiving system sub-suffixes corresponding to the P-1 levels except the highest level among the P levels are used to indicate the receiving sub-business organizations to which the receiving object belongs in the receiving business organization; the receiving sub-business organizations corresponding to the P-1 levels have a subordinate relationship, and the subordinate relationship of the receiving sub-business organizations corresponding to the P-1 levels is progressive in sequence.

[0084] For example, P can be equal to 2, and the P levels can include the highest level and the second highest level. The receiving sub-business organization corresponding to the second highest level can belong to the receiving business organization corresponding to the highest level. For example, the receiving business organization can be a school (or head office), the receiving sub-business organization can be a college (or subsidiary), and the receiving account system name can be A.tx.bc, where "A" can represent the receiving system prefix, "tx.bc" can represent the receiving system suffix, "tx" can represent the receiving system sub-suffix corresponding to the second highest level, and "bc" can represent the receiving system sub-suffix corresponding to the highest level. For another example, P may be equal to 3, and the P levels may include the highest level, the second highest level, and the lowest level. The receiving sub-business organization corresponding to the second highest level may belong to the receiving business organization corresponding to the highest level, and the receiving sub-business organization corresponding to the lowest level may belong to the receiving sub-business organization corresponding to the second highest level. For example, the receiving business organization corresponding to the highest level may be a school (or head office), the receiving sub-business organization corresponding to the second highest level may be a college (or subsidiary), and the receiving sub-business organization corresponding to the lowest level may be a class (or department). The receiving account system name may be A.tx.bc, where "A" may represent the receiving system prefix, "tx.bc" may represent the receiving system suffix, "tx" may represent the receiving system sub-suffix corresponding to the lowest level, "b" may represent the receiving system sub-suffix corresponding to the second highest level, and "c" may represent the receiving system sub-suffix corresponding to the highest level.

[0085] Similarly, the terminal device can obtain the sending account information corresponding to the resource transfer event in the resource client (that is, the resource client includes the sending account information of the sending object), and the sending account information has the function of providing the sending object with the function of initiating a resource transfer event (that is, the sending account information and the receiving account information have the function of providing the sending object with the function of initiating a resource transfer event); the sending account information includes the sending blockchain address of the sending object and the sending account system name of the sending object, and the sending account system name includes the sending system prefix and the sending system suffix, and the sending system suffix is ​​used to indicate the sending business organization to which the sending object belongs, and the sending system prefix is ​​used to indicate the sending object in the sending business organization. Among them, the sending system prefix and the sending system suffix can be connected by a connection string, for example, the connection string can be ".".

[0086] Optionally, the sending system suffix may include sending system sub-suffixes corresponding to S levels, where S may be an integer greater than 1, and the S sending system sub-suffixes may be connected by a connection string; the sending system sub-suffix corresponding to the highest level among the S levels is used to indicate the sending business organization to which the sending object belongs, and the sending system sub-suffixes corresponding to the S-1 levels except the highest level among the S levels are used to indicate the sending sub-business organizations to which the sending object belongs in the sending business organization; the sending sub-business organizations corresponding to the S-1 levels have a subordinate relationship, and the subordinate relationship of the sending sub-business organizations corresponding to the S-1 levels is progressive in sequence.

[0087] Specifically, the terminal device may respond to a resource transfer operation on a resource client, and display a resource transfer area corresponding to the resource transfer event in the resource client. Further, the terminal device may respond to an input operation on the resource transfer area, and display the input receiving account information in the resource transfer area. The resource transfer area may include a first resource transfer area and a second resource transfer area; the terminal device may respond to an input operation on the first resource transfer area, and display the input receiving blockchain address in the first resource transfer area; the terminal device may respond to an input operation on the second resource transfer area, and display the input receiving account system name in the second resource transfer area.

[0088] Among them, the input operation can mean that the sending object directly writes the receiving account information in the resource transfer area; the input operation can also mean that the sending object pastes the receiving account information in the resource transfer area by copying and pasting. Prior to this, the terminal device can copy the receiving account information in other application clients (for example, social clients) other than the resource client; the input operation can also mean that the sending object pastes the receiving blockchain address in the first resource transfer area by copying and pasting, and directly writes the receiving account system name in the second resource transfer area.

[0089] For easier understanding, see Figure 4 , Figure 4 Schematic diagram of a scenario for obtaining receiving account information provided by an embodiment of the present application. Figure 4 As shown, the terminal device may display a client interface 40a in the resource client, and the client interface 40a may include a quantity input area 41a, a first resource transfer area 41b, and a second resource transfer area 41c.

[0090] like Figure 4As shown, the terminal device can respond to the input operation on the quantity input area 41a, and display the input resource transfer quantity (i.e., the quantity of digital assets transferred from the sending object to the receiving object) in the quantity input area 41a, for example, the resource transfer quantity can be 1000; the terminal device can respond to the input operation on the first resource transfer area 41b, and display the input receiving blockchain address in the first resource transfer area 41b, for example, the receiving blockchain address can be LLLLLLLLLL; the terminal device can respond to the input operation on the second resource transfer area 41c, and display the input receiving account system name in the second resource transfer area 41c, for example, the receiving account system name can be A.txbc. Among them, "A" can be the receiving system prefix, "txbc" can be the receiving system suffix, and "." can be a connection string.

[0091] like Figure 4 As shown, the sending object can perform a trigger operation on the confirmation control (e.g., confirmation control 40b) in the client interface 40a, so that the terminal device can respond to the trigger operation performed by the sending object on the confirmation control 40b to obtain the verification result for the receiving blockchain address and the receiving account system name. Further, if the verification result indicates that the object to be verified is the same as the receiving object, the terminal device can generate transaction data for the resource transfer event.

[0092] Optionally, the terminal device may respond to a scan operation for a shared QR code, and display the receiving blockchain address and system name input area corresponding to the resource transfer event in the resource client. The shared QR code is shared by the receiving object to the sending object, and the receiving blockchain address of the receiving object may be integrated in the shared QR code. Therefore, by obtaining the receiving blockchain address by sharing the QR code, the sending object does not need to enter the receiving blockchain address in the resource client, and thus the sending object will not enter the wrong receiving blockchain address, thereby ensuring the accuracy of the resource transfer event. Furthermore, the terminal device may respond to an input operation for the system name input area, and display the input receiving account system name in the system name input area. The receiving account system name and the receiving blockchain address are used to constitute the receiving account information corresponding to the resource transfer event.

[0093] It is understandable that when the terminal device instructs the sender to enter the receiving account system name, the receiving system suffix can be displayed in the resource client so that the sender can enter the receiving system prefix. Optionally, when the terminal device instructs the sender to enter the receiving account system name, the sender can also be required to enter both the receiving system prefix and the receiving system suffix.

[0094] Optionally, the terminal device can respond to the scanning operation for the shared QR code, and display the receiving blockchain address and receiving account system name corresponding to the resource transfer event in the resource client. Among them, the shared QR code is shared by the receiving object to the sending object, and the receiving blockchain address and receiving account system name of the receiving object can be integrated in the shared QR code. Therefore, by obtaining the receiving blockchain address and receiving account system name by sharing the QR code, the sending object does not need to enter the receiving blockchain address and receiving account system name in the resource client, so that the sending object will not enter the wrong receiving blockchain address and receiving account system name, which can ensure the accuracy of the resource transfer event.

[0095] Therefore, the embodiments of the present application can convert complex and illegible blockchain addresses into easy-to-read account system names (i.e., account names), so that objects can use names that are easier to remember and recognize to access blockchain accounts, thereby improving the convenience and usage experience of objects. In addition, the embodiments of the present application provide a globally unique naming system in different blockchain systems, and can create a globally unique account system name (also known as a domain name) for each object. The account system name can be used in scenarios such as encrypted asset transfers, domain name resolution, and identity authentication, and only the object has full control and use rights over the account.

[0096] Step S102, obtaining verification results for the receiving blockchain address and the receiving account system name;

[0097] It can be understood that the verification result is obtained by verifying the receiving blockchain address and the receiving account system name. The terminal device can verify the receiving blockchain address and the receiving account system name to obtain the verification result; the resource server corresponding to the resource client can also verify the receiving blockchain address and the receiving account system name to obtain the verification result.

[0098] It should be understood that the specific process of the terminal device verifying the received blockchain address and the received account system name can be described as follows: the terminal device can send the received blockchain address to the resource server corresponding to the resource client. Among them, the resource server is used to obtain the query account system name corresponding to the received blockchain address from the resource database. Further, the terminal device can receive the query account system name returned by the resource server, compare the query account system name with the receiving account system name, and if the query account system name and the receiving account system name are the same, a verification result is generated to characterize that the object to be verified is the same as the receiving object. Optionally, if the query account system name and the receiving account system name are not the same, the terminal device can generate a verification result to characterize that the object to be verified is different from the receiving object.

[0099] Optionally, the terminal device may send the receiving account system name to the resource server corresponding to the resource client. The resource server is used to obtain the query blockchain address corresponding to the receiving account system name from the resource database. Further, the terminal device may receive the query blockchain address returned by the resource server, compare the query blockchain address with the receiving blockchain address, and if the query blockchain address and the receiving blockchain address are the same, generate a verification result for indicating that the object to be verified is the same as the receiving object. Optionally, if the query blockchain address and the receiving blockchain address are not the same, the terminal device may generate a verification result for indicating that the object to be verified is not the same as the receiving object.

[0100] For easier understanding, see Figure 5a , Figure 5a Schematic diagram of a scenario for obtaining verification results provided by an embodiment of the present application. Figure 5a The terminal device 50a shown may be the above Figure 1 Any terminal device in the terminal device cluster of the corresponding embodiment (for example, terminal device 120b), such as Figure 5a The resource server 50b shown may be the above Figure 1 The resource server 100c in the corresponding embodiment. The resource server 50b may include a resource database, which may include a blockchain address field and an account system name field. The blockchain address field and the account system name field are associated with each other. The account system name field can be searched through the blockchain address field, and the blockchain address field can be searched through the account system name field. For example, the blockchain address B1 and the account system name C1 are associated with each other.

[0101] like Figure 5a As shown, the terminal device 50a can send the received blockchain address to the resource server 50b, so that the resource server 50b can receive the received blockchain address sent by the terminal device 50a, and obtain the query account system name corresponding to the received blockchain address from the resource database. For example, when the received blockchain address is B1, the query account system name corresponding to the received blockchain address can be C1. Further, the resource server 50b can return the query account system name to the terminal device 50a, so that the terminal device 50a can receive the query account system name returned by the resource server 50b, compare the query account system name with the received account system name, and obtain a verification result. Among them, the verification result can indicate that the query account system name and the received account system name are not the same, and the verification result can also indicate that the query account system name and the received account system name are the same.

[0102] Optionally, the terminal device may send the receiving blockchain address and the receiving account system name to the resource server corresponding to the resource client. The resource server is used to obtain the query account system name corresponding to the receiving blockchain address from the resource database; the resource server is also used to compare the query account system name with the receiving account system name. If the query account system name and the receiving account system name are the same, the resource server may generate a verification result for characterizing that the object to be verified is the same as the receiving object; if the query account system name and the receiving account system name are different, the resource server may generate a verification result for characterizing that the object to be verified is different from the receiving object. Further, the terminal device may receive the verification result returned by the resource server.

[0103] Optionally, the terminal device may send the receiving blockchain address and the receiving account system name to the resource server corresponding to the resource client. The resource server is used to obtain the query blockchain address corresponding to the receiving account system name from the resource database; the resource server is also used to compare the query blockchain address with the receiving blockchain address. If the query blockchain address and the receiving blockchain address are the same, the resource server may generate a verification result for characterizing that the object to be verified is the same as the receiving object; if the query blockchain address and the receiving blockchain address are not the same, the resource server may generate a verification result for characterizing that the object to be verified is different from the receiving object. Further, the terminal device may receive the verification result returned by the resource server.

[0104] For easier understanding, see Figure 5b , Figure 5b Schematic diagram of a scenario for obtaining verification results provided by an embodiment of the present application. Figure 5b The terminal device 50a shown may be the above Figure 1 Any terminal device in the terminal device cluster of the corresponding embodiment (for example, terminal device 120b), such as Figure 5b The resource server 50b shown may be the above Figure 1 The resource server 100c in the corresponding embodiment. The resource server 50b may include a resource database, which may include a blockchain address field and an account system name field. The blockchain address field and the account system name field are associated with each other. The account system name field can be searched through the blockchain address field, and the blockchain address field can be searched through the account system name field. For example, the blockchain address B2 and the account system name C2 are associated with each other.

[0105] like Figure 5bAs shown, the terminal device 50a can send the receiving blockchain address and the receiving account system name to the resource server 50b, so that the resource server 50b can receive the receiving blockchain address and the receiving account system name sent by the terminal device 50a, and obtain the query account system name corresponding to the receiving blockchain address from the resource database. For example, when the receiving blockchain address is B2, the query account system name corresponding to the receiving blockchain address can be C2. Further, the resource server 50b can compare the query account system name with the receiving account system name to obtain a verification result. Among them, the verification result can indicate that the query account system name and the receiving account system name are not the same, and the verification result can also indicate that the query account system name and the receiving account system name are the same. Further, the resource server 50b can return the verification result to the terminal device 50a, so that the terminal device 50a can receive the verification result returned by the resource server 50b.

[0106] Step S103: If the verification result indicates that the object to be verified is the same as the receiving object, transaction data for the resource transfer event is generated, and the transaction data is sent to the blockchain node in the blockchain so that the blockchain node processes the transaction data on the chain.

[0107] Specifically, if the verification result indicates that the object to be verified is the same as the receiving object, the terminal device can obtain the blockchain account list corresponding to the sending object from the resource server corresponding to the resource client, and display the blockchain account list in the resource client. Among them, the blockchain account list includes H blockchain accounts corresponding to the sending object, where H can be a positive integer; the H blockchain accounts include the sending blockchain account, and the H blockchain accounts can correspond to different account system names or the same account system name, which is not limited in this application. Further, the terminal device can respond to the selection operation on the blockchain account list and obtain the sending blockchain account selected by the selection operation. Among them, the sending blockchain account includes the blockchain private key and the blockchain public key associated with the sending object, and the sending blockchain account can be the blockchain account corresponding to the resource transfer event. Further, the terminal device can generate transaction data for the resource transfer event, sign the transaction data through the blockchain private key, obtain the signature data, and splice the signature data into the transaction data. Further, the terminal device can send the transaction data carrying the signature data to the blockchain node in the blockchain so that the blockchain node verifies the transaction data carrying the signature data. In other words, the terminal device can send the signature data and transaction data to the blockchain node in the blockchain, so that the blockchain node can verify the signature data and transaction data through the blockchain public key (that is, the signature data and transaction data are verified through the blockchain public key, which can also be called verifying the signature data through the blockchain public key) to obtain the verification result.

[0108] The public key (i.e. blockchain public key) and the private key (i.e. blockchain private key) are a key pair obtained through an algorithm. The public key is the public part of the key pair, and the private key is the non-public part. This algorithm can ensure that the key pair is unique. When using this key pair, if one of the keys is used to encrypt a piece of data, the other key must be used to decrypt it. For example, data encrypted with the public key must be decrypted with the private key, and data encrypted with the private key must also be decrypted with the public key.

[0109] The terminal device may perform hash processing on the transaction data to obtain first summary information corresponding to the transaction data. Further, the terminal device may perform encryption processing on the first summary information using a blockchain private key to obtain signature data. The signature processing may include hash processing and encryption processing.

[0110] Among them, the resource server can decrypt the signature data through the blockchain public key to obtain the first summary information corresponding to the transaction data. Further, the resource server can hash the transaction data to obtain the second summary information corresponding to the transaction data. Among them, the signature verification process includes decryption processing and hash processing. Further, if the first summary information and the second summary information are the same, the resource server can generate a signature verification result indicating that the signature verification is successful; optionally, if the first summary information and the second summary information are different, the resource server can generate a signature verification result indicating that the signature verification failed. Further, if the signature verification result indicates that the signature verification is successful, the blockchain node can process the transaction data on the chain; optionally, if the signature verification result indicates that the signature verification fails, the blockchain node does not need to process the transaction data on the chain.

[0111] It can be understood that the terminal device or resource server can hash the transaction data through a hash algorithm. The embodiment of the present application does not limit the hash algorithm used for hash calculation. For example, the hash algorithm can be an MD5 Message-Digest Algorithm.

[0112] It should be understood that if the transaction data is successfully uploaded to the blockchain network, the terminal device can receive the upload result returned by the blockchain node through the resource client to indicate the successful upload. Alternatively, if the transaction data is not successfully uploaded to the blockchain network, the terminal device can receive the upload result returned by the blockchain node through the resource client to indicate the failure of the upload.

[0113] Optionally, if the verification result indicates that the object to be verified is not the same as the receiving object, the terminal device may display a verification failure prompt in the resource client. Further, the terminal device may display an updated resource transfer area corresponding to the resource transfer event in the resource client based on the verification failure prompt. The updated resource transfer area is used to instruct the sending object to re-enter the receiving account information. The specific process of the sending object entering the receiving account information in the updated resource transfer area can refer to the above description of the sending object entering the receiving account information in the resource transfer area, which will not be repeated here.

[0114] For easier understanding, see Figure 6 , Figure 6 Schematic diagram of a scene showing a verification failure prompt provided by an embodiment of the present application. Figure 6 The client interface 60a shown and the above Figure 4 The client interface 40a in the corresponding embodiment may be a client interface of a resource client in a terminal device at different times.

[0115] like Figure 6 As shown, the terminal device can respond to the above Figure 4 The trigger operation performed by the confirmation control 40b in the corresponding embodiment obtains the verification result for the received blockchain address and the received account system name. Further, if the verification result indicates that the object to be verified is not the same as the received object, the terminal device can switch the client interface 40a to the client interface 60a, and display the verification failure prompt 60b in the client interface 60b. For example, the verification failure prompt 60b can be "the blockchain address and the account system name do not match".

[0116] It can be seen that the embodiment of the present application can simultaneously obtain the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified, and determine whether the object to be verified and the receiving object are the same by verifying the results of the receiving blockchain address and the receiving account system name, so as to realize confirmation of the receiving blockchain address when transferring resources through the receiving blockchain address (that is, confirming whether the obtained receiving blockchain address is the blockchain address of the object to be verified). In this way, when the receiving blockchain address is entered incorrectly, it can be determined that the receiving account system name and the receiving blockchain address belong to different objects, so that the digital assets will not be transferred from the sending object to the receiving object (that is, no errors will occur in the resource transfer), thereby improving the security of the digital assets.

[0117] For further information, see Figure 7 , Figure 7 is a flowchart of a data processing method based on blockchain provided by an embodiment of the present application. The data processing method based on blockchain can be executed by a terminal device, which can be the above-mentioned Figure 1Any terminal device in the terminal device cluster 100b of the corresponding embodiment (for example, the terminal device 120a). The data processing method based on blockchain may include the following steps S201-S203:

[0118] Step S201, generating a sending blockchain account corresponding to the sending object in the resource client;

[0119] Specifically, the terminal device can respond to the trigger operation of the account creation control in the resource client and generate a sending blockchain account corresponding to the sending object in the resource client. The sending blockchain account can include a blockchain public key and a blockchain private key associated with the sending object, and the blockchain public key and the blockchain private key are a key pair.

[0120] Step S202, obtaining a sending blockchain address corresponding to the sending blockchain account and a sending account system name corresponding to the sending blockchain account;

[0121] Specifically, the terminal device can address encode the blockchain public key to generate a sending blockchain address corresponding to the sending blockchain account. Furthermore, the terminal device can obtain the candidate account system name entered by the sending object, authenticate the sending object and the candidate account system name, and obtain an authentication result. Further, if the authentication result indicates that the authentication is successful, the terminal device can determine the candidate account system name as the sending account system name corresponding to the sending blockchain account. Among them, the sending account system name includes a sending system prefix and a sending system suffix; the sending system suffix is ​​used to indicate the sending business organization to which the sending object belongs, and the sending system prefix is ​​used to indicate the sending object in the sending business organization. Optionally, if the authentication result indicates that the authentication failed, the terminal device can instruct the sending object to re-enter the candidate account system name, and then re-authenticate the input candidate account system name.

[0122] Optionally, the terminal device can send the blockchain public key to the resource server corresponding to the resource client, so that the resource server can address encode the blockchain public key and generate a sending blockchain address corresponding to the sending blockchain account. Further, the terminal device can receive the sending blockchain address returned by the resource server. Among them, the embodiment of the present application does not limit the specific process of address encoding. For example, the embodiment of the present application can determine the blockchain public key as the sending blockchain address.

[0123] Optionally, the terminal device may send the candidate account system name input by the sender to the resource server corresponding to the resource client, so that the resource server may authenticate the sender and the candidate account system name to obtain an authentication result. Further, the terminal device may receive the authentication result returned by the resource server.

[0124] It should be understood that the terminal device can obtain the candidate account system name input by the sending object. The candidate account system name includes a candidate system prefix and a candidate system suffix. Further, the terminal device can perform a first authentication on the sending object and the candidate system suffix to obtain a first authentication result; the terminal device can perform a second authentication on the candidate system prefix to obtain a second authentication result. Further, if both the first authentication result and the second authentication result indicate successful authentication, the terminal device can generate an authentication result for characterizing successful authentication; optionally, if the first authentication result or the second authentication result indicates failed authentication, the terminal device can generate an authentication result for characterizing failed authentication.

[0125] It is understandable that the terminal device can perform a first authentication on the sending object and the candidate system suffix. If the sending object belongs to the candidate business organization represented by the candidate system suffix, the terminal device can generate a first authentication result to indicate a successful authentication; optionally, if the sending object does not belong to the candidate business organization represented by the candidate system suffix, the terminal device can generate a first authentication result to indicate a failed authentication. The first authentication can ensure that only objects belonging to a certain business organization can create an account system name with the system suffix of the business organization, and objects that do not belong to the business organization cannot create an account system name with the system suffix of the business organization, thereby ensuring the security of the account system name.

[0126] Among them, the terminal device may require the sending object to enter the email address of the candidate business organization, and determine whether the sending object belongs to the candidate business organization represented by the candidate system suffix through the email address. For example, the terminal device may require the sending object to send a specified email to a specified email address through the email address of the candidate business organization to achieve the first authentication of the sending object and the candidate system suffix. Optionally, the terminal device may require the sending object to upload the certification information associated with the candidate business organization (for example, work contract, work card), and then verify the certification information uploaded by the sending object to achieve the first authentication of the sending object and the candidate system suffix. Optionally, the terminal device can detect whether the sending object is applying to send a blockchain account through a sharing link. If the sending object is applying to send a blockchain account through a sharing link, it is determined that the sending object belongs to the candidate business organization represented by the candidate system suffix; optionally, if the sending object is not applying to send a blockchain account through a sharing link, it is determined that the sending object does not belong to the candidate business organization represented by the candidate system suffix. Among them, the sharing link is shared by an organization object (for example, an administrator) in the candidate business organization, and the organization object is an object that has been authenticated and does belong to the candidate business organization. Optionally, the terminal device may notify the sender to perform an offline identity comparison to confirm the reliability of the sender's identity. For example, the terminal device may receive an offline identity authentication notification, and the sender may perform a manual comparison within a specified time based on the content recorded in the offline identity authentication notification, and then perform the first authentication of the sender and the candidate system suffix based on the manual comparison result.

[0127] It can be understood that the terminal device can perform a second authentication on the candidate system prefix. If the candidate business organization represented by the candidate system suffix does not include an account system name with a system prefix as the candidate system prefix, the terminal device can generate a second authentication result to characterize a successful authentication. Optionally, if the candidate business organization represented by the candidate system suffix includes an account system name with a system prefix as the candidate system prefix, the terminal device can generate a second authentication result to characterize a failed authentication.

[0128] Among them, since different objects in the same business organization should have different system prefixes (that is, different objects in the candidate business organization should have different system prefixes), the second authentication can be used to determine whether the candidate business organization represented by the candidate system suffix has an object with a system prefix that is the candidate system prefix. Further, if the candidate business organization has an object with a system prefix that is the candidate system prefix, it means that the candidate business organization represented by the candidate system suffix includes an account system name with a system prefix that is the candidate system prefix; optionally, if the candidate business organization does not have an object with a system prefix that is the candidate system prefix, it means that the candidate business organization represented by the candidate system suffix does not include an account system name with a system prefix that is the candidate system prefix.

[0129] Step S203: determine the sending blockchain address and the sending account system name as the sending account information.

[0130] It should be understood that the resource server corresponding to the resource client is used to store the sending account information. Similarly, when the object to be verified and the receiving object are the same, the resource server is used to store the receiving account information; optionally, when the object to be verified and the receiving object are different, the receiving blockchain address and the receiving account system name belong to different objects, so the resource server cannot store the receiving blockchain address and the receiving account system name.

[0131] It is understandable that the embodiment of the present application can bind the sending blockchain address and the sending account system name to the sending blockchain account in the process of generating the sending blockchain account. Optionally, the embodiment of the present application can also bind the sending blockchain address to the sending blockchain account in the process of generating the sending blockchain account, and then bind the sending account system name to the sending blockchain account in the subsequent steps.

[0132] It can be seen that the embodiment of the present application can generate a sending blockchain account corresponding to the sending object in the resource client, and then obtain the sending blockchain address corresponding to the sending blockchain account and the sending account system name corresponding to the sending blockchain account, and determine the sending blockchain address and the sending account system name as the sending account information. Therefore, the embodiment of the present application can use the sending blockchain address and the sending account system name in the resource client at the same time, and realize the subsequent resource transfer through the sending blockchain address and the sending account system name, so that the resource transfer will not be wrong, and the security of digital assets is improved.

[0133] For further information, see Figure 8 , Figure 8 This is a flowchart of a data processing method based on blockchain provided by an embodiment of the present application. The data processing method based on blockchain can be executed by a resource server corresponding to a resource client in a terminal device, and the resource server can be the above-mentioned Figure 1 The resource server 100c in the corresponding embodiment. The data processing method based on blockchain may include the following steps S301-S303:

[0134] Step S301, receiving a data acquisition request sent by a target blockchain node;

[0135] Among them, the target blockchain node can be a blockchain node corresponding to the sending business organization, and the resource server can receive a data acquisition request (i.e., a first data acquisition request) sent by the blockchain node corresponding to the sending business organization. At this time, the data acquisition request (i.e., the first data acquisition request) is used to obtain the account information corresponding to the object in the sending business organization, the object in the sending business organization includes the sending object, and the account information corresponding to the object in the sending business organization includes the sending account information. Optionally, the data acquisition request (i.e., the first data acquisition request) can also be used to obtain the account information corresponding to the object in the sending sub-business organization, the object in the sending sub-business organization includes the sending object, and the account information corresponding to the object in the sending sub-business organization includes the sending account information.

[0136] Optionally, the sending business organization may include a sending sub-business organization, the target blockchain node may be a blockchain node corresponding to the sending sub-business organization, and the resource server may receive a data acquisition request (i.e., a second data acquisition request) sent by the blockchain node corresponding to the sending sub-business organization. At this time, the data acquisition request (i.e., the second data acquisition request) is used to obtain the account information corresponding to the object in the sending sub-business organization, the object in the sending sub-business organization includes the sending object, and the account information corresponding to the object in the sending sub-business organization includes the sending account information. Optionally, the data acquisition request (i.e., the second data acquisition request) may also be used to obtain the account information corresponding to the object in the sending business organization, the object in the sending business organization includes the sending object, and the account information corresponding to the object in the sending business organization includes the sending account information.

[0137] Step S302: Performing a permission check on the target blockchain node based on the data acquisition request to obtain a permission check result;

[0138] Wherein, when the target blockchain node is the blockchain node corresponding to the sending business organization, the terminal device can perform permission detection on the blockchain node corresponding to the sending business organization based on the data acquisition request (i.e., the first data acquisition request) to obtain the permission detection result (i.e., the first permission detection result). Wherein, if the first data acquisition request is used to obtain the account information corresponding to the object in the sending business organization, the blockchain node corresponding to the sending business organization has the permission to obtain the account information corresponding to the object in the sending business organization; similarly, if the first data acquisition request is used to obtain the account information corresponding to the object in the sending sub-business organization, the blockchain node corresponding to the sending business organization has the permission to obtain the account information corresponding to the object in the sending sub-business organization.

[0139] Optionally, when the target blockchain node is the blockchain node corresponding to the sending sub-business organization, the terminal device can perform a permission check on the blockchain node corresponding to the sending sub-business organization based on the data acquisition request (i.e., the second data acquisition request) to obtain a permission check result (i.e., the second permission check result). Wherein, if the second data acquisition request is used to obtain the account information corresponding to the object in the sending business organization, the blockchain node corresponding to the sending sub-business organization does not have the permission to obtain the account information corresponding to the object in the sending business organization; similarly, if the second data acquisition request is used to obtain the account information corresponding to the object in the sending sub-business organization, the blockchain node corresponding to the sending sub-business organization has the permission to obtain the account information corresponding to the object in the sending sub-business organization.

[0140] It is understandable that the specific process of the resource server performing permission detection on the target blockchain node can be described as follows: the resource server can obtain the target node identifier corresponding to the data acquisition request. The target node identifier can be used to indicate that the data acquisition request is sent by the target blockchain node; when the target blockchain node is the blockchain node corresponding to the sending business organization, the target node identifier can be the node identifier of the blockchain node corresponding to the sending business organization; when the target blockchain node is the blockchain node corresponding to the sending sub-business organization, the target node identifier can be the node identifier of the blockchain node corresponding to the sending sub-business organization. Furthermore, the resource server may obtain a sending node identifier corresponding to the sending business organization (or a sending node identifier corresponding to the sending sub-business organization). If the target node identifier is the same as the sending node identifier corresponding to the sending business organization (or the sending node identifier corresponding to the sending sub-business organization), a permission detection result is generated to indicate that the target blockchain node has the authority to obtain the account information corresponding to the object in the sending business organization (or the sending sub-business organization); optionally, if the target node identifier is different from the sending node identifier corresponding to the sending business organization (or the sending node identifier corresponding to the sending sub-business organization), a permission detection result is generated to indicate that the target blockchain node does not have the authority to obtain the account information corresponding to the object in the sending business organization (or the sending sub-business organization).

[0141] Step S303: If the authority detection result indicates that the target blockchain node has the authority to obtain the account information corresponding to the object in the sending business organization, the account information corresponding to the object in the sending business organization is returned to the target blockchain node.

[0142] Among them, if the permission detection result (for example, the first permission detection result) indicates that the blockchain node corresponding to the sending business organization (i.e., the target blockchain node) has the authority to obtain the account information corresponding to the object in the sending business organization, the terminal device can return the account information corresponding to the object in the sending business organization to the blockchain node corresponding to the sending business organization. Optionally, if the permission detection result (for example, the second permission detection result) indicates that the blockchain node corresponding to the sending sub-business organization (i.e., the target blockchain node) does not have the authority to obtain the account information corresponding to the object in the sending business organization, the resource server does not need to return the account information corresponding to the object in the sending business organization to the blockchain node corresponding to the sending sub-business organization.

[0143] Optionally, if the permission detection result indicates that the target blockchain node has the permission to obtain the account information corresponding to the object in the sending sub-business organization, the resource server can return the account information corresponding to the object in the sending sub-business organization to the target blockchain node.

[0144] Among them, if the permission detection result (for example, the first permission detection result) indicates that the blockchain node corresponding to the sending business organization (i.e., the target blockchain node) has the authority to obtain the account information corresponding to the object in the sending sub-business organization, the terminal device can return the account information corresponding to the object in the sending sub-business organization to the blockchain node corresponding to the sending business organization. Optionally, if the permission detection result (for example, the second permission detection result) indicates that the blockchain node corresponding to the sending sub-business organization (i.e., the target blockchain node) has the authority to obtain the account information corresponding to the object in the sending sub-business organization, the terminal device can return the account information corresponding to the object in the sending sub-business organization to the blockchain node corresponding to the sending sub-business organization.

[0145] It should be understood that the blockchain node corresponding to the sending business organization can perform account management on the account information corresponding to the object in the sending business organization, the blockchain node corresponding to the sending sub-business organization can perform account management on the account information corresponding to the object in the sending sub-business organization, and the terminal device (i.e., the terminal device corresponding to the sending object) can perform account management on the account information corresponding to the H blockchain accounts of the sending object. Among them, account management may include but is not limited to modifying the account system name, viewing the account system name, and viewing the blockchain address.

[0146] It should be understood that the number of sending business organizations is one, and the number of sending sub-business organizations is S-1, where S can be a positive integer greater than 1. S-1 sending sub-business organizations can obtain the account information corresponding to the objects in their own sub-business organizations, or the account information corresponding to the objects in the lower-level sub-business organizations, but cannot obtain the account information corresponding to the objects in the higher-level sub-business organizations. For example, when the receiving sub-business organization is a college, the college can obtain the account information corresponding to the objects in the college, or the account information corresponding to the objects in the class (the class can be a lower-level sub-business organization of the college), but cannot obtain the account information corresponding to the objects in the school (the school can be a higher-level sub-business organization of the college). For another example, when the receiving sub-business organization is a class, the class can obtain the account information corresponding to the objects in the class, but cannot obtain the account information corresponding to the objects in the college (the college can be a higher-level sub-business organization of the class), or the account information corresponding to the objects in the school (the school can be a higher-level sub-business organization of the class).

[0147] Optionally, the target blockchain node in the embodiment of the present application may also be the blockchain node corresponding to the receiving business organization, or may be the blockchain node corresponding to the receiving sub-business organization. The specific process of the blockchain node corresponding to the receiving business organization obtaining the account information corresponding to the objects in the receiving business organization, and the blockchain node corresponding to the receiving sub-business organization obtaining the account information corresponding to the objects in the receiving sub-business organization, can be referred to the description of the blockchain node corresponding to the sending business organization obtaining the account information corresponding to the objects in the sending business organization, and the blockchain node corresponding to the sending sub-business organization obtaining the account information corresponding to the objects in the sending sub-business organization, and will not be repeated here.

[0148] For easier understanding, see Fig. 9 , Fig. 9 Schematic diagram of a scenario for obtaining account information provided by an embodiment of the present application. Fig. 9 The blockchain node 90a shown can be the above Figure 1 For any blockchain node (e.g., blockchain node 110a) in the blockchain network 100a of the corresponding embodiment, the terminal device 90b can be the above-mentioned Figure 1 For any terminal device in the terminal device cluster 100b of the corresponding embodiment (for example, the terminal device 120b), the resource server 90c may be the above-mentioned Figure 1 The resource server 100c in the corresponding embodiment. Among them, the blockchain node 110a can be a blockchain node corresponding to the sending business organization, or the blockchain node 110a can be a blockchain node corresponding to the sending sub-business organization.

[0149] Among them, the resource server 90c may include a resource database, and the resource database may include a blockchain address field and an account system name field. The blockchain address field and the account system name field are associated with each other. The account system name field can be searched through the blockchain address field, and the blockchain address field can be searched through the account system name field.

[0150] like Fig. 9 As shown, the terminal device 90b can generate the sending account information in the resource client and send the sending account information to the resource server 90c. In this way, the resource server 90c can receive the sending account information sent by the terminal device 90b and store the sending account information. For example, the blockchain address B1 and the account system name C1 have an association relationship (also called a mapping relationship), the blockchain address B1 can be the sending blockchain node, and the account system name C1 can be the sending account system name.

[0151] like Fig. 9 As shown, the blockchain node 90a can send a data acquisition request to the resource server 90c, so that the resource server 90c can receive the data acquisition request sent by the blockchain node 90a. Among them, the data acquisition request can be used to obtain the account information corresponding to the object in the sending business organization. Further, the resource server 90c can perform an authority detection on the blockchain node 90a based on the data acquisition request to obtain the authority detection result.

[0152] Among them, it can be understood that if the blockchain node 110a is the blockchain node corresponding to the sending business organization, the blockchain node 110a has the authority to obtain the account information corresponding to the object in the sending business organization; further, the resource server 90c can return the account information corresponding to the object in the sending business organization (the account information corresponding to the object in the sending business organization can include the blockchain address B1 and the account system name C1) to the blockchain node 90a. Optionally, if the blockchain node 110a is the blockchain node corresponding to the sending sub-business organization, the blockchain node 110a does not have the authority to obtain the account information corresponding to the object in the sending business organization; further, the resource server 90c does not need to return the account information corresponding to the object in the sending business organization to the blockchain node 90a.

[0153] Optionally, the resource server may receive a data acquisition request sent by the target blockchain node. The data acquisition request may be used to obtain account information associated with the target blockchain node. Further, the resource server may return the account information associated with the target blockchain node to the target blockchain node. For example, when the target blockchain node is a blockchain node corresponding to a sending business organization, the data acquisition request is used to obtain the account information corresponding to the object in the sending business organization. At this time, the account information associated with the target blockchain node may be the account information corresponding to the object in the sending business organization. Further, the resource server may return the account information corresponding to the object in the sending business organization to the target blockchain node. For another example, when the target blockchain node is a blockchain node corresponding to a sending sub-business organization, the data acquisition request is used to obtain the account information corresponding to the object in the sending sub-business organization. At this time, the account information associated with the target blockchain node may be the account information corresponding to the object in the sending sub-business organization. Further, the resource server may return the account information corresponding to the object in the sending sub-business organization to the target blockchain node.

[0154] Optionally, the resource server can obtain the decentralized identity information corresponding to the target blockchain node from the data acquisition request, and obtain the decentralized identity signature file of the target blockchain node from the blockchain through the decentralized identity information. Among them, the target blockchain node refers to the blockchain node at the i-th level in the node relationship chain, where i can be an integer greater than 1; the decentralized identity signature file of the blockchain node at the i-th level in the node relationship chain is generated based on the blockchain private key of the blockchain node at the i-1th level in the node relationship chain, and the i-1th level is higher than the i-th level. Each non-top-level blockchain node has a corresponding decentralized identity signature file, and the decentralized identity signature file of each non-top-level blockchain node contains its own blockchain public key. The non-top-level refers to the level other than the top-level; the blockchain public key of the top-level blockchain node (i.e., the blockchain node at the first level, the blockchain node at the first level represents the blockchain node corresponding to the trusted third-party organization) and the decentralized identity signature file of each non-top-level blockchain node are stored in the blockchain.

[0155] Among them, the decentralized identity information can be DID (Decentralized Identity) information, the DID information can be a readable string representing the user identity, the decentralized identity information can also be called a DID identifier, the DID identifier can be used to index a decentralized identity signature file, a DID identifier can correspond to a DID file (DIDDocument, decentralized identity file), and a DID identifier can correspond to a decentralized identity signature file.

[0156] Further, the resource server can determine the i-1th level blockchain node used to sign the decentralized identity signature file of the target blockchain node in the node relationship chain, and obtain the decentralized identity information of the i-1th level blockchain node. Further, if the decentralized identity information of the i-1th level blockchain node indicates that the i-1th level is not the highest level, the resource server can obtain the decentralized identity signature file of the i-1th level blockchain node in the blockchain through the decentralized identity information of the i-1th level blockchain node, add the target blockchain node and the i-1th level blockchain node to the blockchain node set, continue to traverse i-2 objects from the i-1th level blockchain node to the upper layer, and add the traversed i-2 objects to the blockchain node set. Among them, the specific process of traversing i-2 blockchain nodes from the i-1th level blockchain node to the upper layer can refer to the above description of traversing i-1 blockchain nodes from the target blockchain node, which will not be repeated here. Optionally, if the decentralized identity information of the blockchain node at level i-1 indicates that level i-1 is the highest level, the target blockchain node and the blockchain node at level i-1 are added to the blockchain node set, wherein the levels of the blockchain nodes in the blockchain node set include level i to the highest level in order.

[0157] Further, the resource server can obtain the blockchain public key of the highest-level blockchain node from the blockchain, and obtain the second-highest-level blockchain node of the node relationship chain from the blockchain node set. Among them, the blockchain public key of the highest-level blockchain node is obtained from the decentralized identity file of the highest-level blockchain node, and the decentralized identity file of the highest-level blockchain node is directly stored in the blockchain; the decentralized identity signature file of the second-highest-level blockchain node is generated based on the blockchain private key of the highest-level blockchain node. The second-highest-level blockchain node and the highest-level blockchain node are blockchain nodes of adjacent levels in the node relationship chain, and the level of the highest-level blockchain node is higher than that of the second-highest-level blockchain node. Further, if the second-highest-level blockchain node is the target blockchain node, the resource server can determine that the blockchain node at the i-1th level in the blockchain node set is the highest-level blockchain node, and use the blockchain public key of the highest-level blockchain node as the target blockchain public key. Optionally, if the blockchain node at the next higher level is not the target blockchain node, the resource server may verify the decentralized identity signature file of the blockchain node at the next higher level through the blockchain public key of the blockchain node at the highest level. When the decentralized identity signature file of the blockchain node at the next higher level is successfully verified, the blockchain public key of the blockchain node at the next higher level is obtained from the decentralized identity signature file of the blockchain node at the next higher level, and the decentralized identity signature file of the blockchain node at the next level is continued to be verified based on the blockchain public key of the blockchain node at the next level, until the blockchain public key in the decentralized identity signature file of the blockchain node at the i-1th level in the blockchain node set is obtained as the target blockchain public key.

[0158] Among them, the decentralized identity signature file of the second-highest level blockchain node is generated by signing the decentralized identity file of the second-highest level blockchain node through the blockchain private key of the highest level blockchain node. It should be understood that the specific process of the resource server obtaining the blockchain public key of the second-highest level blockchain node from the decentralized identity signature file of the second-highest level blockchain node can be described as follows: the resource server can obtain the decentralized identity file of the second-highest level blockchain node from the decentralized identity signature file of the second-highest level blockchain node, and then obtain the blockchain public key of the second-highest level blockchain node from the decentralized identity file of the second-highest level blockchain node.

[0159] Among them, the specific process of the resource server continuing to verify the decentralized identity signature file of the next-level blockchain node (i.e., the blockchain node at a level lower than the second-level in the node relationship chain) based on the blockchain public key of the second-level blockchain node can be found in the above description of verifying the decentralized identity signature file of the second-level blockchain node based on the blockchain public key of the highest-level blockchain node, which will not be repeated here.

[0160] Furthermore, the resource server can verify the decentralized identity signature file of the target blockchain node through the target blockchain public key. When the decentralized identity signature file of the target blockchain node is successfully verified, the business organization parameter of the target blockchain node is obtained from the decentralized identity signature file of the target blockchain node, and the account information associated with the target blockchain node is obtained through the business organization parameter, and then the account information associated with the target blockchain node is returned to the target blockchain node. Optionally, when the decentralized identity signature file of the target blockchain node fails to be verified, the resource server can return an error prompt to the target blockchain node. The error prompt indicates that the target blockchain node does not have the authority to obtain account information from the resource server.

[0161] Among them, the business organization parameter can represent the system suffix corresponding to the target blockchain node. For example, the system suffix corresponding to the target blockchain node can indicate that the target blockchain node is the blockchain node corresponding to the school (that is, the target blockchain node is the blockchain node corresponding to the sending business organization), and the business organization parameter can represent the school. In this case, the account information associated with the target blockchain node can be the account information corresponding to the object in the school. For another example, the system suffix corresponding to the target blockchain node can indicate that the target blockchain node is the blockchain node corresponding to the college (that is, the target blockchain node is the blockchain node corresponding to the sending business sub-organization), and the business organization parameter can represent the college. In this case, the account information associated with the target blockchain node can be the account information corresponding to the object in the college.

[0162] Among them, the decentralized identity signature file of the target blockchain node may include the decentralized identity file of the target blockchain node and the encrypted file corresponding to the decentralized identity file of the target blockchain node. The resource server verifies the decentralized identity signature file of the target blockchain node, which can indicate that the resource server verifies the decentralized identity file of the target blockchain node and the encrypted file corresponding to the decentralized identity file of the target blockchain node. The specific process of the resource server verifying the decentralized identity file of the target blockchain node and the encrypted file corresponding to the decentralized identity file of the target blockchain node can refer to the above description of verifying the signature data by the blockchain public key, which will not be repeated here. Among them, the encrypted file corresponding to the decentralized identity file of the target blockchain node is obtained by the blockchain node of the upper level of the target blockchain node signing the decentralized identity file of the target blockchain node. The specific process of the blockchain node of the upper level of the target blockchain node signing the decentralized identity file of the target blockchain node can refer to the above description of signing the transaction data by the blockchain private key, which will not be repeated here.

[0163] Among them, the process of the blockchain node at the upper level of the target blockchain node signing the decentralized identity file of the target blockchain node can be understood as the blockchain node at the upper level of the target blockchain node authorizing the target blockchain node to obtain the right of account information. At this time, the subordinate relationship between the blockchain node at the upper level of the target blockchain node and the target blockchain node can be assigned to the resource server through the decentralized identity signature file, so that the resource server can reasonably send the stored account information of different permissions to different blockchain nodes.

[0164] It can be seen from this that the embodiment of the present application can receive the data acquisition request sent by the target blockchain node, and return the account information corresponding to the data acquisition request to the target blockchain node, so that the stored account information can be managed through the resource server, and the sending and receiving of the account information can be realized, thereby improving the security of the stored account information.

[0165] For further information, see Fig.10 , Fig.10 1 is a schematic diagram of the structure of a blockchain-based data processing device provided in an embodiment of the present application. The data processing device 1 may include: an information acquisition module 11, an information verification module 12, and a resource transfer module 13; further, the data processing device 1 may also include: an account generation module 14, an information determination module 15, and a verification failure module 16;

[0166] The information acquisition module 11 is used to obtain the receiving account information corresponding to the resource transfer event in the resource client; the resource transfer event is used to instruct the sending object corresponding to the resource client to transfer the digital assets to the receiving object; the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified; the receiving account system name includes a system prefix and a system suffix; the system suffix is ​​used to indicate the business organization to which the object to be verified belongs, and the system prefix is ​​used to indicate the object to be verified in the business organization;

[0167] The information acquisition module 11 is specifically used to respond to the resource transfer operation on the resource client and display the resource transfer area corresponding to the resource transfer event in the resource client;

[0168] The information acquisition module 11 is specifically configured to respond to an input operation on the resource transfer area and display the input receiving account information in the resource transfer area.

[0169] The information acquisition module 11 is specifically used to respond to the scanning operation of the shared QR code and display the receiving blockchain address and system name input area corresponding to the resource transfer event in the resource client; the shared QR code is shared by the receiving object to the sending object;

[0170] The information acquisition module 11 is specifically used to respond to the input operation on the system name input area and display the input receiving account system name in the system name input area; the receiving account system name and the receiving blockchain address are used to constitute the receiving account information corresponding to the resource transfer event.

[0171] An information verification module 12 is used to obtain a verification result for a receiving blockchain address and a receiving account system name; the verification result is obtained by verifying the receiving blockchain address and the receiving account system name;

[0172] Among them, the information verification module 12 is specifically used to send the received blockchain address to the resource server corresponding to the resource client; the resource server is used to obtain the query account system name corresponding to the received blockchain address from the resource database;

[0173] The information verification module 12 is specifically used to receive the query account system name returned by the resource server, compare the query account system name with the received account system name, and if the query account system name and the received account system name are the same, generate a verification result indicating that the object to be verified is the same as the received object;

[0174] The information verification module 12 is specifically used to generate a verification result indicating that the object to be verified is different from the receiving object if the query account system name and the receiving account system name are different.

[0175] The resource transfer module 13 is used to generate transaction data for the resource transfer event if the verification result indicates that the object to be verified is the same as the receiving object, and send the transaction data to the blockchain node in the blockchain so that the blockchain node can process the transaction data on the chain.

[0176] Among them, the resource transfer module 13 is specifically used to obtain a blockchain account list corresponding to the sending object from the resource server corresponding to the resource client, and display the blockchain account list in the resource client; the blockchain account list includes H blockchain accounts corresponding to the sending object; H is a positive integer; the H blockchain accounts include the sending blockchain account;

[0177] The resource transfer module 13 is specifically used to respond to a selection operation on the blockchain account list and obtain a sending blockchain account selected by the selection operation; the sending blockchain account includes a blockchain private key associated with the sending object;

[0178] The resource transfer module 13 is specifically used to generate transaction data for resource transfer events, sign the transaction data using a blockchain private key to obtain signature data, and splice the signature data into the transaction data;

[0179] The resource transfer module 13 is specifically used to send the transaction data carrying the signature data to the blockchain node in the blockchain, so that the blockchain node verifies the transaction data carrying the signature data.

[0180] Optionally, the resource client includes sending account information of the sending object;

[0181] An account generation module 14 is used to generate a sending blockchain account corresponding to a sending object in a resource client;

[0182] An account generation module 14 is used to obtain a sending blockchain address corresponding to a sending blockchain account and a sending account system name corresponding to the sending blockchain account; the sending account system name includes a sending system prefix and a sending system suffix; the sending system suffix is ​​used to indicate a sending business organization to which a sending object belongs, and the sending system prefix is ​​used to indicate a sending object in the sending business organization;

[0183] Wherein, the sending blockchain account includes the blockchain public key associated with the sending object;

[0184] The account generation module 14 is specifically used to perform address encoding on the blockchain public key and generate a sending blockchain address corresponding to the sending blockchain account;

[0185] The account generation module 14 is specifically used to obtain the candidate account system name input by the sending object, authenticate the sending object and the candidate account system name, and obtain the authentication result;

[0186] The account generation module 14 is specifically configured to determine the candidate account system name as the sending account system name corresponding to the sending blockchain account if the authentication result indicates that the authentication is successful.

[0187] The account generation module 14 is specifically used to obtain the candidate account system name input by the sending object; the candidate account system name includes a candidate system prefix and a candidate system suffix;

[0188] The account generation module 14 is specifically used to perform a first authentication on the sending object and the candidate system suffix, and if the sending object belongs to the candidate business organization represented by the candidate system suffix, a first authentication result is generated to indicate a successful authentication, and if the sending object does not belong to the candidate business organization represented by the candidate system suffix, a first authentication result is generated to indicate a failed authentication;

[0189] The account generation module 14 is specifically used to perform a second authentication on the candidate system prefix, and if the candidate business organization represented by the candidate system suffix does not include the account system name whose system prefix is ​​the candidate system prefix, generate a second authentication result for indicating a successful authentication, and if the candidate business organization represented by the candidate system suffix includes the account system name whose system prefix is ​​the candidate system prefix, generate a second authentication result for indicating a failed authentication;

[0190] The account generation module 14 is specifically configured to generate an authentication result indicating successful authentication if both the first authentication result and the second authentication result indicate successful authentication, and to generate an authentication result indicating failed authentication if either the first authentication result or the second authentication result indicates failed authentication.

[0191] The information determination module 15 is used to determine the sending blockchain address and the sending account system name as the sending account information; the sending account information has the function of providing the sending object with the function of initiating a resource transfer event.

[0192] Optionally, a verification failure module 16 is used to display a verification failure prompt in the resource client if the verification result indicates that the object to be verified is not the same as the received object;

[0193] The verification failure module 16 is used to display an updated resource transfer area corresponding to the resource transfer event in the resource client based on the verification failure prompt; the updated resource transfer area is used to instruct the sending object to re-enter the receiving account information.

[0194] Among them, the sending system suffix includes sending system sub-suffixes corresponding to S levels respectively; S is an integer greater than 1; the sending system sub-suffix corresponding to the highest level among the S levels is used to indicate the sending business organization to which the sending object belongs; the sending system sub-suffixes corresponding to the S-1 levels except the highest level among the S levels are used to indicate the sending sub-business organizations to which the sending object belongs in the sending business organization; the sending sub-business organizations corresponding to the S-1 levels have a subordinate relationship.

[0195] Among them, the resource server corresponding to the resource client is used to store the sending account information; the resource server is used to receive the data acquisition request sent by the blockchain node corresponding to the sending business organization; the data acquisition request is used to obtain the account information corresponding to the object in the sending business organization, the object in the sending business organization includes the sending object, and the account information corresponding to the object in the sending business organization includes the sending account information; the resource server is also used to perform authority detection on the blockchain node corresponding to the sending business organization to obtain the authority detection result; if the authority detection result indicates that the blockchain node corresponding to the sending business organization has the authority to obtain the account information corresponding to the object in the sending business organization, then the resource server is also used to return the account information corresponding to the object in the sending business organization to the blockchain node corresponding to the sending business organization.

[0196] The specific implementation of the information acquisition module 11, the information verification module 12, the resource transfer module 13, the account generation module 14, the information determination module 15, and the verification failure module 16 can be found in the above Figure 3 In the corresponding embodiment, steps S101 to S103, Figure 7 In the corresponding embodiment, steps S201 to S203 and Figure 8 The description of steps S301 to S303 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated here either.

[0197] For further information, see Fig.11 , Fig.11 Schematic diagram of a computer device provided in an embodiment of the present application, the computer device may be a terminal device or a resource server. Fig.11As shown, the computer device 1000 may include: a processor 1001, a network interface 1004 and a memory 1005. In addition, the above-mentioned computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. Among them, in some embodiments, the user interface 1003 may include a display screen (Display), a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or it may be a non-volatile memory (non-volatile memory), such as at least one disk storage. Optionally, the memory 1005 may also be at least one storage device located away from the aforementioned processor 1001. As Fig.11 As shown, the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a device control application program.

[0198] In such Fig.11 In the computer device 1000 shown, the network interface 1004 can provide a network communication function; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0199] Obtain the receiving account information corresponding to the resource transfer event in the resource client; the resource transfer event is used to instruct the sending object corresponding to the resource client to transfer the digital assets to the receiving object; the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified; the receiving account system name includes the receiving system prefix and the receiving system suffix; the receiving system suffix is ​​used to indicate the receiving business organization to which the object to be verified belongs, and the receiving system prefix is ​​used to indicate the object to be verified in the receiving business organization;

[0200] Obtaining the verification result for the receiving blockchain address and the receiving account system name; the verification result is obtained by verifying the receiving blockchain address and the receiving account system name;

[0201] If the verification result indicates that the object to be verified is the same as the receiving object, transaction data for the resource transfer event is generated and sent to the blockchain node in the blockchain so that the blockchain node processes the transaction data on the chain.

[0202] It should be understood that the computer device 1000 described in the embodiment of the present application can execute the above Figure 3 , Figure 7 and Figure 8 The description of the data processing method in the corresponding embodiment can also be performed as described above. Fig.10 The description of the data processing device 1 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated here either.

[0203] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the data processing device 1 mentioned above. When the processor executes the computer program, it can execute the above-mentioned Figure 3 , Figure 7 and Figure 8 The description of the data processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0204] In addition, it should be noted that: the embodiment of the present application also provides a computer program product, which may include a computer program, and the computer program may be stored in a computer-readable storage medium. The processor of the computer device reads the computer program from the computer-readable storage medium, and the processor may execute the computer program, so that the computer device performs the above Figure 3 , Figure 7 and Figure 8 The description of the data processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer program product embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0205] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0206] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A data processing method based on blockchain, characterized in that: include: Obtain the receiving account information corresponding to the resource transfer event in the resource client; The resource transfer event is used to instruct the sending object corresponding to the resource client to transfer the digital asset to the receiving object; the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified; the receiving account system name includes a receiving system prefix and a receiving system suffix; the receiving system suffix is ​​used to indicate the receiving business organization to which the object to be verified belongs, and the receiving system prefix is ​​used to indicate the object to be verified in the receiving business organization; Obtaining verification results for the receiving blockchain address and the receiving account system name; The verification result is obtained by verifying the receiving blockchain address and the receiving account system name; If the verification result indicates that the object to be verified is the same as the receiving object, transaction data for the resource transfer event is generated, and the transaction data is sent to a blockchain node in the blockchain, so that the blockchain node processes the transaction data on the chain.

2. The method according to claim 1, characterized in that The obtaining of the verification result for the receiving blockchain address and the receiving account system name includes: The received blockchain address is sent to a resource server corresponding to the resource client; the resource server is used to obtain the query account system name corresponding to the received blockchain address from a resource database; receiving the query account system name returned by the resource server, comparing the query account system name with the received account system name, and if the query account system name and the received account system name are the same, generating a verification result indicating that the object to be verified is the same as the received object; If the query account system name and the receiving account system name are different, a verification result is generated to indicate that the object to be verified is different from the receiving object.

3. The method according to claim 1, characterized in that The resource client includes sending account information of the sending object; The method further comprises: Generating a sending blockchain account corresponding to the sending object in the resource client; Obtaining a sending blockchain address corresponding to the sending blockchain account and a sending account system name corresponding to the sending blockchain account; the sending account system name includes a sending system prefix and a sending system suffix; the sending system suffix is ​​used to indicate the sending business organization to which the sending object belongs, and the sending system prefix is ​​used to indicate the sending object in the sending business organization; The sending blockchain address and the sending account system name are determined as the sending account information; the sending account information has the function of providing the sending object with initiating the resource transfer event.

4. The method according to claim 3, characterized in that The sending blockchain account includes a blockchain public key associated with the sending object; The obtaining the sending blockchain address corresponding to the sending blockchain account and the sending account system name corresponding to the sending blockchain account includes: Address encoding the blockchain public key to generate a sending blockchain address corresponding to the sending blockchain account; Acquire the candidate account system name input by the sending object, authenticate the sending object and the candidate account system name, and obtain an authentication result; If the authentication result indicates that the authentication is successful, the candidate account system name is determined as the sending account system name corresponding to the sending blockchain account.

5. The method according to claim 4, characterized in that The acquiring the candidate account system name input by the sending object, authenticating the sending object and the candidate account system name, and obtaining an authentication result includes: Acquire the candidate account system name input by the sending object; the candidate account system name includes a candidate system prefix and a candidate system suffix; Performing a first authentication on the sending object and the candidate system suffix, generating a first authentication result indicating a successful authentication if the sending object belongs to the candidate business organization indicated by the candidate system suffix, and generating a first authentication result indicating a failed authentication if the sending object does not belong to the candidate business organization indicated by the candidate system suffix; Performing a second authentication on the candidate system prefix, if the candidate business organization represented by the candidate system suffix does not include an account system name whose system prefix is ​​the candidate system prefix, generating a second authentication result indicating a successful authentication, and if the candidate business organization represented by the candidate system suffix includes an account system name whose system prefix is ​​the candidate system prefix, generating a second authentication result indicating a failed authentication; If both the first authentication result and the second authentication result indicate that the authentication is successful, an authentication result representing that the authentication is successful is generated; if the first authentication result or the second authentication result indicates that the authentication is failed, an authentication result representing that the authentication is failed is generated.

6. The method according to claim 3, characterized in that: The generating transaction data for the resource transfer event and sending the transaction data to a blockchain node in the blockchain includes: Obtaining a blockchain account list corresponding to the sending object from a resource server corresponding to the resource client, and displaying the blockchain account list in the resource client; the blockchain account list includes H blockchain accounts corresponding to the sending object; H is a positive integer; the H blockchain accounts include the sending blockchain account; In response to a selection operation on the blockchain account list, obtaining the sending blockchain account selected by the selection operation; the sending blockchain account includes a blockchain private key associated with the sending object; Generate transaction data for the resource transfer event, sign the transaction data using the blockchain private key to obtain signature data, and splice the signature data into the transaction data; The transaction data carrying the signature data is sent to a blockchain node in the blockchain so that the blockchain node verifies the transaction data carrying the signature data.

7. The method according to claim 1, characterized in that The step of obtaining receiving account information corresponding to the resource transfer event in the resource client includes: In response to a resource transfer operation on a resource client, a resource transfer area corresponding to a resource transfer event is displayed in the resource client; In response to an input operation with respect to the resource transfer area, the input receiving account information is displayed in the resource transfer area.

8. The method according to claim 1, characterized in that The step of obtaining receiving account information corresponding to the resource transfer event in the resource client includes: In response to a scan operation for a shared QR code, a receiving blockchain address and a system name input area corresponding to a resource transfer event are displayed in the resource client; the shared QR code is shared by the receiving object to the sending object; In response to an input operation on the system name input area, the input receiving account system name is displayed in the system name input area; the receiving account system name and the receiving blockchain address are used to constitute the receiving account information corresponding to the resource transfer event.

9. The method according to claim 1, characterized in that: The method further comprises: If the verification result indicates that the object to be verified is not the same as the receiving object, a verification failure prompt is displayed in the resource client; Based on the verification failure prompt, an updated resource transfer area corresponding to the resource transfer event is displayed in the resource client; the updated resource transfer area is used to instruct the sending object to re-enter the receiving account information.

10. The method according to claim 3, characterized in that: The sending system suffix includes sending system sub-suffixes corresponding to S levels respectively; S is an integer greater than 1; the sending system sub-suffix corresponding to the highest level among the S levels is used to indicate the sending business organization to which the sending object belongs; the sending system sub-suffixes corresponding to S-1 levels among the S levels except the highest level are used to indicate the sending sub-business organization to which the sending object belongs in the sending business organization; the sending sub-business organizations corresponding to the S-1 levels have a subordinate relationship.

11. The method according to claim 3, characterized in that The resource server corresponding to the resource client is used to store the sending account information; the resource server is used to receive a data acquisition request sent by the blockchain node corresponding to the sending business organization; the data acquisition request is used to obtain the account information corresponding to the object in the sending business organization, the object in the sending business organization includes the sending object, and the account information corresponding to the object in the sending business organization includes the sending account information; The resource server is also used to perform authority detection on the blockchain node corresponding to the sending business organization to obtain an authority detection result; If the authority detection result indicates that the blockchain node corresponding to the sending business organization has the authority to obtain the account information corresponding to the object in the sending business organization, the resource server is also used to return the account information corresponding to the object in the sending business organization to the blockchain node corresponding to the sending business organization.

12. A data processing device based on blockchain, characterized in that: include: An information acquisition module, used to obtain receiving account information corresponding to a resource transfer event in a resource client; The resource transfer event is used to instruct the sending object corresponding to the resource client to transfer the digital assets to the receiving object; the receiving account information includes the receiving blockchain address of the receiving object and the receiving account system name of the object to be verified; the receiving account system name includes a system prefix and a system suffix; The system suffix is ​​used to indicate the business organization to which the object to be verified belongs, and the system prefix is ​​used to indicate the object to be verified in the business organization; An information verification module, used to obtain a verification result for the receiving blockchain address and the receiving account system name; The verification result is obtained by verifying the receiving blockchain address and the receiving account system name; A resource transfer module is used to generate transaction data for the resource transfer event if the verification result indicates that the object to be verified is the same as the receiving object, and send the transaction data to a blockchain node in the blockchain so that the blockchain node processes the transaction data on the chain.

13. A computer device, characterized in that: include: Processor and memory; The processor is connected to the memory, wherein the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 11.

15. A computer program product, characterized in that The computer program product comprises a computer program, which is stored in a computer-readable storage medium and is suitable for being read and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 11.

Images