A blockchain-based transfer method, device and system

Abstract

The application provides a blockchain-based transfer method, device and system, relates to blockchain technology, and comprises the following steps: receiving a transfer request sent by a user based on a user service node, wherein the transfer request contains a transfer token ID and a transfer target user ID; in a blockchain account book, the user information of the transfer token ID is changed to the transfer target user ID by modifying a key-value pair Key-Value database, the storage structure of the key-value pair database is that the Key value is a token ID, and the Value value contains the user information of the token ID; and transaction success information is returned to the user service node. The application changes the key-value pair of the storage structure of the existing blockchain account book into the form of (token ID, token user information), gives up taking the account ID as the primary key, and changes the storage form to taking the token ID as the primary key, so that the dependency between accounts is avoided in a high-concurrency transaction scenario, and the transaction concurrency performance is improved.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and particularly to a blockchain-based transfer method, apparatus, and system. Background Technology

[0002] As blockchain technology matures, its application scenarios are growing rapidly. Most of these scenarios share commonalities in their business models, which can be broadly categorized into account-based models and evidence-based models. Account-based models primarily reflect states and their values ​​in the ledger. The number of states has a cap and won't grow indefinitely. The core of transactions lies in changes to state values, not changes in the number of states. For example, in bank transfers, while accounts may grow over a period, they typically don't exceed the population of the region; the core of the transfer is the change in account balance. Evidence-based models, on the other hand, primarily record data changes in the ledger. The number of states can increase infinitely, without a cap. The core of transactions is the addition of states, not the modification of their values. Examples include bank account statements or system logs.

[0003] In account-based transaction models, high-concurrency scenarios can occur, necessitating consideration of concurrent data read and write operations. For example, consider a ledger containing three state key-value pairs.<a,100> ,<b,10> ,<c,80> This scenario represents three accounts, a, b, and c, with balances of 100, 10, and 80 yuan respectively. When transactions are received sequentially, with a transferring 10 yuan from a to b and b transferring 20 yuan to c, the former involves modifications to states a and b, while the latter involves modifications to states b and c. Both involve modifications to account b. Therefore, transactions must be executed strictly in the order they are received; otherwise, executing the second transaction first will result in failure due to insufficient balance. Thus, modifications to state values ​​in this concurrent transaction scenario must be processed serially. Existing account model systems primarily handle high-concurrency transaction scenarios by constructing a set of transaction dependencies using a directed acyclic graph. This is achieved by processing independent transactions concurrently and dependent transactions serially, thereby improving overall processing performance.

[0004] However, when dealing with high-concurrency transaction scenarios such as a large number of accounts transferring funds to the same account, because these transactions are interdependent and the resulting directed acyclic graph lacks parallel branches, the transactions are still processed serially. In reality, such transaction scenarios could be handled concurrently to improve performance.

[0005] Currently, existing banking blockchain systems borrow from Bitcoin's UTXO model, introducing the concept of tokens to describe the aforementioned state values. For example, if state a has a value of 200, it can be seen as state a possessing two tokens worth 100 each, with each token having a unique ID, similar to a currency's serial number. In this way, the key-value pair of the existing blockchain ledger's storage structure is (account ID, token set). However, this method uses the account ID as the primary key. When dealing with high-concurrency transaction scenarios, the constructed directed acyclic graph is based on the primary key, thus still revealing dependencies between transaction accounts. This leads to serialized transaction processing, impacting transaction processing performance. Summary of the Invention

[0006] In view of this, the present invention provides a blockchain-based transfer method, apparatus and system for effectively improving transaction concurrency performance in high-concurrency transaction scenarios.

[0007] To achieve the above objectives, the present invention employs the following solution:

[0008] In one embodiment of the present invention, a blockchain-based transfer method includes:

[0009] Receive a transfer request sent by a user based on a user service node, wherein the transfer request includes a transfer token ID and a target user ID;

[0010] In the blockchain ledger, the user information to which the transfer token ID belongs is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information to which the token ID belongs.

[0011] Return transaction success information to the user service node.

[0012] In one embodiment of the present invention, a blockchain-based transfer device includes:

[0013] A transfer request receiving unit is used to receive a transfer request sent by a user based on a user service node, wherein the transfer request includes a transfer token ID and a transfer target user ID;

[0014] The transaction execution unit is used to change the user information of the transfer token ID to the target user ID of the transfer by modifying the key-value database in the blockchain ledger. The key value of the key-value database is the token ID, and the value contains the user information of the token ID.

[0015] The receipt unit is used to return transaction success information to the user service node.

[0016] In one embodiment of the present invention, an electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the blockchain-based transfer method described in the above embodiments.

[0017] In one embodiment of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the blockchain-based transfer method described in the above embodiments.

[0018] In one embodiment of the present invention, a computer program product includes a computer program / instructions that, when executed by a processor, implement the steps of the blockchain-based transfer method described in the above embodiments.

[0019] In one embodiment of the present invention, a blockchain-based transfer system includes: a user service node and a blockchain ledger node, wherein the user service node and the blockchain ledger node transmit data through a network communication protocol;

[0020] The user service node sends a transfer request to the blockchain ledger node according to the user's instructions. The transfer request includes the transfer token ID and the transfer target user ID.

[0021] Upon receiving the transfer request, the blockchain ledger node modifies the key-value pair database in the blockchain ledger to change the user information belonging to the transfer token ID to the target user ID. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID. Finally, it returns transaction success information to the user service node.

