CN117670330A - Block chain-based transaction processing method and device, electronic equipment and storage medium - Google Patents
Block chain-based transaction processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN117670330A CN117670330A CN202410139156.1A CN202410139156A CN117670330A CN 117670330 A CN117670330 A CN 117670330A CN 202410139156 A CN202410139156 A CN 202410139156A CN 117670330 A CN117670330 A CN 117670330A
- Authority
- CN
- China
- Prior art keywords
- transaction
- block
- target
- data
- transaction data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 20
- 238000012795 verification Methods 0.000 claims abstract description 98
- 238000000034 method Methods 0.000 claims abstract description 27
- 238000001514 detection method Methods 0.000 claims abstract description 20
- 230000004044 response Effects 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 16
- 238000010586 diagram Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000001174 ascending effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000006798 recombination Effects 0.000 description 1
- 238000005215 recombination Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the disclosure discloses a transaction processing method and device based on a blockchain, an electronic device and a storage medium, wherein the method comprises the following steps: when a transaction request sent by a client is received, the server generates target verification information according to the address information and the random number of the client in the transaction request; the server performs replay transaction detection on target transaction data in the transaction request based on the target verification information; when the target transaction data is not the replayed transaction data, determining a corresponding block-out block height range when the target transaction data is blocked based on the preset buffer block number of the server side and a transaction block-out height threshold value in the transaction request; when the target transaction data is determined to accord with the preset block outlet condition according to the block height and the block outlet block height range corresponding to the server side, the server side generates target block data corresponding to the target transaction data and adds the target block data to the block chain.
Description
Technical Field
The present disclosure relates to the field of blockchain technology and the field of transaction replay technology, and in particular, to a blockchain-based transaction processing method and apparatus, an electronic device, and a storage medium.
Background
With the continuous expansion of the application field of the blockchain technology, the data security of the blockchain is also more and more important. Wherein the replay attack prevention capability of the blockchain is related to the accuracy of the ledgers in the blockchain. In the related art, it is common to set a verification value for each transaction, which is a continuous value generated strictly in ascending order, and then determine whether the transaction is replay transaction data based on the corresponding verification value of the transaction. However, since the verification values are consecutive values generated strictly in ascending order, this causes a long period of time to be impossible for subsequent transactions when transaction data is lost or the verification values are set incorrectly.
Disclosure of Invention
In order to solve the above-mentioned difficult problems, embodiments of the present disclosure provide a transaction processing method and apparatus based on blockchain, an electronic device, and a storage medium.
In one aspect of the disclosed embodiments, there is provided a blockchain-based transaction processing method, including: in response to receiving a transaction request sent by a client, a server generates target verification information according to client address information and a random number in the transaction request; the server performs replay transaction detection on target transaction data in the transaction request based on the target verification information; responding to the transaction data which is not replayed by the target transaction data, and determining a corresponding block-out height range when the target transaction data is blocked out based on the preset buffer block number of the server side and a transaction block-out height threshold value in the transaction request; and in response to determining that the target transaction data meets a preset block condition according to the block height corresponding to the server side and the block outlet block height range, the server side generates target block data corresponding to the target transaction data and adds the target block data to a block chain.
In another aspect of an embodiment of the present disclosure, there is provided a blockchain-based transaction processing device including: the system comprises a verification information generation module, a verification information generation module and a verification information generation module, wherein the verification information generation module is used for responding to a transaction request sent by a client, and the server generates target verification information according to client address information and random numbers in the transaction request; the replay transaction detection module is used for detecting the replay transaction of the target transaction data in the transaction request based on the target verification information by the server; the first determining module is used for determining a corresponding block outlet height range when the target transaction data is blocked based on the preset buffer block number of the server side and the transaction block outlet height threshold value in the transaction request in response to the fact that the target transaction data is not replayed transaction data; and the block outputting module is used for responding to the determination that the target transaction data accords with the preset block outputting condition according to the block height corresponding to the server side and the block outputting block height range, and the server side generates target block data corresponding to the target transaction data and adds the target block data to a block chain.
In yet another aspect of the disclosed embodiments, there is provided an electronic device including: a memory for storing a computer program; and a processor for executing the computer program stored in the memory, and when the computer program is executed, implementing a blockchain-based transaction processing method.
In yet another aspect of the disclosed embodiments, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements a blockchain-based transaction processing method.
In the embodiment of the disclosure, the server generates the target verification information corresponding to the target transaction data through the client address information and the random number in the transaction request, and then performs replay transaction detection on the target transaction data according to the target verification information, so that high-efficiency replay transaction detection processing on the target transaction data is realized, whether the target transaction data is the replay transaction data is determined, the safety and the accuracy of block data corresponding to the server are ensured, the random number is not required in the embodiment of the disclosure, whether the target transaction data is the replay transaction data can be determined only according to the target verification information comprising the random number and the client address information, the problem that subsequent transactions cannot be executed for a long time due to the fact that the transaction request is lost or the verification value is set incorrectly is solved, and the robustness of the server is improved.
In addition, in the embodiment of the disclosure, after determining that the target transaction data is not the replayed transaction data, determining a corresponding block-out block height range when the target transaction data is blocked out based on the preset buffer block number of the server side and the transaction block-out height threshold value in the transaction request; and when the target transaction data is determined to be in accordance with the preset block-out condition according to the block height and the block-out block height range corresponding to the server, the server generates target block data corresponding to the target transaction data and transmits the target block data to a block chain. By limiting the block height of the target block data when the target transaction data is blocked, the server side can reasonably block the target transaction data within the range of the block height to generate the target block data, so that the problem that the target transaction data is judged to be replayed transaction data and further the transaction request cannot be executed due to the fact that the client side repeatedly sends the transaction request because the target transaction data waits for the block-out time to be too long is avoided.
The technical scheme of the present disclosure is described in further detail below through the accompanying drawings and examples.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings in which:
FIG. 1 is a flow diagram of a blockchain-based transaction processing method provided by an exemplary embodiment of the present disclosure;
FIG. 2 is a flow diagram of a blockchain-based transaction processing method provided by another exemplary embodiment of the present disclosure;
FIG. 3 is a flow chart of step S220 provided by an exemplary embodiment of the present disclosure;
FIG. 4 is a schematic diagram of an application example provided by an exemplary embodiment of the present disclosure;
FIG. 5 is a block diagram of a blockchain-based transaction processing device provided in an exemplary embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an application embodiment of the electronic device of the present disclosure.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless it is specifically stated otherwise.
It will be appreciated by those of skill in the art that the terms "first," "second," etc. in embodiments of the present disclosure are used merely to distinguish between different steps, devices or modules, etc., and do not represent any particular technical meaning nor necessarily logical order between them.
It should also be understood that in embodiments of the present disclosure, "plurality" may refer to two or more, and "at least one" may refer to one, two or more.
It should also be appreciated that any component, data, or structure referred to in the presently disclosed embodiments may be generally understood as one or more without explicit limitation or the contrary in the context.
In addition, the term "and/or" in this disclosure is merely an association relationship describing an association object, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" in the present disclosure generally indicates that the front and rear association objects are an or relationship.
It should also be understood that the description of the various embodiments of the present disclosure emphasizes the differences between the various embodiments, and that the same or similar features may be referred to each other, and for brevity, will not be described in detail.
Meanwhile, it should be understood that the sizes of the respective parts shown in the drawings are not drawn in actual scale for convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but are intended to be part of the specification where appropriate.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
Embodiments of the present disclosure may be applicable to electronic devices such as terminal devices, computer systems, servers, etc., which may operate with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known terminal devices, computing systems, environments, and/or configurations that may be suitable for use with the terminal device, computer system, server, or other electronic device include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers, small computer systems, mainframe computer systems, and distributed cloud computing technology environments that include any of the foregoing, and the like.
Electronic devices such as terminal devices, computer systems, servers, etc. may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, etc., that perform particular tasks or implement particular abstract data types. The computer system/server may be implemented in a distributed cloud computing environment in which tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computing system storage media including memory storage devices.
In the disclosed embodiments:
the Block Chain (Block Chain) is a distributed account book technology based on a point-to-point network, each Node (Node) in the Block Chain network has the same complete data, and the nodes realize the data consistency on the Chain of each Node through a consensus mechanism. Nodes in a blockchain network, commonly referred to as computing devices in the blockchain network, that is, any computing device connected to the blockchain network (including cell phones, servers, etc.) are referred to as nodes, wherein the nodes may be used to store, run, validate, etc. blockdata in the blockchain network.
The block-out refers to that any node in the blockchain network carries out consensus on a certain amount of transaction data in any node and other nodes, and then each node packs the consensus transaction data to generate block data and stores the block data, so that the block-out of the block data is completed.
Replay Attacks (Replay Attacks) in blockchains refer to repeated transmission of transaction data that has been executed in order to make one transaction data executed multiple times by spoofing the blockchain network, thereby using one monetary transaction multiple commodities and thus giving the blockchain a serious security problem.
Fig. 1 is a flow chart of a blockchain-based transaction processing method provided in an exemplary embodiment of the present disclosure. The embodiment can be applied to an electronic device, as shown in fig. 1, and includes the following steps:
in step S110, in response to receiving the transaction request sent by the client, the server generates target verification information according to the address information and the random number of the client in the transaction request.
Wherein the transaction request includes: client address information, random numbers, and target transaction data. The target authentication information includes client address information and a random number. The target verification information has a correspondence with the target transaction data. The random number in the transaction request may be randomly generated without meeting the requirement of continuous increment.
The client address information may include an IP address (Internet Protocol Address ) or URL (Uniform Resource Locator, uniform resource location system) address of the client, etc. The target transaction data may include transaction type, gas fee, transaction party information, transaction time, etc. The transaction types can include, but are not limited to, ticket transactions, car purchase transactions, parking fee transactions, etc., and the transaction party information includes party information involved in the transactions, etc.
The server may be any node in the blockchain. The client may be a computing device or a plug-in wallet or the like. The plug-in wallet is a plug-in developed based on a browser, and can be used for storing, managing, constructing digital identity identifiers, verifiable certificates and the like, transaction data and the like. The server is in communication connection with the client.
In an alternative embodiment, the server obtains the client address information a and the random number r from the transaction request, and then generates a binary data set key < a, r > from the client address information a and the random number r, takes the key < a, r > as target verification information, and binds the key < a, r > with the target transaction data so as to enable the target transaction data to correspond to the target verification information.
In step S120, the service end performs playback transaction detection on the target transaction data in the transaction request based on the target verification information.
The server side comprises a plurality of transaction data and verification information corresponding to each transaction data. The replayed transaction data indicates that the transaction data has been previously executed. The server may store the plurality of transaction data in the blockchain in the form of blockdata.
In a specific implementation manner, at the server side, all verification information of the server side may be compared with the target verification information, and when verification information identical to the target verification information does not exist, it is determined that the target transaction data is not replayed transaction data, and then step S130 is performed; when the verification information which is the same as the target verification information exists, the target transaction data is determined to be replayed transaction data, and then the server side sends a transaction request execution failure message to the client side. Or,
comparing the target verification information with verification information of transaction data in a preset period of time when the distance in the server is the same as the target verification information, determining that the target transaction data is not replayed transaction data when the verification information which is the same as the target verification information does not exist, and then executing step S130; when the verification information which is the same as the target verification information exists, the target transaction data is determined to be replayed transaction data, and then the server side sends a transaction request execution failure message to the client side.
Step S130, in response to the target transaction data not being the replayed transaction data, determining a corresponding block-out block height range when the target transaction data is blocked based on the preset buffer block number of the server side and the transaction block-out height threshold value in the transaction request.
Wherein the transaction request further comprises: trading out a block height threshold; the transaction out block threshold represents a block height maximum value of block data including target transaction data, i.e., a block height of block data of a latest out block of target transaction data. The out-block height range represents a range of block corresponding block heights including the target transaction. The server side caches block data with preset cache block number.
In an alternative embodiment, assuming that the number of preset cache blocks is N and the transaction out block height threshold is h, the out block height range may be (h-N) to h, where N and h are both natural numbers.
In step S140, in response to determining that the target transaction data meets the preset block-out condition according to the block height and the block-out block height range corresponding to the server, the server generates target block data corresponding to the target transaction data and adds the target block data to the blockchain. In the present embodiment, a block including target transaction data is referred to as target block data.
The block height corresponding to the server is the block height of block data generated by transaction data, verification data and the like in the server. The target block data includes target transaction data.
In a specific implementation manner, at the server, when the target transaction data is not the replayed transaction data, the target transaction data may be added to the transaction task queue, and when it is time to process the target transaction data, that is, the transaction task queue pops up the target transaction data, the current block height H1 corresponding to the server is obtained, and the block height of the block data to be currently generated (out of the block) at the server is determined according to the current block height H1 corresponding to the server, that is, the block height of the block data to be currently generated at the server is H2, where h2=h1+1. When (H-N) is less than H2 and less than or equal to H, determining that the target transaction data meets the preset block-out condition, generating target block data corresponding to the target transaction data by the server, and adding the target block data to the blockchain to finish the uplink of the target block data.
When H2 > H, determining that the target transaction data does not meet the preset block-out condition, and sending a transaction request execution failure message to the client by the server.
In the embodiment of the disclosure, the server generates the target verification information corresponding to the target transaction data through the client address information and the random number in the transaction request, and then performs replay transaction detection on the target transaction data according to the target verification information, so that high-efficiency replay transaction detection processing on the target transaction data is realized, whether the target transaction data is the replay transaction data is determined, the safety and the accuracy of block data corresponding to the server are ensured, the random number is not required in the embodiment of the disclosure, whether the target transaction data is the replay transaction data can be determined only according to the target verification information comprising the random number and the client address information, the problem that subsequent transactions cannot be executed for a long time due to the fact that the transaction request is lost or the verification value is set incorrectly is solved, and the robustness of the server is improved.
In addition, in the embodiment of the disclosure, after determining that the target transaction data is not the replayed transaction data, determining a corresponding block-out block height range when the target transaction data is blocked out based on the preset buffer block number of the server side and the transaction block-out height threshold value in the transaction request; and when the target transaction data is determined to be in accordance with the preset block-out condition according to the block height and the block-out block height range corresponding to the server, the server generates target block data corresponding to the target transaction data and adds the target block data to the block chain. By limiting the block height of the target block data when the target transaction data is blocked, the server side reasonably blocks the target transaction data within the block-out block height range, and the target block data is generated, so that the problem that the target transaction data is judged to be replayed transaction data and further the transaction request cannot be executed due to the fact that the client side repeatedly sends the transaction request because the target transaction data waits for the block-out time to be too long is avoided.
In some optional implementations, step S120 in the embodiments of the present disclosure may include: and determining that the target transaction data is not the replayed transaction data according to the verification information corresponding to the transaction data in the transaction pool in the server and the verification information corresponding to the transaction data in the transaction task queue in the server, which are different from the target verification information.
Wherein, the server side includes: the system comprises a transaction pool and a transaction task queue, wherein the transaction pool caches block data with preset cache block number, any block data comprises a plurality of transaction data, and the transaction data in the transaction pool are transaction data processed by a server side; the transaction task queue comprises a plurality of transaction data, and the transaction data in the transaction task queue are the transaction data to be processed by the server side. The server side also stores verification information corresponding to each transaction data in the transaction pool and verification information corresponding to each transaction data in the transaction task queue.
In an alternative implementation manner, at the server side, the target verification information may be compared with verification information corresponding to each transaction data in the transaction pool, when the verification information corresponding to each transaction data in the transaction pool is different from the target verification information, the target verification information is compared with verification information corresponding to each transaction data in the transaction task queue, and when the verification information corresponding to each transaction data in the transaction task queue is different from the target verification information, it is determined that the target transaction data is not the replayed transaction data. And when the verification information corresponding to any transaction data in the transaction pool is the same as the target verification information, determining that the target transaction data is replayed transaction data.
In the embodiment of the disclosure, the target transaction data is subjected to replay transaction detection by selecting the transaction data corresponding to the number of the preset cache blocks and combining the transaction data in the transaction task queue, so that the calculated number of the replay transaction detection is reduced, and the accuracy of the replay transaction detection of the target transaction data is ensured.
In some optional implementations, step S120 in the embodiments of the present disclosure may include: responding to that verification information corresponding to transaction data in a transaction pool is different from target verification information, and verification information corresponding to any transaction data in a transaction task queue is the same as the target verification information, acquiring first transaction cost information in the target transaction data and acquiring second transaction cost information in any transaction data in the transaction task queue; in response to the first transaction fee information being greater than the second transaction fee information, determining that the target transaction data is not replayed transaction data, and deleting any transaction data in the transaction task queue.
In the embodiment of the disclosure, the transaction fee information included in the target transaction data is referred to as first fee information, and the fee information included in the transaction data in the transaction pool and the fee information included in the transaction information in the transaction task queue are referred to as second fee information.
Wherein, the first fee information and the second fee information may be Gas fees. Gas fees refer to the fees actually paid by a user for a transaction or contract.
In an alternative implementation manner, at the server, when the verification information corresponding to each transaction data in the transaction pool is different from the target verification information, and the verification information corresponding to any transaction data in the transaction task queue is the same as the target verification information, that is, the verification information corresponding to one transaction data in the transaction task queue is the same as the target verification information. And acquiring Gas fees (first fee information) included in the target transaction data, acquiring Gas fees (second fee information) included in any transaction data, comparing the Gas fees included in the target transaction data with the Gas fees included in any transaction data, determining that the target transaction data is not replayed transaction data when the Gas fees included in the target transaction data are greater than the Gas fees included in any transaction data, and deleting any transaction data in the transaction task queue. And when the Gas fee included in the target transaction data is less than or equal to the Gas fee included in any transaction data, determining that the target transaction data is replayed transaction data.
In some alternative implementations, step S130 in the embodiments of the present disclosure may include: and in response to determining that the target transaction data meets the preset block-out waiting condition according to the block height and the block-out block height range corresponding to the server, setting the state of the target transaction data as a waiting state until the target transaction data meets the preset block-out condition, and generating the target block data by the server.
In one particular implementation, at the server, when the target transaction data is not replayed transaction data,
the method comprises the steps that target transaction data can be added into a transaction task queue, the transaction task queue can pop up the target transaction data once every preset time length, for each transaction task queue popping up the target transaction data, the block height H2 of block data to be generated currently of a server side is determined, when H2 is less than or equal to (H-N), the target transaction data is determined to meet preset block waiting conditions, the state of the target transaction data is set to be a waiting state, the target transaction data is added into the transaction task queue again, when (H-N) is less than H2 and less than or equal to H, the target transaction data is determined to meet the preset block waiting conditions, the server side generates target block data corresponding to the target transaction data, and the target block data is transmitted to a block chain, so that the uplink of the target block data is completed; when H2 > H, determining that the target transaction data does not meet the preset block-out condition, and sending a transaction request execution failure message to the client by the server.
In some alternative implementations, step S140 in the embodiments of the present disclosure may include: and updating the target block data into the transaction pool according to a preset block cache updating rule so that the number of block data in the updated transaction pool accords with the number of preset cache blocks.
In a specific implementation manner, the target block data may be added to the transaction pool, and then the block data corresponding to the block height (H2-N) in the cache pool is deleted, that is, the block data corresponding to the minimum block height in the transaction pool is deleted, so that the number of the block data in the transaction pool after updating is equal to the preset cache block number.
Fig. 2 is a flow chart of a blockchain-based transaction processing method provided by another exemplary embodiment of the present disclosure. In some alternative embodiments, as shown in fig. 2, the following steps are further included before step S110:
in step S210, the client obtains the block height corresponding to the server and the preset buffer block number.
Before the client sends the transaction request, the client may request the block height and the preset buffer block number corresponding to the server from the server, and the server feeds back the block height and the preset buffer block number corresponding to the server to the client.
In step S220, the client determines a transaction block height threshold according to the block height corresponding to the server and the preset buffer block number.
In a specific implementation manner, a selection range of a transaction output block height threshold h can be determined according to a block height h0 corresponding to a server side and the number N of preset cache blocks, the selection range is h0 to (h0+N), h0 is not included, namely h satisfies h0 < h0+N, wherein a value as small as possible is selected from h0 to (h0+N) as the transaction output block height threshold, and waiting for process time when target transaction data is output from the server side is avoided.
In step S230, the client determines a transaction request according to the target transaction data, the client address information, the random number, and the transaction output block height threshold.
The client may generate the random number according to a preset random number generation algorithm, for example, a linear congruence method, a meisen rotation algorithm, or the like, or may generate the random number by using a random number generator. The random generation generated by the server does not need to meet the requirement of continuous increment.
The client packages the target transaction data, the client address information, the random number and the transaction output block height threshold value into a transaction request, and then sends the transaction request to the server.
Fig. 3 is a flowchart illustrating step S220 provided in an exemplary embodiment of the present disclosure. In some alternative embodiments, as shown in fig. 3, step S220 may include the steps of:
in step S221, the client obtains the amount of transaction data in the transaction task queue in the server.
The client requests the amount of transaction data in a transaction task queue in the server from the server, and the server feeds back the amount of the transaction data in the transaction task queue to the client.
Step S222, in response to the transaction data in the transaction task queue being greater than or equal to the preset transaction data amount, determining the transaction output block height threshold by using a first preset rule based on the block height corresponding to the server side and the preset buffer block number.
Wherein the first preset rule includes h > h0+N.
The amount of transaction data in the transaction task queue may be compared with a preset amount of transaction data, and when the amount of transaction data in the transaction task queue is greater than or equal to the preset amount of transaction data, h is selected from the values greater than h0+N, such that the selected h satisfies h > h0+N.
In step S223, in response to the amount of transaction data in the transaction task queue being less than the preset transaction data amount, determining a transaction out-block height threshold by using a second preset rule based on the block height corresponding to the server and the preset buffer block amount.
The transaction output block height threshold value obtained by the first preset rule is larger than the transaction output block height threshold value obtained by the second preset rule.
The second preset rule comprises h0 < h < h0+N.
When the number of transaction data in the transaction task queue is smaller than the preset transaction data amount, h is selected from h0 to (h0+N) so that the selected h meets h0 < h0+N.
It should be noted that, there is no sequence in execution between step S222 and step S223.
Fig. 4 is a schematic diagram of an application example provided by an exemplary embodiment of the present disclosure. As shown in fig. 4, a communication protocol, for example, HTTP (Hypertext Transfer Protocol ) or the like, may be set between the client and the server. Assuming that the blockchain includes 4 nodes, any node in the server may be used as the server. Node 1 will be available as the server in this application example. Each node comprises a transaction pool, wherein the transaction pool caches block data of the preset cache block number, and any block data comprises a plurality of transaction data. The client acquires the block height corresponding to the server, the preset buffer block number and the transaction data in the transaction task queue, generates a transaction output block height threshold based on the block height corresponding to the server, the preset buffer block number and the transaction data in the transaction task queue, generates a random number at the same time, determines a transaction request according to the target transaction data, the client address information, the random number and the transaction output block height threshold, and sends the transaction request to the server.
The server generates target verification information according to the address information of the client and the random number in the transaction request; the server performs replay transaction detection on target transaction data in the transaction request based on the target verification information; when the target transaction data is not the replayed transaction data, determining a corresponding block-out block height range when the target transaction data is blocked based on the preset buffer block number of the server side and a transaction block-out height threshold value in the transaction request; when the target transaction data is determined to meet the preset block-out condition according to the block height and the block-out block height range corresponding to the server side, the server side generates target block data corresponding to the target transaction data, and synchronizes the target block data to other nodes, namely to the node 2, the node 3 and the node 4, so as to finish adding the target block data to the block chain. When the target transaction data is determined to meet the preset block-out waiting condition according to the block height and the block-out block height range corresponding to the server, setting the state of the target transaction data to be a waiting state until the target transaction data meets the preset block-out condition, generating the target block data by the server, and synchronizing the target block data to other nodes, namely to the node 2, the node 3 and the node 4, so as to finish adding the target block data to the block chain.
Fig. 5 is a block diagram of a block chain based transaction processing device according to an exemplary embodiment of the present disclosure. As shown in fig. 5, the blockchain-based transaction processing device includes:
the verification information generation module 300 is configured to generate target verification information according to client address information and a random number in a transaction request sent by a client in response to receiving the transaction request;
a replay transaction detection module 310, configured to perform replay transaction detection on target transaction data in the transaction request based on the target verification information by the server side;
a first determining module 320, configured to determine, in response to the target transaction data not being replayed transaction data, a corresponding block-out height range when the target transaction data is blocked, based on a preset buffer block number of the server side and a transaction block-out height threshold in the transaction request;
the block outputting module 330 is configured to, in response to determining that the target transaction data meets a preset block outputting condition according to the block height corresponding to the server and the block outputting height range, generate target block data corresponding to the target transaction data by the server, and add the target block data to a blockchain.
In one embodiment of the present disclosure, the replay transaction detection module 310 in an embodiment of the present disclosure is specifically configured to: and responding to verification information corresponding to transaction data in a transaction pool in the server side and verification information corresponding to transaction data in a transaction task queue in the server side, wherein the verification information is different from the target verification information, determining that the target transaction data is not replayed transaction data, caching block data with the preset cache block number in the transaction pool, and any block data comprises a plurality of transaction data.
In one embodiment of the present disclosure, the replay transaction detection module 310 in embodiments of the present disclosure is specifically: responding to that verification information corresponding to transaction data in the transaction pool is different from the target verification information, and verification information corresponding to any transaction data in the transaction task queue is the same as the target verification information, acquiring first transaction cost information in the target transaction data and acquiring second transaction cost information in any transaction data in the transaction task queue; and in response to the first transaction fee information being greater than the second transaction fee information, determining that the target transaction data is not replayed transaction data, and deleting any transaction data in a transaction task queue.
In one embodiment of the present disclosure, the blockchain-based transaction processing device in embodiments of the present disclosure further includes:
and the second determining module is used for setting the state of the target transaction data to be a waiting state until the target transaction data accords with the preset block outlet condition in response to determining that the target transaction data accords with the preset block outlet waiting condition according to the block height corresponding to the server side and the block outlet block height range, and the server side generates the target block data.
In one embodiment of the present disclosure, the blockchain-based transaction processing device in embodiments of the present disclosure further includes:
and the updating module is used for updating the target block data into the transaction pool according to a preset block cache updating rule so that the number of the block data in the updated transaction pool is the number of the preset cache blocks.
In one embodiment of the present disclosure, the blockchain-based transaction processing device in embodiments of the present disclosure further includes:
the acquisition module is used for acquiring the block height corresponding to the server side and the preset buffer block number by the client side;
a third determining module, configured to determine, by the client, the transaction block height threshold according to the block height corresponding to the server and the preset buffer block number;
And the fourth determining module is used for determining the transaction request by the client according to the target transaction data, the client address information, the random number and the transaction output block height threshold value.
In one embodiment of the present disclosure, the fourth determining module in an embodiment of the present disclosure includes:
the acquisition sub-module is used for acquiring the quantity of the transaction data in the transaction task queue by the client;
the first determining submodule is used for determining the transaction output block height threshold value by utilizing a first preset rule based on the block height corresponding to the server side and the preset cache block number in response to the fact that the number of transaction data in the transaction task queue is larger than or equal to a preset transaction data amount;
and the second determining submodule is used for determining the transaction output block height threshold value by utilizing a second preset rule based on the block height corresponding to the server side and the preset buffer block number in response to the fact that the number of transaction data in the transaction task queue is smaller than the preset transaction data amount, and the transaction output block height threshold value acquired by utilizing the first preset rule is larger than the transaction output block height threshold value acquired by utilizing the second preset rule.
The blockchain-based transaction processing device in the embodiment of the present disclosure corresponds to the embodiment of the blockchain-based transaction processing method in the present disclosure, and the related contents may be referred to each other and are not described herein again.
Advantageous technical effects corresponding to the exemplary embodiments of the blockchain-based transaction processing device according to the embodiments of the present disclosure may refer to the corresponding advantageous technical effects of the corresponding exemplary method section described above, and will not be described herein.
In addition, the embodiment of the disclosure also provides an electronic device, which comprises:
a memory for storing a computer program;
and a processor configured to execute the computer program stored in the memory, and when the computer program is executed, implement the blockchain-based transaction processing method according to any of the above embodiments of the present disclosure.
Fig. 6 is a schematic structural diagram of an application embodiment of the electronic device of the present disclosure. Next, an electronic device according to an embodiment of the present disclosure is described with reference to fig. 6. The electronic device may be either or both of the first device and the second device, or a stand-alone device independent thereof, which may communicate with the first device and the second device to receive the acquired input signals therefrom.
As shown in fig. 6, the electronic device includes one or more processors and memory.
The processor may be a Central Processing Unit (CPU) or other form of processing unit having data processing and/or instruction execution capabilities, and may control other components in the electronic device to perform the desired functions.
The memory may include one or more computer program products that may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, random Access Memory (RAM) and/or cache memory (cache), and the like. The non-volatile memory may include, for example, read Only Memory (ROM), hard disk, flash memory, and the like. One or more computer program instructions may be stored on the computer readable storage medium that can be executed by a processor to implement the blockchain-based transaction processing methods and/or other desired functions of the various embodiments of the present disclosure as described above.
In one example, the electronic device may further include: input devices and output devices, which are interconnected by a bus system and/or other forms of connection mechanisms (not shown).
In addition, the input device may include, for example, a keyboard, a mouse, and the like.
The output device may output various information including the determined distance information, direction information, etc., to the outside. The output devices may include, for example, a display, speakers, a printer, and a communication network and remote output devices connected thereto, etc.
Of course, only some of the components of the electronic device relevant to the present disclosure are shown in fig. 6, with components such as buses, input/output interfaces, etc. omitted for simplicity. In addition, the electronic device may include any other suitable components depending on the particular application.
In addition to the methods and apparatus described above, embodiments of the present disclosure may also be a computer program product comprising computer program instructions which, when executed by a processor, cause the processor to perform the steps in a blockchain-based transaction processing method according to various embodiments of the present disclosure described in the above section of the present description.
The computer program product may write program code for performing the operations of embodiments of the present disclosure in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server.
Further, embodiments of the present disclosure may also be a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, cause the processor to perform steps in a blockchain-based transaction processing method according to various embodiments of the present disclosure described in the above section of the present description.
The computer readable storage medium may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
The basic principles of the present disclosure have been described above in connection with specific embodiments, however, it should be noted that the advantages, benefits, effects, etc. mentioned in the present disclosure are merely examples and not limiting, and these advantages, benefits, effects, etc. are not to be considered as necessarily possessed by the various embodiments of the present disclosure. Furthermore, the specific details disclosed herein are for purposes of illustration and understanding only, and are not intended to be limiting, since the disclosure is not necessarily limited to practice with the specific details described.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different manner from other embodiments, so that the same or similar parts between the embodiments are mutually referred to. For system embodiments, the description is relatively simple as it essentially corresponds to method embodiments, and reference should be made to the description of method embodiments for relevant points.
The block diagrams of the devices, apparatuses, devices, systems referred to in this disclosure are merely illustrative examples and are not intended to require or imply that the connections, arrangements, configurations must be made in the manner shown in the block diagrams. As will be appreciated by one of skill in the art, the devices, apparatuses, devices, systems may be connected, arranged, configured in any manner. Words such as "including," "comprising," "having," and the like are words of openness and mean "including but not limited to," and are used interchangeably therewith. The terms "or" and "as used herein refer to and are used interchangeably with the term" and/or "unless the context clearly indicates otherwise. The term "such as" as used herein refers to, and is used interchangeably with, the phrase "such as, but not limited to.
The methods and apparatus of the present disclosure may be implemented in a number of ways. For example, the methods and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, firmware. The above-described sequence of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the sequence specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present disclosure may also be implemented as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
It is also noted that in the apparatus, devices and methods of the present disclosure, components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered equivalent to the present disclosure.
The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing description has been presented for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of the disclosure to the form disclosed herein. Although a number of example aspects and embodiments have been discussed above, a person of ordinary skill in the art will recognize certain variations, modifications, alterations, additions, and subcombinations thereof.
Claims (10)
1. A blockchain-based transaction processing method, comprising:
in response to receiving a transaction request sent by a client, a server generates target verification information according to client address information and a random number in the transaction request;
the server performs replay transaction detection on target transaction data in the transaction request based on the target verification information;
responding to the transaction data which is not replayed by the target transaction data, and determining a corresponding block-out height range when the target transaction data is blocked out based on the preset buffer block number of the server side and a transaction block-out height threshold value in the transaction request;
and in response to determining that the target transaction data meets a preset block condition according to the block height corresponding to the server side and the block outlet block height range, the server side generates target block data corresponding to the target transaction data and adds the target block data to a block chain.
2. The method of claim 1, wherein the server performs playback transaction detection on the target transaction data in the transaction request based on the target verification information, comprising:
and responding to verification information corresponding to transaction data in a transaction pool in the server side and verification information corresponding to transaction data in a transaction task queue in the server side, wherein the verification information is different from the target verification information, determining that the target transaction data is not replayed transaction data, caching block data with the preset cache block number in the transaction pool, and any block data comprises a plurality of transaction data.
3. The method of claim 2, wherein the server performs playback transaction detection on the target transaction data in the transaction request based on the target verification information, further comprising:
responding to that verification information corresponding to transaction data in the transaction pool is different from the target verification information, and verification information corresponding to any transaction data in the transaction task queue is the same as the target verification information, acquiring first transaction cost information in the target transaction data and acquiring second transaction cost information in any transaction data in the transaction task queue;
And in response to the first transaction fee information being greater than the second transaction fee information, determining that the target transaction data is not replayed transaction data, and deleting any transaction data in a transaction task queue.
4. The method according to claim 2, wherein after determining the corresponding block-out height range when the target transaction data is blocked based on the preset number of cache blocks of the server side and the transaction block-out height threshold in the transaction request, the method comprises:
and in response to determining that the target transaction data meets a preset block waiting condition according to the block height corresponding to the server side and the block outlet block height range, setting the state of the target transaction data as a waiting state until the target transaction data meets the preset block outlet condition, and generating the target block data by the server side.
5. The method of any of claims 2-4, wherein after the adding the target block to a blockchain, further comprising:
and updating the target block data into the transaction pool according to a preset block cache updating rule, so that the number of block data in the updated transaction pool is the number of the preset cache blocks.
6. The method of any of claims 1-4, wherein prior to receiving the transaction request sent by the client, further comprising:
the client acquires the block height corresponding to the server and the preset buffer block number;
the client determines the transaction block outlet height threshold according to the block height corresponding to the server and the preset buffer block number;
the client determines the transaction request according to the target transaction data, the client address information, the random number and the transaction output block height threshold.
7. The method of claim 6, wherein the determining, by the client, the transaction out-block height threshold according to the block height corresponding to the server and the preset number of cache blocks comprises:
the client acquires the quantity of transaction data in a transaction task queue;
determining a transaction output block height threshold by using a first preset rule based on the block height corresponding to the server side and the preset buffer block number in response to the transaction data in the transaction task queue being greater than or equal to a preset transaction data amount;
And determining the transaction output block height threshold by using a second preset rule based on the block height corresponding to the server side and the preset buffer block number in response to the transaction data amount in the transaction task queue being smaller than the preset transaction data amount, wherein the transaction output block height threshold obtained by using the first preset rule is larger than the transaction output block height threshold obtained by using the second preset rule.
8. A blockchain-based transaction processing device, comprising:
the system comprises a verification information generation module, a verification information generation module and a verification information generation module, wherein the verification information generation module is used for responding to a transaction request sent by a client, and the server generates target verification information according to client address information and random numbers in the transaction request;
the replay transaction detection module is used for detecting the replay transaction of the target transaction data in the transaction request based on the target verification information by the server;
the first determining module is used for determining a corresponding block outlet height range when the target transaction data is blocked based on the preset buffer block number of the server side and the transaction block outlet height threshold value in the transaction request in response to the fact that the target transaction data is not replayed transaction data;
And the block outputting module is used for responding to the determination that the target transaction data accords with the preset block outputting condition according to the block height corresponding to the server side and the block outputting block height range, and the server side generates target block data corresponding to the target transaction data and adds the target block data to a block chain.
9. An electronic device, comprising:
a memory for storing a computer program;
a processor for executing a computer program stored in the memory and which, when executed, implements the blockchain-based transaction processing method of any of the preceding claims 1-7.
10. A computer readable storage medium having stored thereon a computer program, which when executed by a processor, implements the blockchain-based transaction processing method of any of the preceding claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410139156.1A CN117670330A (en) | 2024-02-01 | 2024-02-01 | Block chain-based transaction processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410139156.1A CN117670330A (en) | 2024-02-01 | 2024-02-01 | Block chain-based transaction processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117670330A true CN117670330A (en) | 2024-03-08 |
Family
ID=90086632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410139156.1A Pending CN117670330A (en) | 2024-02-01 | 2024-02-01 | Block chain-based transaction processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117670330A (en) |
Citations (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130013491A1 (en) * | 2011-04-19 | 2013-01-10 | Early Warning Sevices, LLC | System and method for detecting and mitigating duplicate transaction fraud |
| CN107067242A (en) * | 2017-03-24 | 2017-08-18 | 钱德君 | Difficulty value creation method in a kind of block chain generating process |
| US20180294955A1 (en) * | 2017-04-05 | 2018-10-11 | Samsung Sds Co., Ltd. | System for processing data based on blockchain and operating method thereof |
| US20190370806A1 (en) * | 2018-05-29 | 2019-12-05 | Alibaba Group Holding Limited | Blockchain-based transaction processing method and apparatus, and electronic device |
| CN111108734A (en) * | 2019-06-26 | 2020-05-05 | 阿里巴巴集团控股有限公司 | Improved anti-replay device based on memory space interchange |
| US10785035B1 (en) * | 2019-04-26 | 2020-09-22 | Alibaba Group Holding Limited | Anti-replay attack authentication protocol |
| US20200311718A1 (en) * | 2017-12-01 | 2020-10-01 | Quant Network Ltd. | Blockchain communications and ordering |
| US20200364212A1 (en) * | 2019-05-17 | 2020-11-19 | Samsung Sds Co., Ltd. | System and method of supporting reflection of transactions between blockchain networks |
| US20210109920A1 (en) * | 2018-02-16 | 2021-04-15 | bitFlyer Blockchain, Inc | Method for Validating Transaction in Blockchain Network and Node for Configuring Same Network |
| US20210232571A1 (en) * | 2020-01-06 | 2021-07-29 | Tata Consultancy Services Limited | Method and system for processing transactions in a blockchain network |
| CN113553380A (en) * | 2021-07-23 | 2021-10-26 | 东北大学 | Reputation-behavior association-oriented data traceability system with double block chains |
| WO2022041899A1 (en) * | 2020-08-28 | 2022-03-03 | 平安科技（深圳）有限公司 | Block processing method and apparatus for blockchain, node device, and storage medium |
| CN114612103A (en) * | 2022-05-10 | 2022-06-10 | 中国信息通信研究院 | Method, device, system, medium and electronic equipment for cross-block chain transaction |
| CN114640524A (en) * | 2022-03-18 | 2022-06-17 | 中国建设银行股份有限公司 | Method, apparatus, device and medium for processing transaction replay attack |
| WO2022141024A1 (en) * | 2020-12-29 | 2022-07-07 | 杭州趣链科技有限公司 | Blockchain technology-based business transaction method and system, and storage medium |
| US20220215390A1 (en) * | 2019-12-23 | 2022-07-07 | Islamic Development Bank Institute | Method and system for transaction validation in a distributed computing system |
| WO2022267180A1 (en) * | 2021-06-22 | 2022-12-29 | 深圳壹账通智能科技有限公司 | Blockchain-based service system and method, and device and storage medium |
| CN115658357A (en) * | 2022-09-30 | 2023-01-31 | 蚂蚁区块链科技(上海)有限公司 | Method and apparatus for replaying blockchain transactions |
| KR20230019648A (en) * | 2021-08-02 | 2023-02-09 | 계명대학교 산학협력단 | Blockchain consensus system and method to improve transaction processing speed |
| US20230090296A1 (en) * | 2021-05-18 | 2023-03-23 | Tencent Technology (Shenzhen) Company Limited | Transaction verification of a transaction based on a blockchain network |
| US20230095123A1 (en) * | 2015-04-08 | 2023-03-30 | Portabe Data Corp | Systems and Methods for Digitally Signed Contracts with Verifiable Credentials |
| CN116055052A (en) * | 2021-10-28 | 2023-05-02 | 腾讯科技（深圳）有限公司 | Block chain-based data processing method, device, equipment and readable storage medium |
| WO2023160077A1 (en) * | 2022-02-25 | 2023-08-31 | 蚂蚁区块链科技(上海)有限公司 | Blockchain data recovery method and apparatus, and electronic device |
| CN116707891A (en) * | 2023-05-31 | 2023-09-05 | 蚂蚁区块链科技(上海)有限公司 | Replay attack checking method and block link point |
| CN116756152A (en) * | 2023-08-22 | 2023-09-15 | 中国信息通信研究院 | Block chain-based data processing method and device, electronic equipment and storage medium |
| WO2023184052A1 (en) * | 2022-03-26 | 2023-10-05 | 华为技术有限公司 | Data processing method, blockchain node and blockchain system |
| CN116991948A (en) * | 2023-09-25 | 2023-11-03 | 中国信息通信研究院 | Block data synchronization system and method, electronic device and storage medium |
-
2024
- 2024-02-01 CN CN202410139156.1A patent/CN117670330A/en active Pending
Patent Citations (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130013491A1 (en) * | 2011-04-19 | 2013-01-10 | Early Warning Sevices, LLC | System and method for detecting and mitigating duplicate transaction fraud |
| US20230095123A1 (en) * | 2015-04-08 | 2023-03-30 | Portabe Data Corp | Systems and Methods for Digitally Signed Contracts with Verifiable Credentials |
| CN107067242A (en) * | 2017-03-24 | 2017-08-18 | 钱德君 | Difficulty value creation method in a kind of block chain generating process |
| US20180294955A1 (en) * | 2017-04-05 | 2018-10-11 | Samsung Sds Co., Ltd. | System for processing data based on blockchain and operating method thereof |
| US20200311718A1 (en) * | 2017-12-01 | 2020-10-01 | Quant Network Ltd. | Blockchain communications and ordering |
| US20210109920A1 (en) * | 2018-02-16 | 2021-04-15 | bitFlyer Blockchain, Inc | Method for Validating Transaction in Blockchain Network and Node for Configuring Same Network |
| US20190370806A1 (en) * | 2018-05-29 | 2019-12-05 | Alibaba Group Holding Limited | Blockchain-based transaction processing method and apparatus, and electronic device |
| US10785035B1 (en) * | 2019-04-26 | 2020-09-22 | Alibaba Group Holding Limited | Anti-replay attack authentication protocol |
| US20200364212A1 (en) * | 2019-05-17 | 2020-11-19 | Samsung Sds Co., Ltd. | System and method of supporting reflection of transactions between blockchain networks |
| CN111108734A (en) * | 2019-06-26 | 2020-05-05 | 阿里巴巴集团控股有限公司 | Improved anti-replay device based on memory space interchange |
| US20220215390A1 (en) * | 2019-12-23 | 2022-07-07 | Islamic Development Bank Institute | Method and system for transaction validation in a distributed computing system |
| US20210232571A1 (en) * | 2020-01-06 | 2021-07-29 | Tata Consultancy Services Limited | Method and system for processing transactions in a blockchain network |
| WO2022041899A1 (en) * | 2020-08-28 | 2022-03-03 | 平安科技（深圳）有限公司 | Block processing method and apparatus for blockchain, node device, and storage medium |
| WO2022141024A1 (en) * | 2020-12-29 | 2022-07-07 | 杭州趣链科技有限公司 | Blockchain technology-based business transaction method and system, and storage medium |
| US20230090296A1 (en) * | 2021-05-18 | 2023-03-23 | Tencent Technology (Shenzhen) Company Limited | Transaction verification of a transaction based on a blockchain network |
| WO2022267180A1 (en) * | 2021-06-22 | 2022-12-29 | 深圳壹账通智能科技有限公司 | Blockchain-based service system and method, and device and storage medium |
| CN113553380A (en) * | 2021-07-23 | 2021-10-26 | 东北大学 | Reputation-behavior association-oriented data traceability system with double block chains |
| KR20230019648A (en) * | 2021-08-02 | 2023-02-09 | 계명대학교 산학협력단 | Blockchain consensus system and method to improve transaction processing speed |
| CN116055052A (en) * | 2021-10-28 | 2023-05-02 | 腾讯科技（深圳）有限公司 | Block chain-based data processing method, device, equipment and readable storage medium |
| WO2023160077A1 (en) * | 2022-02-25 | 2023-08-31 | 蚂蚁区块链科技(上海)有限公司 | Blockchain data recovery method and apparatus, and electronic device |
| CN114640524A (en) * | 2022-03-18 | 2022-06-17 | 中国建设银行股份有限公司 | Method, apparatus, device and medium for processing transaction replay attack |
| WO2023184052A1 (en) * | 2022-03-26 | 2023-10-05 | 华为技术有限公司 | Data processing method, blockchain node and blockchain system |
| CN114612103A (en) * | 2022-05-10 | 2022-06-10 | 中国信息通信研究院 | Method, device, system, medium and electronic equipment for cross-block chain transaction |
| CN115658357A (en) * | 2022-09-30 | 2023-01-31 | 蚂蚁区块链科技(上海)有限公司 | Method and apparatus for replaying blockchain transactions |
| CN116707891A (en) * | 2023-05-31 | 2023-09-05 | 蚂蚁区块链科技(上海)有限公司 | Replay attack checking method and block link point |
| CN116756152A (en) * | 2023-08-22 | 2023-09-15 | 中国信息通信研究院 | Block chain-based data processing method and device, electronic equipment and storage medium |
| CN116991948A (en) * | 2023-09-25 | 2023-11-03 | 中国信息通信研究院 | Block data synchronization system and method, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111787072B (en) | Cross-block-chain interaction method, device, system and electronic equipment | |
| CN108415784B (en) | Cross-block-chain interaction method, device, system and electronic equipment | |
| US8424073B2 (en) | Refreshing a page validation token | |
| US11080691B2 (en) | Fork-tolerant consensus protocol | |
| US9459888B2 (en) | Implementing browser based hypertext transfer protocol session storage | |
| CN109002349B (en) | Application program interaction method, implementation method, device, equipment and medium | |
| CN110910000A (en) | Block chain asset management method and device | |
| CN116257589A (en) | Transaction data processing method, system, device, electronic equipment and storage medium | |
| CN109995775B (en) | Block chain verification code application method, equipment and storage medium | |
| CN110928952A (en) | Data synchronization method and device based on block chain | |
| CN115495770B (en) | Block chain based overdue contract processing method and device, equipment and medium | |
| CN117670330A (en) | Block chain-based transaction processing method and device, electronic equipment and storage medium | |
| CN116991948A (en) | Block data synchronization system and method, electronic device and storage medium | |
| CN114782045B (en) | Cross-chain non-transactional writing method and device, storage medium and electronic equipment | |
| CN114461912A (en) | Information processing method and device, electronic equipment and storage medium | |
| CN117670329B (en) | Trust-based transaction method and device in blockchain network | |
| CN112910643A (en) | Method and device for generating random number in block chain | |
| CN115987683B (en) | Node access control method, device, equipment and medium in block chain network | |
| CN115860744B (en) | Processing method and device of cross-blockchain transaction, blockchain system and equipment | |
| CN115883315B (en) | Node joining method, device, electronic equipment and storage medium in blockchain network | |
| CN115576953B (en) | Block chain-based data interaction method and system, storage medium and equipment | |
| CN117648295B (en) | Text issuing method and device based on blockchain, electronic equipment and storage medium | |
| CN115357548B (en) | Block chain-based electronic contract query method, device, equipment and medium | |
| CN111786936A (en) | Method and device for authentication | |
| CN117812092B (en) | Predicate-based block compression transmission method and apparatus, device and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |