Blockchain-based blockchain transfer transaction method and related device

Abstract

The embodiment of the application belongs to the technical field of blockchain transfer transaction, and relates to a blockchain transfer transaction method based on a blockchain, which comprises the following steps: when receiving a plurality of transfer transaction requests, obtaining the block height and the block hash of a known blockchain system as a trust root; performing transaction sorting on each transfer transaction request according to the trust root to obtain a transaction number of each transfer transaction request; sorting the transfer transaction cases located at the same block height according to the transaction number to obtain a transaction sequence; and executing each transfer transaction request according to the transaction sequence. The application also provides a blockchain transfer transaction device based on a blockchain, a computer device and a storage medium. The method greatly improves the performance of the blockchain transfer transaction.

Description

Technical Field

[0001] The present application relates to the field of blockchain transfer transaction technology, and in particular to a blockchain transfer transaction method, device, computer equipment and storage medium based on blockchain. Background Art

[0002] Using blockchain for transaction settlement offers the advantages of reliable and traceable on-chain data, enabling instant settlement. However, blockchain system performance is a concern. Blockchain systems maintain data consistency through consensus algorithms. Transactions are processed linearly, following the order in which they reach consensus nodes. Changes in data state depend on the previous state information and can only be made once within a block. This means that an account can only make one transaction within the same block. If multiple transactions are made, the subsequent transactions will fail. However, this happens frequently in the real world. For example, if A transfers money to B and C simultaneously, as long as the available balance in A's account exceeds the transfer amount to B and C's accounts, the transfer will be successful. Summary of the Invention

[0003] Based on this, in response to the above technical problems, the present application provides a blockchain-based blockchain transfer transaction method, device, computer equipment and storage medium to solve the technical problem in the existing technology that transactions are processed linearly in the order of reaching the consensus node, the change of data status needs to rely on the previous status information, and can only be changed once in a block, resulting in an account being able to only make one transaction in the same block.

[0004] A blockchain-based blockchain transfer transaction method, the method comprising:

[0005] When receiving multiple transfer transaction requests, obtain the block height and block hash of the known blockchain system as the root of trust;

[0006] Sort the transfer transaction requests according to the trust root to obtain a transaction number for each transfer transaction request;

[0007] Sort the transfer transactions at the same block height according to the transaction number to obtain the transaction order; and

[0008] Execute each transfer transaction request according to the transaction order.

[0009] A blockchain-based blockchain transfer transaction device, the device comprising:

[0010] The verification module is used to obtain the block height and block hash of the known blockchain system as the root of trust when receiving multiple transfer transaction requests;

[0011] a first sorting module, configured to sort each transfer transaction request according to the trust root, and obtain a transaction number of each transfer transaction request;

[0012] A second sorting module is configured to sort the transfer transactions at the same block height according to the transaction number to obtain a transaction order; and

[0013] The transfer execution module is used to execute each transfer transaction request according to the transaction sequence.

[0014] A computer device includes a memory and a processor, as well as computer-readable instructions stored in the memory and executable on the processor. When the processor executes the computer-readable instructions, the steps of the above-mentioned blockchain-based blockchain transfer transaction method are implemented.

[0015] A computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the above-mentioned blockchain-based blockchain transfer transaction method.

[0016] In the above-mentioned blockchain-based blockchain transfer transaction method, in order to address the technical problems existing in the prior art, in some embodiments, the known blockchain system block height and block hash are used as the trust root to sort transactions, and transactions at the same block height are sorted using transaction numbers. Relying on this transaction order rather than the historical status of the data, transfer transactions can be executed concurrently, thereby improving blockchain performance. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 A schematic diagram of the application environment of a blockchain-based blockchain transfer transaction method;

[0019] Figure 2 A flowchart of a blockchain-based transfer transaction method;

[0020] Figure 3 for Figure 2 Schematic diagram of the overall process of transfer transactions;

[0021] Figure 4 A schematic diagram of a blockchain-based blockchain transfer transaction device;