[0022] The blockchain-based transfer method, apparatus, and system provided in this invention change the key-value pair storage structure of the existing blockchain ledger to a (token ID, token-owning user information) format. It abandons the account ID as the primary key and replaces it with the token ID, thereby avoiding dependencies between accounts in high-concurrency transaction scenarios and effectively improving transaction concurrency performance. For ease of understanding, the existing technology using the account ID as the primary key can be understood as multiple individual entities conducting transfer transactions. For example, individuals a, b, and c each transfer funds to individual d. Therefore, the constructed directed acyclic graph shows that a, b, and c all have dependencies on d, and these transactions are executed sequentially. However, in this invention, using the token ID as the primary key is equivalent to using the currency held by individuals a, b, c, and d as the primary key for transfer transactions. These currencies do not have dependencies; the relationship between currency and individuals is reflected through the value. Therefore, the above transactions can be executed concurrently, effectively improving transaction concurrency performance. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0024] Figure 1 This is a schematic flowchart of a blockchain-based transfer method provided in an embodiment of the present invention;

[0025] Figure 2 This is a flowchart illustrating a blockchain-based transfer method provided in another embodiment of the present invention;

[0026] Figure 3 This is a flowchart illustrating a blockchain-based transfer method provided in another embodiment of the present invention;

[0027] Figure 4 This is a flowchart illustrating a blockchain-based transfer method provided in another embodiment of the present invention;

[0028] Figure 5 This is a schematic diagram of a token splitting process provided by an embodiment of the present invention;

[0029] Figure 6 This is a flowchart illustrating a blockchain-based transfer method provided in another embodiment of the present invention;

[0030] Figure 7 This is a schematic diagram of a token merging process provided by an embodiment of the present invention;

[0031] Figure 8 This is a diagram illustrating a blockchain-based transfer system architecture provided in an embodiment of the present invention.

[0032] Figure 9 This is a schematic diagram of a blockchain-based transfer transaction process provided by an embodiment of the present invention;

[0033] Figure 10 This is a schematic diagram of the structure of a blockchain-based transfer device provided in another embodiment of the present invention;

[0034] Figure 11 A schematic block diagram of the system configuration of an electronic device provided in another embodiment of the present invention. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0036] It should be noted that the blockchain-based transfer method, device, and system disclosed in this application can be used in the field of blockchain technology, or in any field other than blockchain technology. The application field of the process business flow method and device disclosed in this application is not limited.

[0037] To facilitate understanding of the technical solution provided in this application, the relevant content of the technical solution in this application will be explained below. Figure 1 This is a schematic flowchart of a blockchain-based transfer method provided in an embodiment of the present invention. Figure 1 As shown, the blockchain-based transfer method provided in this embodiment may include:

[0038] Step S110: Receive a transfer request sent by a user based on the user service node. The transfer request includes the transfer token ID and the target user ID.

[0039] In this step, the user service node can be deployed in the user's local environment, such as existing in the user's mobile terminal as an APP application. Of course, this embodiment of the invention is not limited to this, and other feasible node deployment methods are also possible, such as self-service terminals located in bank branches. Users can log in to the user service node using a username and password, and initiate a transfer request through the user service node by performing a transfer operation.

[0040] In this embodiment, the content of the transfer request can be "current account A transfers X yuan to target account B". Therefore, the information in the transfer request can include the ID information of current account A, the ID information of target account B, and the transfer amount. Of course, the transfer request can also include verification information for security verification, etc., but this embodiment of the invention does not limit this.

[0041] Step S120: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0042] In this step, the blockchain ledger can be stored using two data structures: blockchain and world state. Blocks in the blockchain can be stored as files, which can include disk file systems or distributed file systems. These files consist of several transaction messages and corresponding state value changes, linked together using hashes to ensure the transaction data is tamper-proof. World state is a proprietary term in blockchain technology, recording various information such as account balances, smart contract bytecode, custom data from various smart contracts, and chain configuration parameters. World state represents the current state, i.e., the current value of each recorded state data. In this embodiment, the world state is stored as a key-value database, used to record all tokens in the current blockchain ledger and their attributes. Specifically, the key value is the token ID, and the value contains the user information associated with that token ID, such as the user ID. Of course, in this embodiment, the value can also include token type, token issuing institution, token issuing institution signature, token face value, etc.

[0043] Step S130: Return transaction success information to the user service node.

[0044] Once the user information corresponding to the token ID is successfully modified in step S120, the transaction success information can be returned to the user service node and displayed to the user via SMS, pop-up window, subscription message, etc.

[0045] In this embodiment, the above steps can be implemented by the blockchain ledger node set on the blockchain network side. The present invention changes the key-value pair of the storage structure in the existing blockchain ledger to the form of (token ID, user information to which the token belongs), abandoning the account ID as the primary key and replacing it with the token ID as the primary key. This avoids the dependency between accounts in high-concurrency transaction scenarios and effectively improves transaction concurrency performance.

[0046] Figure 2 This is a flowchart illustrating a blockchain-based transfer method according to another embodiment of the present invention. Figure 2 As shown, the blockchain-based transfer method provided in this embodiment may include:

[0047] Step S210: Receive the total token amount query request sent by the user based on the user service node.

[0048] Step S220: Return the total token amount information of the user to the user service node according to the query request.

[0049] In this embodiment, steps S210 and S220 can be implemented by a blockchain token service node located on the blockchain network side. This blockchain token service node can provide blockchain token query services, allowing users to query all their token information by accessing the node. Specifically, the blockchain token service node may include a data statistics module and a token service module. The data statistics module constructs a relational database, monitors changes in state data in the blockchain ledger, establishes a correspondence between accounts and tokens in the database, and provides users with blockchain token query services through the token service module.

[0050] In this embodiment, after receiving the user's transfer operation instruction, the user service node will send a token total amount query request to the blockchain token service node to obtain the total amount of tokens on the chain. After receiving the query request, the blockchain token service node will query the database and feed back the obtained token total amount information of the user to the user service node.

[0051] In this embodiment, after receiving the user's transfer operation instruction, the user service node can retrieve the user's token balance in its local storage module. Only when the token balance does not meet the transfer requirements will it send a token total amount query request to the blockchain token service node. When the token balance meets the requirements, it directly proceeds to step S230.

[0052] Step S230: Receive a transfer request sent by a user based on the user service node. The transfer request includes the transfer token ID and the target user ID.

[0053] Step S240: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0054] Step S250: Return transaction success information to the user service node.

[0055] The steps S230 to S250 described above are similar to steps S110 to S130 in the previous embodiments, and will not be repeated here.

[0056] In this embodiment, by changing the key-value pair storage structure of the existing blockchain ledger to the form of (token ID, user information to which the token belongs), the storage format of using the token ID as the primary key is abandoned, thus avoiding inter-account dependencies in high-concurrency transaction scenarios and effectively improving transaction concurrency performance. Furthermore, this embodiment provides token query services by setting up blockchain token service nodes, reducing the resource consumption for users to statistically verify their own tokens and improving the overall operating efficiency of the system.

[0057] Figure 3 This is a flowchart illustrating a blockchain-based transfer method according to another embodiment of the present invention. Figure 3 As shown, the blockchain-based transfer method provided in this embodiment may include:

[0058] Step S310: Receive the total token amount query request sent by the user based on the user service node.

[0059] Step S320: Return the total token amount information of the user to the user service node according to the total token amount query request.

[0060] Step S330: Receive the token synchronization request sent by the user based on the user service node.

[0061] Step S340: Retrieve and return all token information of the user to the user service node according to the token synchronization request.

[0062] In this embodiment, steps S310 to S340 can be implemented by a blockchain token service node set on the blockchain network side. The blockchain token service node can provide blockchain token query services, and users can access all their token information by accessing the blockchain token service node.

[0063] In this embodiment, after receiving the user's transfer operation instruction, the user service node can retrieve the user's token balance in its local storage module. If the token balance does not meet the transfer requirements, it sends a total token balance query request to the blockchain token service node. If the token balance meets the requirements, it directly proceeds to step S350.

[0064] In addition, after the user service node receives the total token amount information returned by the blockchain token service node, it will determine whether the user's account balance meets the transfer requirements. If it does not meet the requirements, the user service node will send a transaction failure message to the user. If it does meet the requirements, the user service node will send a token synchronization request to the blockchain token service node and update the token data in the local storage module according to all the token information of the user returned by the blockchain token service node.

[0065] Step S350: Receive a transfer request sent by the user based on the user service node. The transfer request contains the transfer token ID and the target user ID.

[0066] Step S360: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of this key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0067] Step S370: Return transaction success information to the user service node.

[0068] In this embodiment, by changing the key-value pair storage structure of the existing blockchain ledger to the form of (token ID, user information to which the token belongs), the storage format of using the token ID as the primary key is abandoned, thus avoiding inter-account dependencies in high-concurrency transaction scenarios and effectively improving transaction concurrency performance. Furthermore, this embodiment provides token query services by setting up blockchain token service nodes, reducing the resource consumption for users to statistically verify their own tokens and improving the overall operating efficiency of the system.

[0069] Figure 4 This is a flowchart illustrating a blockchain-based transfer method according to another embodiment of the present invention. Figure 4 As shown, the blockchain-based transfer method provided in this embodiment may include:

[0070] Step S410: Receive the token splitting request sent by the user based on the user service node.

[0071] In this embodiment, when the user service node receives a user's transfer operation instruction, it can query the local storage module to see if the user has a set of tokens that meet the transfer amount. If so, it directly issues a transfer request; otherwise, it issues a token splitting request. The token splitting request can include the token ID to be split and the set of splitting denominations. This embodiment assumes that the user has sufficient current balance. For example, if the user needs to transfer 100 yuan, and the account has token a with a face value of 60, token b with a face value of 40, and token c with a face value of 30, then only tokens a and b need to be transferred to meet the transfer amount, and the user service node can directly issue a transfer request. If the account has token a with a face value of 60, token b with a face value of 20, and token c with a face value of 50, then the transfer amount cannot be met, and the user service node needs to issue a splitting request to split one of the tokens.

[0072] Step S420: Execute the token splitting contract according to the token splitting request, and return the split token set information to the user service node.

[0073] In this embodiment, the specific splitting rules and procedures can be determined by the token issuing institution and defined in the smart contract; this invention does not limit this. Preferably, in this embodiment, a block can be generated in the blockchain network based on the execution result of the token splitting contract, the blockchain ledger can be updated, and then the split token set information can be returned to the user service node.

[0074] Step S430: Receive a transfer request sent by a user based on the user service node. The transfer request contains the transfer token ID and the target user ID.

[0075] Step S440: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0076] Step S450: Return transaction success information to the user service node.

[0077] Further preferred, such as Figure 5 The diagram shown illustrates a token splitting process according to an embodiment of the present invention. The token splitting process includes:

[0078] Step S501: Verify the validity of the parameters in the token splitting request.

[0079] Step S502: Search the token data of the token issuing institution itself to check whether there is an existing set of tokens with the split face value. If it exists, proceed to step S503; if it does not exist, proceed to step S504.

[0080] Step S503: In the key-value pair database, change the user information belonging to the token set with the split face value to the user's ID information. In this embodiment, this step can change the existing tokens originally belonging to the token issuing institution to the user's tokens.

[0081] Step S504: Issue the aforementioned split-denomination tokens to the user. In this embodiment, this step involves directly issuing tokens with the required split-denomination to the user when the token issuing institution itself does not have any existing tokens with split-denominations. For example, if a user needs to split a 10-yuan token into 7-yuan and 3-yuan tokens, but the token issuing institution does not have 7-yuan and 3-yuan tokens, then the institution directly issues 7-yuan and 3-yuan tokens to the user. That is, 7-yuan and 3-yuan tokens are newly generated in the key-value pair database, and their user information is changed to the user's ID information.

[0082] Of course, if the token issuing institution only has a portion of tokens that meet the requirement of splitting the face value, it can change the user information of the tokens that meet the requirement to the user's ID information and issue tokens of the remaining face value to the user.