[0022] Figure 5FIG. 1 is a schematic diagram of a computer device according to an embodiment. DETAILED DESCRIPTION

[0023] Unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of the application are for the purpose of describing specific embodiments only and are not intended to limit this application. The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0024] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0025] In order to make the purpose, technical solutions and advantages of this application more clear, the present application is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0026] The blockchain-based blockchain transfer transaction method provided by the embodiment of the present invention can be applied to Figure 1 In the application environment shown, the application environment may include a terminal 102, a network, and a server 104. The network is used to provide a communication link medium between the terminal 102 and the server 104. The network may include various connection types, such as wired or wireless communication links or optical fiber cables.

[0027] The user can use the terminal 102 to interact with the server 104 via the network to receive or send messages, etc. Various communication client applications can be installed on the terminal 102, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0028] Terminal 102 can be various electronic devices with a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, Moving Picture Experts Group Audio Layer 3), MP4 (Moving Picture Experts Group Audio Layer IV, Moving Picture Experts Group Audio Layer 4) players, laptop computers and desktop computers, etc.

[0029] The server 104 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal 102 .

[0030] It should be noted that the blockchain-based blockchain transfer transaction method provided in the embodiment of the present application is generally executed by the server / terminal. Accordingly, the blockchain-based blockchain transfer transaction device is generally set in the server / terminal device.

[0031] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments in which tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0032] It should be understood that Figure 1 The number of terminals, networks, and servers in the embodiment is merely illustrative. Any number of terminals, networks, and servers may be used as required.

[0033] The terminal 102 communicates with the server 104 via a network. The terminal 102 and the server 104 are connected via a network, which can be a wired network or a wireless network. The terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices. The server 104 can be implemented as an independent server or a server cluster consisting of multiple servers.

[0034] In one embodiment, Figure 2 As shown, a blockchain transfer transaction method based on blockchain is provided, and the method is applied to Figure 1 The server in the example is used as an example to illustrate the following steps:

[0035] Step 202: When receiving multiple transfer transaction requests, obtain the block height and block hash of the known blockchain system as the trust root; and

[0036] Step 204: sorting the transfer transaction requests according to the trust root to obtain a transaction number for each transfer transaction request;

[0037] Step 206: sort the transfer transactions at the same block height according to the transaction number to obtain a transaction order; and

[0038] Step 208: Execute each transfer transaction request according to the transaction order.

[0039] like Figure 3 As shown in the diagram of the overall transfer transaction process, blockchains have numerous nodes, and each round of consensus is costly. Therefore, blockchains bundle multiple transactions into a single block, then reach consensus on the block and record it to increase processing capacity. However, concurrently executing multiple transactions within the same block can lead to the following scenario: A transfers 10 gold coins to B, and later, A transfers 20 gold coins to C. Both transactions are bundled into the same block. Account A, as shown on the blockchain, has 100 gold coins. A transfers 10 gold coins to B, expecting to have 90 gold coins after the transaction. However, when A transfers to C, the information that A only has 90 gold coins remaining is not available. Instead, the information indicates that A currently has 100 gold coins on the blockchain, and that the expected remaining amount after the transfer to C is 80 gold coins. There is no problem with both transactions, but when executing the transaction record book, if the transfer from A to B is received first, this transfer can be recorded normally. When executing the transfer from A to C, it is found that the balance of A's account is 90, which is different from the expected 100, and the balance of A's account after the transfer is 70, which is also different from the expected 80. At this time, the transfer from A to C fails the verification and cannot be recorded in this block. If the transfer from A to C is executed first, it can succeed, but the transfer from A to B will fail the verification.