[0083] Step S505: Change the user information of the above-mentioned token ID to be split to the token issuing institution in the key-value pair database. In this embodiment, the split tokens have been given to the user through steps S503 and S504, so the token issuing institution needs to reclaim the user's tokens to be split through this step.

[0084] In this embodiment, by changing the key-value pair storage structure of the existing blockchain ledger to the form of (token ID, token owner's information), and abandoning the account ID as the primary key, the storage format of using the token ID as the primary key is replaced. This avoids dependencies between accounts in high-concurrency transaction scenarios and effectively improves transaction concurrency performance. Furthermore, this embodiment enhances the flexibility of token transfer transactions by splitting the token.

[0085] Figure 6 This is a flowchart illustrating a blockchain-based transfer method according to another embodiment of the present invention. Figure 6 As shown, the blockchain-based transfer method provided in this embodiment may include:

[0086] Step S610: Receive the token merging request sent by the user based on the user service node.

[0087] In this embodiment, after a user issues a transfer request instruction, the user service node queries the local storage module. If it finds that the user has a large number of tokens, it can issue a token merging request to reduce the number of tokens for the user. The token merging request may contain a set of token IDs that need to be merged.

[0088] Step S620: Execute the token merging contract according to the token merging request and return the merged token set information to the user service node.

[0089] In this embodiment, the specific merging rules and procedures can be determined by the token issuing institution and defined in the smart contract; this invention does not limit this. Preferably, in this embodiment, a block can be generated in the blockchain network based on the execution result of the token merging contract, the blockchain ledger can be updated, and then the merged token set information can be returned to the user service node.

[0090] Step S630: Receive a transfer request sent by a user based on the user service node. The transfer request contains the transfer token ID and the target user ID.

[0091] Step S640: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0092] Step S650: Return transaction success information to the user service node.

[0093] Further preferably, after executing step S620, the token splitting request from the user can be received to split the token, thereby meeting the transfer requirements.

[0094] Further preferred, such as Figure 7 The diagram shown illustrates a token merging process according to an embodiment of the present invention. The token merging process includes:

[0095] Step S701: Verify the validity of the parameters in the token merging request.

[0096] Step S702: Calculate the total face value of the tokens to be merged, and re-divide them according to the face value restriction rules to obtain a merged set of tokens with different face values. These face value restriction rules are also set by the token issuing institution and can be defined in the smart contract.

[0097] Step S703: Search the token issuing institution's own token data to check if there is an existing set of tokens with different face values; if it exists, proceed to step S704; if it does not exist, proceed to step S705.

[0098] Step S704: In the key-value pair database, change the user information of the above-mentioned existing token sets of different face values ​​to the user's ID information.

[0099] Step S705: Issue the remaining tokens to the user.

[0100] Step S706: In the key-value pair database, change the user information of the above-mentioned set of token IDs to be merged to the token issuing institution. In this embodiment, the merged token set has already been given to the user through steps S704 and S705, so this step is needed to reclaim the tokens that the user needs to merge.

[0101] In this embodiment, by changing the key-value pair storage structure of the existing blockchain ledger to the form of (token ID, user information to which the token belongs), the storage format of using the token ID as the primary key is abandoned, thus avoiding inter-account dependencies in high-concurrency transaction scenarios and effectively improving transaction concurrency performance. Furthermore, this embodiment reduces the management difficulty of fragmented tokens by merging tokens.

[0102] To facilitate understanding, the following specific examples illustrate the blockchain-based transfer method, but these are not intended to limit the scope of the method. Figure 8 The diagram illustrates an architecture of a blockchain-based transfer system according to an embodiment of the present invention. The system includes a user service node 801, a blockchain ledger node 802, a blockchain token service node 803, and a CA (Certificate Authority) node 804. The blockchain ledger node 802, blockchain token service node 803, and CA node 804 are deployed on the blockchain network side. The blockchain ledger node 802 and blockchain token service node 803 are interconnected to form a network. The networking and data transmission between the blockchain ledger node 802, blockchain token service node 803, and CA node 804 can utilize the GRPC / GRPCS protocol. The user service node 801 is deployed in the user's local environment, and data transmission between the user service node 801 and the blockchain ledger node 802 and blockchain token service node 803 can utilize the HTTP / HTTPS protocol.

[0103] User service node 801 can provide users with local query services for user tokens, and can also obtain user token data from blockchain token service node 803 through full data synchronization or subscription push. User service node 801 may include a local storage module, a data synchronization module, and a transaction processing module.

[0104] This local storage module provides users with local token storage services, storing the token information of the current user through relational data storage.

[0105] This data synchronization module can update its own token information in the aforementioned local storage module based on on-chain data. For example, it can synchronize its full token information by calling the relevant services of blockchain token service node 803; or it can incrementally update its local token information by subscribing to and listening to the status changes of the tokens involved in its own tokens in blockchain ledger node 802.

[0106] This transaction processing module is used to construct transfer transaction requests.

[0107] The blockchain ledger node 802 and the blockchain token service node 803 can be used to implement the steps of the above-mentioned blockchain-based transfer method.

[0108] The blockchain ledger node 802 can include a communication module, a storage module, a consensus module, a security module, and a contract module.

[0109] This communication module provides external communication services for blockchain ledger node 802.

[0110] This storage module provides data storage services for blockchain ledger node 802, which can be used to store persistent data such as blockchain ledgers and node configuration information.

[0111] This consensus module provides fault tolerance for up to one-third of the Byzantine nodes by integrating the Hotstuff consensus mechanism, which supports pipelined parallelism, ensuring the consistency of the blockchain ledger among the 802 blockchain accounting nodes.

[0112] This security module provides basic security support for blockchain ledger node 802. By applying for certificates from CA node 804 and generating relevant keys, it provides identity authentication services for external nodes and users, as well as data encryption and decryption services, ensuring the legitimacy of the identities of network nodes and users accessing transactions, and protecting the privacy and integrity of data.