[0040] Block-based transaction bundling and concurrent execution can improve performance, but requires no state dependencies between transactions. For state-dependent transactions, only one transaction can be included in the same block. In this example, if A transfers funds to B and C, both transactions can be executed as long as A's balance is sufficient. However, in practice, these two transactions cannot be completed in the same block. The problem is that this method relies on on-chain data state, and changing data state requires verifying the previous state of the data. Therefore, it is impossible to perform multiple data state changes based on the same historical data state simultaneously. Therefore, we have constructed a new trust method that no longer relies on historical data state, but instead relies on known blockchains for transaction sorting, allowing state-dependent transactions to be executed concurrently in the same block.

[0041] Concurrent transactions require knowing the order of transactions. Because local times vary between nodes, the order of transactions cannot be determined based on the time they occurred locally. Currently, most common blockchain systems prioritize transactions based on the time they were submitted to the blockchain. However, transactions arriving at the blockchain are subject to network latency, making ordering impossible. Here, we design a method that relies on the block height and hash value of an existing blockchain system, regardless of local time or arrival time. Instead, we rely on the block height and hash value of each node in the blockchain, which are available to all nodes.

[0042] Because it's impossible to obtain the future block height and corresponding block hash value of a known blockchain system in advance, it's impossible to forge a future time. However, we can specify an existing block height and hash value of a known blockchain system. This specified block height and hash value can be used to determine the order of account transactions. You can use the current block height or a significantly later block height, but using a significantly later block height is not recommended. Transactions require a validity period, which is also calculated based on the block height. If a block is generated every three seconds and the validity period is five days, the transaction will be invalid after 5*24*3600 / 3=144,000 blocks have passed since the specified block height.

[0043] Transaction concurrency does not rely on on-chain state, allowing us to include multiple transfers from the same account in a single block. These transactions are sorted by the block height of the known blocks they map to. Transactions mapped to the same block height are sorted by transaction number. With transaction ordering, we can calculate and verify the following information before packaging transactions: Is the account balance + the amount of gold coins received in this block minus the amount of gold coins transferred in this block greater than 0? If it is less than 0, transactions corresponding to the subsequent block heights are removed, and only those that can be processed are included. Transfers and receipts mapped to the same block cannot be sorted, so when removing transactions, they are removed entirely based on the known blocks they map to. When recording accounts, the balance increases and decreases for all transactions in the block are calculated. If no account has insufficient balance, the final account balance is recorded directly. Transactions are recorded as detailed transactions, without individual settlements. If an attacker maliciously discovers insufficient balances during transaction recording, all transactions in the block are rolled back.

[0044] Among them, this blockchain needs to rely on the block height of a known blockchain as the source of time information. The known blockchain can be a public chain or a blockchain built by itself and trusted by the participants of this blockchain. The participants of this blockchain can obtain the latest blockchain height and blockchain hash value information from the known blockchain.

[0045] Transaction order: The transaction needs to include the latest block height and block hash value of the known blockchain, as well as the transaction sequence number of the account corresponding to this transaction at the current known block height. Starting from 1, 1 represents the first transaction of this account at a specific block height of the known blockchain, and the second transaction is recorded as sequence number 2. This constitutes a strict transaction sequence. For different block heights, the block height is used for sorting, and for the same block height, the transaction number corresponding to the block is used for sorting.

[0046] The transaction validity period uses the block height of the known blockchain as the transaction time. However, different nodes may obtain different latest block heights. In order to prevent the use of old block heights, a validity period is set for the transaction. For example, it is valid within 10,000 blocks from the current block. After the block height is exceeded, if the transaction has not been executed and included in the ledger, the transaction is deemed invalid.

[0047] Transaction content validity: The transaction must include the known blockchain block height and block hash value, transaction validity period, transaction sequence number, and transaction initiator signature information. If the known blockchain block height and block hash value specified by the node do not match, or the transaction validity period has expired, or the transaction signature is invalid, the submitted transaction will be considered invalid.

[0048] The parallel processing method for transfer transactions ensures that transactions that meet both time validity and content validity are processed in the order in which they are processed. Before transactions are grouped into the same block, the balance and transfer amount are statistically calculated and verified. If the balance does not meet the transfer amount, the excess transaction is excluded from the block for future processing. The transaction verification system does not rely on the original account balance data or the remaining balance data after the transfer to ensure transaction validity. The order of transactions is not determined by the time it arrives at the node, but rather by the actual order of transactions within the known blockchain specified by the transaction account. Parallel processing allows multiple transactions from the same account to be processed within the same block, improving the concurrent transaction processing performance of the blockchain system.

[0049] Transactions are processed in the order in which they are packaged. To prioritize certain transactions, transaction initiators can prioritize transactions by forwarding them to older, known block heights. There are no transaction continuity requirements; transactions can be unexecuted transactions corresponding to any historical block height within their validity period. The execution of a transaction forwarded to a new block height on a known blockchain does not affect the execution of transactions forwarded to older, known block heights. Transactions with different transaction numbers at the same block height can be processed intermittently. For example, if a transaction is excluded from a block due to a transfer limit, the remaining transactions can still proceed. Transactions do not need to be strictly consecutive in time.

[0050] Prevention method for replay attacks: The account will record the transfer details table. New transfer transactions need to be verified against the known block height value and block hash value as well as the corresponding transaction sequence number and transaction content to see if they are already in the transfer details table. If relevant transaction records exist, they will not be processed.

[0051] To prevent double-spending attacks, each transaction has a different sequence number, a different known block height, or different transaction numbers at the same known block height, ensuring double spending is impossible. If two transactions with the same sequence number and the same block height are received from the same account, and the transaction signatures pass validation, it will be considered a double-spending operation. Only the first transaction received will be executed, and the initiator of the transaction will be penalized for the violation by deducting the agreed amount from their account.

[0052] Preventing insufficient balance attacks: All transfer transactions included in a block must meet the following conditions: Account Balance + Receivable >= Transfer Amount. Verification is performed by the transaction packaging node. If a packaging node maliciously includes a transaction where Account Balance + Receivable < Transfer Amount, an error will occur during the node's accounting and settlement, causing the node to roll back the operation to the normal block height and discard the execution results. To prevent this attack, malicious packaging nodes that disrupt normal transactions will be penalized and deducted an agreed amount.

[0053] In the above-mentioned blockchain-based blockchain transfer transaction method, in order to address the technical problems existing in the prior art, in some embodiments, the known blockchain system block height and block hash are used as the time source for transaction sorting, and transactions at the same block height are sorted using transaction numbers. Relying on this transaction order rather than the historical status of the data, transfer transactions can be executed concurrently, thereby improving blockchain performance.

[0054] It should be understood that although Figure 2 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figure 2 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages do not necessarily have to be executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages does not have to be sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0055] In one embodiment, Figure 4 As shown, a blockchain-based blockchain transfer transaction device is provided, which corresponds one-to-one to the blockchain-based blockchain transfer transaction method in the above embodiment. The blockchain-based blockchain transfer transaction device includes:

[0056] Verification module 402 is configured to obtain the block height and block hash of a known blockchain system as a trust root upon receiving multiple transfer transaction requests;

[0057] A first sorting module 404 is configured to sort each transfer transaction request according to the trust root to obtain a transaction number for each transfer transaction request;

[0058] The second sorting module 406 is configured to sort the transfer transactions at the same block height according to the transaction number to obtain a transaction order; and

[0059] The transfer execution module 408 is configured to execute each transfer transaction request according to the transaction sequence.

[0060] Furthermore, the transfer execution module 408 includes:

[0061] The first execution submodule is configured to sort and execute the transfer transaction requests in accordance with the transaction sequence if the transfer transaction requests meet the transaction time validity and transaction content validity.

[0062] Furthermore, the transfer execution module 408 further includes:

[0063] The second execution submodule is configured to execute unexecuted transfer transaction requests corresponding to any block height when each transfer transaction request meets the validity of the transaction time and the validity of the transaction content, and to perform interval processing on transfer transaction requests with different transaction numbers at the same block height.