[0113] This contract module provides customized transaction processing capabilities. The blockchain ledger management organization defines the core logic of account transactions and ledger read / write rules by writing smart contracts, and deploys them in a secure, isolated environment on the nodes. When a node receives a transaction, the contract is triggered and executed, resulting in a change in the ledger state. This contract module can run transfer transaction contracts, token splitting contracts, and token merging contracts. The transfer transaction contract defines the process of changing the account ownership of a token in a transfer transaction, the token splitting contract defines the process of token splitting transactions, and the token merging contract defines the process of token merging transactions.

[0114] Blockchain token service node 803 provides blockchain token query services, allowing users to access all their tokens. This node may include a data statistics module, which monitors changes in state data within the blockchain ledger by building a relational database. This module establishes a mapping between accounts and tokens in the relational database and provides token statistics query services to the corresponding users. It should be noted that the functionality of blockchain token service node 803 can also be integrated into blockchain ledger node 802. Preferably, blockchain token service node 803 can be asynchronously built on some resource-sufficient nodes using a relational database to provide token statistics and query services to users. This reduces the resource consumption for users to statistically analyze and verify their own tokens, improving the overall system efficiency.

[0115] CA node 804 can provide management services for node and user certificates and identity authentication services.

[0116] Figure 9 The diagram shown illustrates a blockchain-based transfer transaction process according to an embodiment of the present invention. The transfer transaction process includes:

[0117] Step S101: User A sends a transfer request to the local user service node, requesting that account A transfer X yuan to target account B.

[0118] Step S102: When the user service node receives a transfer request initiated by user A, it retrieves the token balance of user A from the local storage module.

[0119] Step S103: The user service node determines whether user A's token balance meets the requirements. If it does, proceed to step S110; otherwise, proceed to step S104.

[0120] Step S104: The user service node sends a total token amount query request to the blockchain token service node.

[0121] Step S105: After receiving the total token amount query request, the blockchain token service node retrieves the relational database and returns the total token amount of user A to the user service node.

[0122] Step S106: The user service node determines whether the total amount of user A's tokens meets the requirements. If it does not meet the requirements, it returns a transaction failure message to user A. If it meets the requirements, it proceeds to step S107.

[0123] Step S107: The user service node sends a token synchronization request to the blockchain service node.

[0124] Step S108: After receiving the token synchronization request, the blockchain token service node retrieves the relational database and returns all token information of user A to the user service node.

[0125] Step S109: The user service node updates the token data in the local storage module based on all the token information received from user A.

[0126] Step S110: The user service node queries the token data of user A in the local storage module.

[0127] Step S111: The user service node determines whether user A has a set of tokens S that meets the transfer limit. If it does, proceed to step S115; otherwise, proceed to step S112.

[0128] Step S112: The user service node initiates a token splitting request to the blockchain ledger node.

[0129] Step S113: After receiving the token splitting request, the blockchain ledger node executes the token splitting contract and returns the split token information to the user service node.

[0130] Step S114: The user service node updates the token data in the local storage module based on the split token information returned by the user service node, and then executes step S110 again.

[0131] Step S115: The user service node constructs a transfer request and sends the transfer request to the blockchain ledger node. The content of the transfer request is to change the account to which the token set S belongs to user B.

[0132] Step S116: The blockchain ledger node executes the transfer transaction according to the transfer request from the user service node, changes the account to which the token set S belongs to user B, and returns the execution result to the user service node.

[0133] Step S117: After receiving the execution result from the blockchain ledger node, the user service node returns a message indicating that the transaction was successful to user A.

[0134] In the transaction process of this embodiment, after the blockchain network receives and executes a transfer transaction or a token splitting transaction, that is, after implementing steps S113 and S116, the blockchain token service node will listen to the changes in the token status on the chain, and then update the database of the correspondence between accounts and tokens in the data statistics module.

[0135] Based on and Figure 1The present invention also provides a blockchain-based transfer device, as described in the following embodiments, which shares the same inventive concept as the blockchain-based transfer method. Since the principle by which this blockchain-based transfer device solves the problem is similar to the aforementioned transfer method, the implementation of this blockchain-based transfer device can refer to the implementation of the blockchain-based transfer method, and repeated details will not be elaborated further.

[0136] Figure 10 This is a schematic diagram of the structure of a blockchain-based transfer device provided in another embodiment of the present invention. Figure 10 As shown, the blockchain-based transfer device may include: a transfer request receiving unit 101, a transaction execution unit 102, and a receipt unit 103, which are connected sequentially.

[0137] The transfer request receiving unit 101 is used to receive a transfer request sent by a user based on a user service node. The transfer request includes a transfer token ID and a transfer target user ID.

[0138] The transaction execution unit 102 is used to change the user information belonging to the transfer token ID to the transfer target user ID by modifying the key-value pair database in the blockchain ledger. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the aforementioned token ID.

[0139] The receipt unit 103 is used to return transaction success information to the user service node.

[0140] In some embodiments, the blockchain-based transfer device may further include a query request receiving unit and a query result feedback unit, wherein:

[0141] The query request receiving unit is used to receive the total token amount query request sent by the user based on the user service node.

[0142] The query result feedback unit is used to return the total token amount information of the user to the user service node according to the query request.

[0143] In some embodiments, the blockchain-based transfer device may further include a synchronization request receiving unit and a synchronization result feedback unit, wherein:

[0144] The synchronization request receiving unit is used to receive token synchronization requests sent by users based on user service nodes.

[0145] The synchronization result feedback unit is used to retrieve and return all token information of the user to the user service node according to the token synchronization request.

[0146] In some embodiments, the blockchain-based transfer device may further include a split request receiving unit and a split execution unit, wherein:

[0147] The token splitting request receiving unit is used to receive token splitting requests sent by users based on user service nodes. The token splitting request may include the token ID to be split and the set of splitting face values.

[0148] The splitting execution unit is used to execute the token splitting contract according to the token splitting request and return the split token set information to the user service node.

[0149] In some embodiments, the split execution unit may further include a first verification module, a first query module, a split execution module, and a split feedback module, wherein:

[0150] The first verification module is used to verify the legality of the parameters in the token splitting request.

[0151] The first query module is used to retrieve the token data of the token issuing institution itself and to query whether there is an existing set of tokens with the split face value.

[0152] The split execution module is configured to, when the query result of the first query module shows that there is an existing set of tokens with the split face value, change the user information belonging to the token set with the split face value to the user's ID information in the key-value pair database; when the query result of the first query module shows that there is no existing set of tokens with the split face value, issue the token with the split face value to the user; and change the user information belonging to the ID of the token to be split to the token issuing institution in the key-value pair database.

[0153] The split feedback module is used to return the split token set information to the user service node.

[0154] In some embodiments, the split feedback module may further include a consensus submodule, an update submodule, and a feedback submodule, wherein...

[0155] The consensus submodule is used to reach a consensus and generate blocks in the blockchain network based on the execution results of the split execution module.

[0156] The update submodule is used to update the blockchain ledger based on the execution result of the split execution module.

[0157] The feedback submodule is used to return the split token set information to the user service node.

[0158] In some embodiments, the blockchain-based transfer device may further include a merge request receiving unit and a merge execution unit, wherein:

[0159] The merge request receiving unit is used to receive token merge requests sent by users based on user service nodes. The token merge request may contain a set of token IDs that need to be merged.

[0160] The merge execution unit is used to execute the token merge contract according to the token merge request and return the merged token set information to the user service node.

[0161] In some embodiments, the merge execution unit may further include a second verification module, a calculation module, a second query module, a merge execution module, and a merge feedback module, wherein:

[0162] The second verification module is used to verify the legality of the parameters in the token merging request;

[0163] The calculation module is used to calculate the total face value of the tokens that need to be merged, and then re-divide them according to the face value limit rules to obtain a set of tokens with different face values ​​after merging.

[0164] The second query module is used to retrieve the token data of the token issuing institution itself and to query whether there is an existing set of tokens with different face values.

[0165] The merge execution module is configured to, when the query result of the second query module shows that there is an existing set of tokens of different denominations, change the user information belonging to the existing set of tokens of different denominations in the key-value pair database to the user's ID information; when the query result of the second query module shows that there is no existing set of tokens of different denominations, issue the remaining insufficient tokens to the user; and change the user information belonging to the set of token IDs to be merged in the key-value pair database to the token issuing institution.

[0166] The merge feedback module is used to return the merged token set information to the user service node.

[0167] In this embodiment, by changing the key-value pair storage structure of the existing blockchain ledger to the form of (token ID, user information to which the token belongs), the storage format of using the token ID as the primary key is abandoned, thereby avoiding inter-account dependencies in high-concurrency transaction scenarios and effectively improving transaction concurrency performance. Furthermore, this embodiment can also increase the freedom of token transfer transactions by splitting tokens and reduce the management difficulty of fragmented tokens by merging tokens.

[0168] From a hardware perspective, in order to avoid inter-account dependencies and improve transaction concurrency performance in high-concurrency transaction scenarios, this application provides an embodiment of an electronic device for implementing all or part of the aforementioned blockchain-based transfer method. The electronic device specifically includes the following components:

[0169] The system comprises a processor, memory, a communications interface, and a bus; wherein the processor, memory, and communications interface communicate with each other via the bus; the communications interface is used to realize information transmission between the blockchain-based transfer device and core business systems, user terminals, and related databases and other related devices; the logic controller can be a desktop computer, tablet computer, or mobile terminal, etc., and this embodiment is not limited to these. In this embodiment, the logic controller can be implemented with reference to the embodiments of the blockchain-based transfer method and the blockchain-based transfer device in the embodiments, the content of which is incorporated herein, and repeated details will not be described again.

[0170] It is understood that the user terminal may include smartphones, tablet computers, network set-top boxes, portable computers, desktop computers, personal digital assistants (PDAs), in-vehicle devices, smart wearable devices, etc. Among these, the smart wearable devices may include smart glasses, smartwatches, smart bracelets, etc.

[0171] In practical applications, the blockchain-based transfer method can be partially executed on the electronic device side as described above, or all operations can be completed on the client device or server device. The choice can be made based on the processing power of the client device or server device, as well as the limitations of the user's usage scenario. This application does not impose any limitations on this. If all operations are completed on the client device or server device, the client device or server device may further include a processor.

[0172] The aforementioned client or server devices may have a communication module (i.e., a communication unit) that can communicate with remote servers or clients to achieve data transmission. The server may include a server on the task scheduling center side; in other implementation scenarios, it may also include a server on an intermediate platform, such as a server on a third-party server platform that has a communication link with the task scheduling center server. The server may include a single computer device, a server cluster consisting of multiple servers, or a distributed server structure.

[0173] Figure 11 This is a schematic block diagram illustrating the system configuration of an electronic device 1100 provided in another embodiment of the present invention. (See diagram below.) Figure 11 As shown, the electronic device 1100 may include a central processing unit 1110 and a memory 1120; the memory 1120 is coupled to the central processing unit 1110. It is worth noting that... Figure 11This is an example; other types of structures can also be used to supplement or replace this structure to achieve telecommunications functions or other functions.

[0174] In one embodiment, the blockchain-based transfer method functionality can be integrated into the central processing unit 1110. The central processing unit 1110 can be configured to perform the following control:

[0175] Step S110: Receive a transfer request sent by a user based on the user service node. The transfer request includes the transfer token ID and the target user ID.

[0176] Step S120: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0177] Step S130: Return transaction success information to the user service node.