[0064] Furthermore, the transfer execution module 408 further includes:

[0065] The third execution submodule is configured to abandon processing the transfer transaction request if the transaction number and transaction content corresponding to the transfer transaction request are already in the transfer details table.

[0066] In the above-mentioned blockchain-based blockchain transfer transaction device, in order to address the technical problems existing in the prior art, in some embodiments, the known blockchain system block height and block hash are used as the trust root to sort transactions, and transactions at the same block height are sorted using transaction numbers. Relying on this transaction order rather than the historical status of the data, transfer transactions can be executed concurrently, thereby improving blockchain performance.

[0067] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, memory, a network interface, and a database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer-readable instructions, and a database. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in the non-volatile storage medium. The database of the computer device can be used to store a transfer transaction details table. The network interface of the computer device is used to communicate with an external terminal via a network connection. When executed by the processor, the computer-readable instructions implement a blockchain-based blockchain transfer transaction method.

[0068] Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0069] In one embodiment, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the steps of the blockchain-based blockchain transfer transaction method in the above embodiment are implemented, such as Figure 2 Steps 202 to 208 shown, or when the processor executes the computer-readable instructions, implement the functions of each module / unit of the blockchain-based blockchain transfer transaction device in the above embodiment, for example Figure 4 The functions of modules 402 to 408 are shown.

[0070] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing related hardware through computer-readable instructions, and the computer-readable instructions can be stored in a non-volatile computer-readable storage medium. When the computer-readable instructions are executed, they may include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0071] The blockchain referred to in this application is a new application model for computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Blockchain is essentially a decentralized database, a series of data blocks generated using cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity of this information (to prevent counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, the platform product service layer, and the application service layer.

[0072] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0073] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0074] The above-mentioned embodiments only express several implementation methods of the present application, and their descriptions are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that for ordinary technicians in this field, without departing from the concept of the present application, they can also make several modifications, improvements or equivalent replacements of some technical features, and these modifications or replacements do not make the essence of the same technical solution depart from the spirit and scope of the technical solution of each embodiment of the present invention, and all belong to the scope of protection of this application. Therefore, the scope of protection of the patent in this application shall be based on the attached claims.

Claims

1. A blockchain-based transfer transaction method, characterized in that: The method comprises: When receiving multiple transfer transaction requests, obtain the block height and block hash of the known blockchain system as the root of trust; Sort the transfer transaction requests according to the trust root to obtain a transaction number for each transfer transaction request; Sort the transfer transactions at the same block height according to the transaction number to obtain the transaction order; and Execute each transfer transaction request according to the transaction order.

2. The method according to claim 1, characterized in that The executing each transfer transaction request according to the transaction order includes: In the case where each of the transfer transaction requests meets the validity of the transaction time and the validity of the transaction content, the transfer transaction requests are sorted and executed according to the transaction order.

3. The method according to claim 1, characterized in that The executing of each transfer transaction request according to the transaction order further includes: If the transaction number and transaction content corresponding to the transfer transaction request are already in the transfer details table, the transfer transaction request is abandoned.

4. A blockchain-based blockchain transfer transaction device, characterized in that: include: The verification module is used to obtain the block height and block hash of the known blockchain system as the root of trust when receiving multiple transfer transaction requests; a first sorting module, configured to sort each transfer transaction request according to the trust root, and obtain a transaction number of each transfer transaction request; A second sorting module is used to sort the transfer transactions at the same block height according to the transaction number to obtain a transaction order; and The transfer execution module is used to execute each transfer transaction request according to the transaction sequence.

5. A computer device comprising a memory and a processor, wherein the memory stores computer-readable instructions, wherein: When the processor executes the computer-readable instructions, the steps of the method according to any one of claims 1 to 3 are implemented.

6. A computer-readable storage medium having computer-readable instructions stored thereon, characterized in that: When the computer-readable instructions are executed by a processor, the steps of the method according to any one of claims 1 to 3 are implemented.

Images