[0178] As can be seen from the above description, the electronic device provided in the embodiments of the present invention changes the key-value pairs in the storage structure of the existing blockchain ledger to the form of (token ID, user information to which the token belongs), abandoning the account ID as the primary key and replacing it with the token ID as the primary key. This avoids the dependency between accounts in high-concurrency transaction scenarios and effectively improves transaction concurrency performance.

[0179] In another embodiment, the transfer device can be configured separately from the central processing unit 1110. For example, the transfer device can be configured as a chip connected to the central processing unit 1110, and the above-mentioned transfer method function can be implemented through the control of the central processing unit.

[0180] like Figure 11 As shown, the electronic device 1100 may further include: a communication module 1130, an input unit 1140, an audio processor 1150, a display 1160, and a power supply 1170. It is worth noting that the electronic device 1100 does not necessarily need to include these components. Figure 11 All components shown; in addition, the electronic device 1100 may also include Figure 11 For components not shown, please refer to existing technologies.

[0181] like Figure 11 As shown, the central processing unit 1110, sometimes also referred to as a controller or operation control, may include a microprocessor or other processor device and / or logic device. The central processing unit 1110 receives input and controls the operation of various components of the electronic device 1100.

[0182] The memory 1120 may be one or more of the following: a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable device. It may store information related to the aforementioned transfer method, and may also store programs for executing that information. The central processing unit 1110 may execute the program stored in the memory 1120 to perform information storage or processing, etc.

[0183] Input unit 1140 provides input to central processing unit 1110. This input unit 1140 may be, for example, a keypad or touch input device. Power supply 1170 provides power to electronic device 1100. Display 1160 displays images and text. This display may be, for example, an LCD display, but is not limited thereto.

[0184] The memory 1120 can be a solid-state memory, such as a read-only memory (ROM), random access memory (RAM), SIM card, etc. It can also be a memory that retains information even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROMs. The memory 1120 can also be some other type of device. The memory 1120 includes a buffer memory 1121 (sometimes referred to as a buffer). The memory 1120 may include an application / function storage unit 1122 for storing application programs and function programs or processes for executing the operation of the electronic device 1100 via the central processing unit 1110.

[0185] The memory 1120 may also include a data storage unit 1123 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 1124 of the memory 1120 may include various drivers for the electronic device for communication functions and / or for performing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0186] The communication module 1130 is a transmitter / receiver 1130 that transmits and receives signals via antenna 1131. The communication module (transmitter / receiver) 1130 is coupled to the central processing unit 1110 to provide input signals and receive output signals, which can be the same as in a conventional mobile communication terminal.

[0187] Based on different communication technologies, multiple communication modules 1130 can be configured in the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) 1130 is also coupled to a speaker 1151 and a microphone 1152 via an audio processor 1150 to provide audio output via the speaker 1151 and receive audio input from the microphone 1152, thereby enabling typical telecommunications functions. The audio processor 1150 may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor 1150 is coupled to a central processing unit 1110, enabling on-device recording via the microphone 1152 and on-device playback of stored sound via the speaker 1151.

[0188] Embodiments of this application also provide a computer-readable storage medium capable of implementing all steps of the blockchain-based transfer method with a server or client as the execution subject in the above embodiments. The computer-readable storage medium stores a computer program that, when executed by a processor, implements all steps of the blockchain-based transfer method with a server or client as the execution subject in the above embodiments. For example, when the processor executes the computer program, it implements the following steps:

[0189] Step S110: Receive a transfer request sent by a user based on the user service node. The transfer request includes the transfer token ID and the target user ID.

[0190] Step S120: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0191] Step S130: Return transaction success information to the user service node.

[0192] As can be seen from the above description, the computer-readable storage medium provided in this application embodiment changes the key-value pairs in the storage structure of the existing blockchain ledger to the form of (token ID, user information to which the token belongs), abandoning the account ID as the primary key and replacing it with the token ID as the primary key. This avoids the dependency between accounts in high-concurrency transaction scenarios and effectively improves transaction concurrency performance.

[0193] Embodiments of this application also provide a computer program product capable of implementing all steps of the blockchain-based transfer method in the above embodiments, where the execution subject is a server or a client. When executed by a processor, this computer program / instruction implements the steps of the blockchain-based transfer method. For example, the computer program / instruction implements the following steps:

[0194] Step S110: Receive a transfer request sent by a user based on the user service node. The transfer request includes the transfer token ID and the target user ID.

[0195] Step S120: In the blockchain ledger, the user information belonging to the above-mentioned transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID.

[0196] Step S130: Return transaction success information to the user service node.

[0197] As can be seen from the above description, the computer program product provided in this application embodiment changes the key-value pair of the storage structure in the existing blockchain ledger to the form of (token ID, user information to which the token belongs), abandoning the account ID as the primary key and changing it to the token ID as the primary key. This avoids the dependency between accounts in high-concurrency transaction scenarios and effectively improves transaction concurrency performance.

[0198] This invention also provides a blockchain-based transfer system, comprising a user service node and a blockchain ledger node, which transmit data via a network communication protocol. The user service node sends a transfer request to the blockchain ledger node according to user instructions. The transfer request includes a transfer token ID and a target user ID. Upon receiving the transfer request, the blockchain ledger node modifies the key-value pair database in the blockchain ledger to change the user information belonging to the transfer token ID to the target user ID. In the key-value pair database, the key value is the token ID, and the value contains the user information belonging to the token ID. Finally, the system returns transaction success information to the user service node.

[0199] In summary, the blockchain-based transfer method, apparatus, and system of this invention, by changing the key-value pair storage structure of the existing blockchain ledger to a (token ID, token-owning user information) format, abandons the account ID as the primary key and replaces it with the token ID as the primary key. This avoids inter-account dependencies in high-concurrency transaction scenarios and effectively improves transaction concurrency performance. Furthermore, this embodiment can provide token query services by setting up blockchain token service nodes, reducing the resource consumption of users in statistically verifying their own tokens and improving the overall system operating efficiency. Secondly, this embodiment can increase the freedom of token transfer transactions by splitting tokens and reduce the management difficulty of fragmented tokens by merging tokens.

[0200] In the description of this specification, the references to "an embodiment," "a specific embodiment," "some embodiments," "for example," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. The order of steps involved in the various embodiments is used to illustrate the implementation of the present invention, and the order of steps is not limited and may be adjusted as needed.

[0201] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0202] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0203] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0204] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0205] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A blockchain-based transfer method, characterized in that, include: Receive a transfer request sent by a user based on a user service node, wherein the transfer request includes a transfer token ID and a target user ID; In the blockchain ledger, the user information belonging to the transfer token ID is changed to the transfer target user ID by modifying the key-value pair database. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID. The key-value pair of the storage structure is a storage format with the token ID as the primary key. Return transaction success information to the user service node; The step of modifying the key-value database to change the user information belonging to the transfer token ID to the transfer target user ID includes: if a transfer token ID identical to the transfer token ID contained in the transfer request is found in the key-value database, then the user information belonging to the transfer token ID in the key-value database is changed to the transfer target user ID received along with the transfer token ID.

2. The blockchain-based transfer method according to claim 1, characterized in that, Before receiving the transfer request sent by the user based on the user service node, the process also includes: Receive total token amount query requests sent by users based on user service nodes; The total token amount information of the user is returned to the user service node according to the query request.

3. The blockchain-based transfer method according to claim 1, characterized in that, Before receiving the transfer request sent by the user based on the user service node, the method further includes: receiving the token synchronization request sent by the user based on the user service node; Based on the token synchronization request, retrieve and return all token information of the user to the user service node.

4. The blockchain-based transfer method according to claim 1, characterized in that, Before receiving the transfer request sent by the user based on the user service node, the process also includes: Receive token splitting requests sent by users based on user service nodes; Execute the token splitting contract according to the token splitting request, and return the split token set information to the user service node.

5. The blockchain-based transfer method according to claim 4, characterized in that, The token splitting request includes the token ID to be split and the set of splitting face values.

6. The blockchain-based transfer method according to claim 5, characterized in that, The step of executing the token splitting contract according to the token splitting request includes: Verify the validity of the parameters in the token splitting request; Search the token data of the token issuing institution itself to check whether there is an existing set of tokens with the split face value; If it exists, then in the key-value pair database, change the user information of the token set to which the split face value belongs to the user's ID information; If it does not exist, then issue the token with the split face value to the user; In the key-value database, change the user information of the token ID to be split to the token issuing institution.

7. The blockchain-based transfer method according to claim 4, characterized in that, The step of returning the split token set information to the user service node includes: reaching consensus and producing a block in the blockchain network based on the execution result of the token splitting contract, updating the blockchain ledger, and returning the split token set information to the user service node.

8. The blockchain-based transfer method according to claim 1, characterized in that, Before receiving the transfer request sent by the user based on the user service node, the process also includes: Receive token merging requests sent by users based on user service nodes; The token merging contract is executed according to the token merging request, and the merged token set information is returned to the user service node.

9. The blockchain-based transfer method according to claim 8, characterized in that, The token merge request contains a set of token IDs to be merged; the execution of the token merge contract according to the token merge request includes: Verify the validity of the parameters in the token merging request; Calculate the total face value of the tokens to be merged, and then re-divide them according to the face value limit rules to obtain a set of tokens with different face values ​​after merging. Search the token issuing institution's own token data to check if there is an existing set of tokens with different face values; If it exists, then in the key-value pair database, change the user information of the set of tokens with different face values ​​in the existing stock to the user's ID information; If it does not exist, then issue the remaining insufficient tokens to the user; In the key-value database, change the user information of the set of token IDs to be merged to the token issuing institution.

10. A blockchain-based transfer device, characterized in that, include: A transfer request receiving unit is used to receive a transfer request sent by a user based on a user service node, wherein the transfer request includes a transfer token ID and a transfer target user ID; The transaction execution unit is used to modify the key-value pair database in the blockchain ledger to change the user information belonging to the transfer token ID to the target user ID of the transfer. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID. The key-value pair of the storage structure is a storage format with the token ID as the primary key. The receipt unit is used to return transaction success information to the user service node; The step of modifying the key-value database to change the user information belonging to the transfer token ID to the transfer target user ID includes: if a transfer token ID identical to the transfer token ID contained in the transfer request is found in the key-value database, then the user information belonging to the transfer token ID in the key-value database is changed to the transfer target user ID received along with the transfer token ID.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the blockchain-based transfer method according to any one of claims 1 to 9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the blockchain-based transfer method according to any one of claims 1 to 9.

13. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the blockchain-based transfer method according to any one of claims 1 to 9.

14. A blockchain-based transfer system, characterized in that, include: User service nodes and blockchain ledger nodes transmit data via a network communication protocol; The user service node sends a transfer request to the blockchain ledger node according to the user's instructions. The transfer request includes the transfer token ID and the transfer target user ID. Upon receiving the transfer request, the blockchain ledger node modifies the key-value pair database in the blockchain ledger to change the user information belonging to the transfer token ID to the target user ID. In the storage structure of the key-value pair database, the key value is the token ID, and the value value contains the user information belonging to the token ID. The key-value pair of the storage structure is a storage format with the token ID as the primary key. Finally, a transaction success message is returned to the user service node. The step of modifying the key-value database to change the user information belonging to the transfer token ID to the transfer target user ID includes: if a transfer token ID identical to the transfer token ID contained in the transfer request is found in the key-value database, then the user information belonging to the transfer token ID in the key-value database is changed to the transfer target user ID received along with the transfer token ID.

Images