Nothing Special   »   [go: up one dir, main page]

CN111353893A - Transaction data processing method and device based on block chain - Google Patents

Transaction data processing method and device based on block chain Download PDF

Info

Publication number
CN111353893A
CN111353893A CN202010330348.2A CN202010330348A CN111353893A CN 111353893 A CN111353893 A CN 111353893A CN 202010330348 A CN202010330348 A CN 202010330348A CN 111353893 A CN111353893 A CN 111353893A
Authority
CN
China
Prior art keywords
transaction
data
hash value
block
contract
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
Application number
CN202010330348.2A
Other languages
Chinese (zh)
Inventor
李敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202010330348.2A priority Critical patent/CN111353893A/en
Publication of CN111353893A publication Critical patent/CN111353893A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2471—Distributed queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Bioethics (AREA)
  • Health & Medical Sciences (AREA)
  • Probability & Statistics with Applications (AREA)
  • Computational Linguistics (AREA)
  • Mathematical Physics (AREA)
  • Fuzzy Systems (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Computing Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the specification provides a transaction data processing method and device based on a block chain, in the transaction data processing method, transaction data of a transaction can be obtained, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction; packaging the acquired transaction data into a first block, wherein the first block comprises a transaction identifier and a corresponding first hash value, and the first hash value is generated based on the transaction data; and recording the first block on the block chain.

Description

Transaction data processing method and device based on block chain
Technical Field
The embodiment of the specification relates to the field of transaction data processing, in particular to a transaction data processing method and device based on a block chain.
Background
The transaction may pass through multiple stages from initiation to completion, each of which may be performed by the same or different performers. For example, in a purchase transaction, a buyer determines to purchase a commodity, places an order for the commodity and pays the order, and a seller pays the commodity to the buyer after receiving payment from the buyer, and the buyer obtains the purchased commodity, at which time a purchase transaction is completed.
The transaction can be completed on line or off line, when the transaction is off line, the transaction can be performed face to face between the transaction parties, when the transaction is on line, the operation can be performed in the modes of website, APP and the like, and data generated by the on line transaction can be stored on the server equipment or the cloud server.
Disclosure of Invention
In view of the foregoing, embodiments of the present specification provide a method and an apparatus for processing transaction data based on a blockchain. In the transaction data processing method, transaction data of the transaction can be acquired, the transaction data comprises complete transaction service data generated in each transaction service stage of the transaction, and based on the complete transaction service data, the transaction data of each transaction can completely reflect the whole transaction process of the transaction. And packaging the acquired transaction data into a first block, and recording the first block on a block chain. Therefore, the transaction data of the transaction is completely recorded on the blockchain, the transaction data is prevented from being tampered, the authenticity of the transaction data is further ensured, and the transaction data can be used as evidence for solving transaction disputes. The first block includes a transaction identification and a first hash value generated based on transaction data. Therefore, the transaction dispute resolution party can acquire the first hash value from the block chain based on the transaction identifier and verify the transaction data to be verified based on the first hash value to determine whether the transaction data to be verified is credible.
According to an aspect of an embodiment of the present specification, there is provided a transaction data processing method based on a blockchain, including: acquiring transaction data of a transaction, wherein the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction; packaging the acquired transaction data into a first block, wherein the first block comprises a transaction identifier and a corresponding first hash value, and the first hash value is generated based on the transaction data; and recording the first block on a block chain.
Optionally, in one example of the above aspect, recording the first chunk on a chunk chain includes: broadcasting the first block to a consensus node in a block chain network for consensus processing; and recording the first block on a block chain after the consensus node achieves consensus.
Optionally, in one example of the above aspect, the transaction has an electronic contract defining the responsibility of a party to the transaction, the electronic contract being packaged into a second chunk recorded on a blockchain, the second chunk comprising a contract identification and a corresponding second hash value, the first chunk comprising the contract identification of the electronic contract.
Optionally, in one example of the above aspect, the electronic contract is packaged into the second chunk record on the chunk chain using the following process: acquiring signing data generated in each signing phase of the signing process of the electronic contract; packaging the obtained signing data and the electronic contract data into the second block, wherein the second block comprises the contract identifier, the signing data and a corresponding second hash value; and recording the second block on the block chain.
Optionally, in one example of the above aspect, the first block includes the transaction data and/or the second block includes the electronic contract data and the signing data.
Optionally, in one example of the above aspect, the various signing phases include identity authentication and contract signing.
Optionally, in one example of the above aspect, the respective signing business phases further include at least one of account creation, contract signing initiation, signing notification, contract viewing, willingness authentication, and electronic contract storage.
Optionally, in one example of the above aspect, the transaction has an electronic contract for defining the responsibility of the party to the transaction, the electronic contract is packaged into a second block recorded on a blockchain, the second block includes a contract identification and a corresponding second hash value, the transaction corresponds to an index for recording the correspondence of the transaction identification and the contract identification of the electronic contract.
Optionally, in an example of the above aspect, the first block includes transaction data, and the transaction data processing method further includes: receiving a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier; inquiring transaction service data corresponding to the transaction identification from the block chain; and sending the inquired transaction service data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
Optionally, in an example of the above aspect, the first block includes transaction service data, and the second block includes the electronic contract data, and the transaction data processing method includes: receiving a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier and a contract identifier; inquiring transaction service data corresponding to the transaction identification and electronic contract data corresponding to the contract identification from the block chain; and sending the inquired transaction service data and the electronic contract data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
Optionally, in an example of the above aspect, further comprising: receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises a transaction identifier of a transaction to be resolved and transaction service data to be verified; performing hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified; querying a first hash value corresponding to the transaction identification on the blockchain; comparing the third hash value to the first hash value; and sending notification information used for indicating whether the transaction business data to be verified is available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value.
Optionally, in an example of the above aspect, further comprising: receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises a transaction identifier of a transaction to be resolved, transaction service data to be verified, a contract identifier of an electronic contract to be verified and electronic contract data of the electronic contract to be verified; performing hash calculation on the transaction service data to be verified and the electronic contract data to be verified respectively to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified; querying a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier on the blockchain; comparing the third hash value to the first hash value, and comparing the fourth hash value to the second hash value; and sending notification information for indicating whether the transaction service data to be verified and the electronic contract data to be verified are available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value and the comparison result of the fourth hash value and the second hash value.
According to another aspect of the embodiments of the present specification, there is also provided a method for processing transaction data based on a blockchain, including: receiving a transaction service data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier; inquiring transaction service data corresponding to the transaction identification from the block chain; and sending the inquired transaction service data to the transaction dispute resolution party to enable the transaction dispute resolution party to serve as an evidence for resolving the transaction dispute, wherein the block chain records a first block formed by packaging transaction service data based on transactions, the first block comprises transaction identification information, transaction data and a corresponding first hash value, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transactions.
Optionally, in an example of the above aspect, the block chain records a second block formed by packaging based on the electronic contract data, where the second block includes a contract identifier, the electronic contract data and a corresponding second hash value, the transaction data obtaining request further includes the contract identifier, and querying transaction service data corresponding to the transaction identifier from the block chain includes: and inquiring transaction service data corresponding to the transaction identification and electronic contract data corresponding to the contract identification from the block chain.
According to another aspect of the embodiments of the present specification, there is also provided a method for processing transaction data based on a blockchain, including: receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises transaction service data to be verified and a transaction identifier; performing hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified; querying a first hash value corresponding to the transaction identifier on a blockchain; comparing the third hash value to the first hash value; and sending notification information used for indicating whether the transaction service data to be verified are available to the transaction dispute resolution party based on a comparison result of the third hash value and the first hash value, wherein the block chain records a first block formed by packaging the transaction service data based on the transaction, the first block comprises transaction identification information and a first hash value, the first hash value is generated based on the transaction data of the transaction, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction.
According to another aspect of the embodiments of the present specification, there is also provided a method for processing transaction data based on a blockchain, including: receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises transaction service data to be verified, a transaction identifier, electronic contract data to be verified and a contract identifier; performing hash calculation on the transaction service data to be verified and the electronic contract data to be verified respectively to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified; querying a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier on a blockchain; comparing the third hash value to the first hash value and the fourth hash value to the second hash value; and sending notification information indicating whether the transaction service data to be verified and the electronic contract to be verified are available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value and the comparison result of the fourth hash value and the second hash value, wherein the blockchain records a first block formed by packaging transaction service data based on transaction and a second block formed by packaging transaction service data based on electronic contract data, the first block includes transaction identification information and a first hash value, the first hash value being generated based on transaction data for a transaction, the transaction data includes complete transaction service data generated at each transaction service stage included in the transaction, the second chunk includes a contract identification and a second hash value, the second hash value generated based on the electronic contract data.
According to another aspect of embodiments herein, there is also provided a blockchain-based transaction data processing apparatus, including: the transaction data acquisition unit acquires transaction data of a transaction, wherein the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction; the block generation unit packs the acquired transaction data into a first block, wherein the first block comprises a transaction identifier and a corresponding first hash value, and the first hash value is generated based on the transaction data; and the block recording unit records the first block on a block chain.
Optionally, in an example of the above aspect, the tile recording unit includes: the consensus processing module broadcasts the first block to a consensus node in a block chain network to perform consensus processing; and the block recording module records the first block on a block chain after the consensus node achieves the consensus.
Optionally, in one example of the above aspect, the transaction has an electronic contract defining the responsibility of a party to the transaction, the electronic contract being packaged into a second chunk recorded on a blockchain, the second chunk comprising a contract identification and a corresponding second hash value, the first chunk comprising the contract identification of the electronic contract.
Optionally, in an example of the above aspect, further comprising: a signing data acquisition unit acquires signing data generated in each signing phase of a signing process of the electronic contract; the block generation unit packages the acquired signing data and the electronic contract data into the second block, the second block comprising the contract identifier, the signing data and a corresponding second hash value; and the block recording unit records the second block on the block chain.
Optionally, in one example of the above aspect, the first block includes the transaction data and/or the second block includes the electronic contract data and the signing data.
Optionally, in one example of the above aspect, the transaction has an electronic contract for defining the responsibility of the party to the transaction, the electronic contract is packaged into a second block recorded on a blockchain, the second block includes a contract identification and a corresponding second hash value, the transaction corresponds to an index for recording the correspondence of the transaction identification and the contract identification of the electronic contract.
Optionally, in an example of the above aspect, the first block includes transaction data, and the transaction data processing apparatus further includes: the data request receiving unit receives a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier; the data query unit queries transaction service data corresponding to the transaction identification from the block chain; and the data sending unit sends the inquired transaction service data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
Optionally, in an example of the above aspect, the first block includes transaction service data, the second block includes the electronic contract data, and the transaction data processing apparatus further includes: the data request receiving unit receives a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier and a contract identifier; the data query unit queries transaction service data corresponding to the transaction identifier and electronic contract data corresponding to the contract identifier from the block chain; and the data sending unit sends the inquired transaction service data and the electronic contract data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
Optionally, in an example of the above aspect, further comprising: the method comprises the steps that a verification request receiving unit receives a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises a transaction identifier of a transaction to be resolved and transaction service data to be verified; the hash value processing unit carries out hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified, a first hash value corresponding to the transaction identifier is inquired on the block chain, and the third hash value is compared with the first hash value; and the notification unit sends notification information used for indicating whether the transaction business data to be verified is available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value.
Optionally, in an example of the above aspect, further comprising: the method comprises the steps that a verification request receiving unit receives a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises a transaction identifier of a transaction to be resolved, transaction service data to be verified, a contract identifier of an electronic contract to be verified and electronic contract data of the electronic contract to be verified; a hash value processing unit respectively carries out hash calculation on the transaction service data to be verified and the electronic contract data to be verified to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified, a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier are inquired on the block chain, the third hash value is compared with the first hash value, and the fourth hash value is compared with the second hash value; and the notification unit sends notification information for indicating whether the transaction service data to be verified and the electronic contract data to be verified are available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value and the comparison result of the fourth hash value and the second hash value.
According to another aspect of embodiments herein, there is also provided a blockchain-based transaction data processing apparatus, including: the data request receiving unit receives a transaction service data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier; the data query unit queries transaction service data corresponding to the transaction identification from the block chain; and the data sending unit sends the inquired transaction service data to the transaction dispute resolution party so that the transaction dispute resolution party can serve as an evidence for resolving the transaction dispute, wherein the block chain records a first block formed by packaging transaction service data based on the transaction, the first block comprises transaction identification information, the transaction data and a corresponding first hash value, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction.
Optionally, in an example of the above aspect, the blockchain records a second block formed by packaging based on electronic contract data, where the second block includes a contract identifier, electronic contract data and a corresponding second hash value, the transaction data acquisition request further includes a contract identifier, and the data query unit queries transaction service data corresponding to the transaction identifier and electronic contract data corresponding to the contract identifier from the blockchain; and the data sending unit sends the inquired transaction service data and the electronic contract data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
According to another aspect of embodiments herein, there is also provided a blockchain-based transaction data processing apparatus, including: the method comprises the steps that a verification request receiving unit receives a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises transaction service data to be verified and a transaction identifier; the hash value processing unit carries out hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified, a first hash value corresponding to the transaction identifier is inquired on a block chain, and the third hash value is compared with the first hash value; and the notification unit sends notification information used for indicating whether the transaction service data to be verified is available to the transaction dispute resolution party based on a comparison result of the third hash value and the first hash value, wherein the block chain records a first block formed by packaging the transaction service data based on the transaction, the first block comprises transaction identification information and a first hash value, the first hash value is generated based on the transaction data of the transaction, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction.
According to another aspect of embodiments herein, there is also provided a blockchain-based transaction data processing apparatus, including: the dispute evidence data verification request comprises transaction service data to be verified, a transaction identifier, electronic contract data to be verified and a contract identifier; a hash value processing unit respectively carries out hash calculation on the transaction service data to be verified and the electronic contract data to be verified to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified, a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier are inquired on a block chain, the third hash value is compared with the first hash value, and the fourth hash value is compared with the second hash value; and a notification unit that sends notification information indicating whether the transaction service data to be verified and the electronic contract to be verified are available to the transaction dispute resolvers based on a comparison result of the third hash value with the first hash value and a comparison result of the fourth hash value with the second hash value, wherein the blockchain records a first block formed by packaging transaction service data based on transaction and a second block formed by packaging transaction service data based on electronic contract data, the first block includes transaction identification information and a first hash value, the first hash value being generated based on transaction data for a transaction, the transaction data includes complete transaction service data generated at each transaction service stage included in the transaction, the second chunk includes a contract identification and a second hash value, the second hash value generated based on the electronic contract data.
According to another aspect of embodiments herein, there is also provided an electronic device, including: at least one processor; and a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the blockchain based transactional data processing method as described above.
According to another aspect of embodiments herein, there is also provided a machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform a blockchain based transaction data processing method as described above.
According to another aspect of embodiments herein, there is also provided an electronic device, including: at least one processor; and a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform a blockchain based transaction data acquisition and verification method as described above.
According to another aspect of embodiments herein, there is also provided a machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform a blockchain based transaction data acquisition and verification method as described above.
Drawings
A further understanding of the nature and advantages of the present disclosure may be realized by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. The accompanying drawings, which are included to provide a further understanding of the embodiments of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the detailed description serve to explain the embodiments of the specification, but are not intended to limit the embodiments of the specification. In the drawings:
FIG. 1 shows a schematic diagram of an example environment;
FIG. 2 is a schematic diagram illustrating one example of a system architecture for transaction data processing of embodiments of the present description;
fig. 3 is a flowchart illustrating an example of a data processing method based on a block chain according to an embodiment of the present specification;
FIG. 4 illustrates a schematic diagram of one example of a transaction including multiple transaction business phases of an embodiment of the present description;
FIG. 5 is a schematic diagram illustrating one example of complete transaction business data generated by a transaction of an embodiment of the present description;
FIG. 6 shows a schematic diagram of an example of a consensus process of an embodiment of the present specification;
fig. 7 is a diagram illustrating an example of formats of a pre-preparation message, a preparation message, and an acknowledgement message in a consensus process of an embodiment of the present specification;
fig. 8 shows a flowchart of one example of packing an electronic contract and signing data into a second chunk record on a blockchain of embodiments of the present specification;
fig. 9 is a schematic diagram showing an example of a signing process of an electronic contract of the embodiment of the present specification;
FIG. 10 illustrates a flow diagram of one example of an embodiment of the present description for obtaining transaction data from a blockchain;
FIG. 11 shows a flowchart of one example for obtaining transaction data and electronic contracts from a blockchain in an embodiment of the present description;
FIG. 12 illustrates a flow diagram of one example of verifying whether transaction data is available based on a blockchain in an embodiment of the present description;
FIG. 13 illustrates a flow chart of one example of verifying whether transaction service data and an electronic contract are available based on a blockchain in an embodiment of the present description;
fig. 14 is a block diagram illustrating an example of a blockchain-based transaction data processing apparatus according to an embodiment of the present specification;
FIG. 15 illustrates a block diagram of one example of a transaction data processing device that obtains transaction data from a blockchain in accordance with embodiments of the present description;
fig. 16 is a block diagram illustrating an example of a transaction data processing device that verifies transaction data based on a blockchain according to an embodiment of the present specification;
fig. 17 illustrates a block diagram of an electronic device for recording transaction data in a blockchain in accordance with an embodiment of the present description;
fig. 18 is a block diagram of an electronic device for obtaining transaction data from a blockchain in an embodiment of the present description; and
fig. 19 shows a block diagram of an electronic device for verifying transaction data and an electronic contract based on a blockchain in an embodiment of the present description.
Detailed Description
The subject matter described herein will be discussed with reference to example embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thereby implement the subject matter described herein, and are not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as needed. In addition, features described with respect to some examples may also be combined in other examples.
As used herein, the term "include" and its variants mean open-ended terms in the sense of "including, but not limited to. The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first," "second," and the like may refer to different or the same object. Other definitions, whether explicit or implicit, may be included below. The definition of a term is consistent throughout the specification unless the context clearly dictates otherwise.
FIG. 1 is a schematic diagram of an example environment provided by an example embodiment. As shown in fig. 1, the example environment 100 allows entities to participate in a blockchain network 102. The blockchain network 102 may be a public type, a private type, or a federation type of blockchain network. The example environment 100 may include computing devices 104, 106, 108, 110, 112 and a network 114; in an embodiment, the Network 114 may include a Local Area Network (LAN), Wide Area Network (WAN), the internet, or a combination thereof, and is connected to websites, user devices (e.g., computing devices), and backend systems. In one embodiment, the network 114 may be accessed through wired and/or wireless communication. 045 in some cases, the computing devices 106, 108 may be nodes of a cloud computing system (not shown), or each computing device 106, 108 may be a separate cloud computing system, comprising multiple computers interconnected by a network and operating as a distributed processing system.
In an embodiment, computing devices 104-108 may run any suitable computing system that enables them to act as nodes in blockchain network 102; for example, the computing devices 104-108 may include, but are not limited to, servers, desktop computers, laptops, tablet computing devices, and smartphones. In an embodiment, the computing devices 104-108 can be affiliated with a related entity and used to implement a corresponding service, which can be used to manage transactions between an entity or entities, for example.
In one embodiment, the computing devices 104-108 respectively store a blockchain ledger corresponding to the blockchain network 102. The computing device 104 may be (or include) a web server for providing browser functionality that may provide visualization information related to the blockchain network 102 based on the network 114. In some cases, the computing device 104 may not participate in the blockchain verification, but rather monitor the blockchain network 102 to determine when other nodes (e.g., which may include the computing device 106 and 108) agree, and generate a corresponding blockchain visualization user interface accordingly.
In an embodiment, computing device 104 may receive a request initiated by a client device (e.g., computing device 110 or computing device 112) for a blockchain visualization user interface. In some cases, the nodes of the blockchain network 102 may also act as client devices, such that a user of the computing device 108 may send the request to the computing device 104 using a browser running on the computing device 108.
In response to the request, computing device 104 may generate a blockchain visualization user interface (e.g., a web page) based on the stored blockchain ledger and send the generated blockchain visualization user interface to the requesting client device. If blockchain network 102 is a private type or a federated type blockchain network, the request for the blockchain visual user interface may include user authorization information, which may be verified by computing device 104 before generating and sending the blockchain visual user interface to the requesting client device, and the corresponding blockchain visual user interface returned after verification.
The blockchain visualization user interface may be displayed on the client device (e.g., as may be displayed in user interface 116 shown in fig. 1). When the blockchain ledger is updated, the display content of the user interface 116 may be updated accordingly. Further, user interaction with user interface 116 may result in requests to other user interfaces, such as a search results page that displays a block list, block details, transaction list, transaction details, account list, account details, contract list, contract details, or results of a user conducting a search of the block chain network, and so forth.
FIG. 2 illustrates a schematic diagram of one example of a system architecture 200 for transaction data processing of embodiments of the present specification.
As shown in fig. 2, the system architecture 200 for transaction data processing may include a blockchain client and a blockchain network end, wherein the blockchain client is communicatively connected to a blockchain node in the blockchain network. The blockchain client may include a buyer client 211, a seller client 213, an electronic contract signing end 217, a third party data requester 230, a third party data provider 250, and the like. The blockchain network end may include a transaction service provider server 220, a data acquisition node 240, a data verification node 260, other blockchain nodes, and the like.
The buyer client 211 and the seller client 213 are both connected to the transaction service provider server 220, and the buyer client 211 and the seller client 213 perform transactions through the transaction service provider server 220.
For example, in the scenario of stock exchange, the exchange service provider server 220 may be a stock exchange platform server, providing a stock exchange platform for each stock exchange user. Both the buyer and the seller are registered users of the security trading platform, and the security trading is carried out by using the account which is successfully registered. On the transaction platform provided by the transaction service provider server 220, the seller logs in a seller account on the seller client 213, and the buyer logs in a buyer account on the buyer client 211, and then securities transactions are performed through the seller account and the buyer account, respectively. Transaction data, logs, and the like generated during the transaction are stored in the transaction service provider server 220.
The electronic contract signing terminal 217 is in communication connection with the transaction service provider server 220, the electronic contract signing terminal 217 is used for executing the operation of signing electronic contracts of transaction parties, and can acquire relevant data in the electronic contract signing process, and the electronic contract signing terminal 217 can send the data to the transaction service provider server 220 for storage. For example, the electronic contract signing terminal 217 may generate an electronic contract and display the generated electronic contract on a display screen, and after confirming that the contract is correct, each party in the transaction may input a respective signature at the electronic contract signing terminal 217, where the signature may include at least one of an electronic signature, a fingerprint, a human face, a password, and the like. The electronic contract signing end 217 may obtain signature data of transaction parties and other related data, such as time stamps, and send the obtained data to the transaction service provider server 220.
In one example, the electronic contract signing end 217 and the buyer client 211 or the seller client 213 may be or be part of the same equipment end, which may process transactions as a buyer client or a seller client and may also perform electronic contract signing operations.
In this example, the transaction service provider server 220, as a blockchain node in the blockchain network 214 or a component thereof, can package the data received from the buyer client 211 and the seller client 213 and/or the data received from the electronic contract signing terminal 217 into blocks to be recorded on the blockchain 216, and the transaction data and/or the electronic contract related data recorded on the blockchain 216 cannot be tampered, so that the authenticity of the data is ensured.
In addition, the data acquisition node 240 may be a blockchain node in the blockchain network 214 or a component thereof, and the data acquisition node 240 may query and acquire transaction service data of a transaction and/or related data of an electronic contract signing and the like from the blockchain 216. The data acquisition node 240 may include at least one of a securities trading supervisory organization, a judicial organization, and a notary organization. The securities custody authority may obtain data associated with each transaction from blockchain 216 for review and analysis, thereby achieving the purpose of monitoring the transactions. The judicial organization may obtain data of one or more transactions from blockchain 216 as judicial evidence, and the notary organization may obtain relevant data of the transaction directly from blockchain 216 when needing to notarize the transaction.
In one example, the data acquisition node 240 is a judicial agency and is communicatively connected with the third-party data requestor 230. When a trade dispute occurs, both parties of the trade request the judicial institution to resolve, at least one of the two parties of the trade can be used as a third-party data requesting party to request the judicial institution to acquire the relevant trade data of the trade from the blockchain 216, and the judicial institution can use the trade data acquired from the blockchain 216 as judicial evidence.
In addition, the data verification node 260 may also be a blockchain node in the blockchain network 214 or a component thereof, and the data verification node 260 may query a hash value corresponding to the transaction service data and/or the electronic contract data from the blockchain 216, and verify the transaction service data to be verified and/or the electronic contract data to be verified based on the queried hash value. The data validation node 260 may include at least one of a securities trading supervision agency, a judicial agency, and a notary agency. A security trading supervision agency, a judicial agency, or a notary agency as the data verification node 260 may verify trading service data and/or electronic contract data acquired from a third party to determine whether the acquired data is authentic.
In one example, the data validation node 260 is a securities trading supervisor that oversees the trading of securities to avoid the occurrence of fraudulent trades. The securities exchange overseer may be communicatively coupled to the third party data provider 230, and when the securities exchange overseer checks a certain transaction, each party and/or the transaction service provider server of the transaction may act as the third party data provider 230 to provide the data verification node 260 with the relevant transaction data of the transaction. After the data verification node 260 receives the relevant transaction data, hash calculation is performed on the data to obtain a hash value, the data verification node 260 queries the hash value corresponding to the relevant transaction data of the transaction from the blockchain 216, and compares the queried hash value with the calculated hash value to determine whether verification passes.
Further, in one example, the transaction service provider server 220, the data acquisition node 240, and the data validation node 260 may belong to or be part of the same blockchain node in the blockchain network 214. The block link point can realize the functions of the transaction service provider server 220, the data acquisition node 240 and the data verification node 260.
Furthermore, in another example of the embodiment of the present specification, the transaction service provider server 220 in the system architecture 200 belongs to a blockchain client, and the transaction service provider server 220 is connected in communication with at least one blockchain node in the blockchain network 214.
In this example, the transaction service provider server 220 can receive transaction data during a transaction from the buyer client 211 and the seller client 213 and/or signing data during an electronic contract signing process from the electronic contract signing terminal 217 and send the received data to blockchain nodes that package the transaction data and/or the electronic contract signing data into blockchains 216 for recordation by the blockchain nodes.
Fig. 3 is a flowchart illustrating an example of a data processing method based on a block chain according to an embodiment of the present specification.
The transaction data processing method shown in fig. 3 may be performed by a blockchain node in a blockchain network, for example, the transaction service provider server as the blockchain node in fig. 2. The transaction service provider server may be in communication connection with each client that performs a transaction operation, and may record the collected transaction data on the blockchain. In one example, a blockchain network as used by embodiments of the present specification may include an ethernet house network.
As shown in FIG. 3, at block 310, transaction data for a transaction is obtained.
In one acquisition mode, the transaction service provider server as a blockchain node can directly acquire transaction data of transactions from local.
In another acquisition mode, the transaction service provider server sends transaction data of the transaction to the block link point in communication connection, so that the block link point can acquire the transaction data of the transaction. In one example, the transaction service provider server may actively send local transaction data to the blockchain node, for example, the transaction service provider server sends collected transaction data to the blockchain node each time the transaction service provider server collects transaction data of a transaction. In another example, the transaction service provider server may send local transaction data to the blockchain node in response to a transaction data request by the blockchain node.
In the embodiments of the present specification, the transaction may include at least one of a security transaction, a money transaction, a stock right transaction, a commodity transaction, and a property transaction. Each transaction (or referred to as a transaction) may include the entire process from transaction initiation to transaction completion, including transaction success, transaction failure, and transaction cancellation, with transaction completion indicating that the transaction has ended. The processing of different transactions may differ.
Each transaction may include a plurality of transaction service phases, and the transaction service phases may be mutually connected according to a transaction flow sequence of the transaction, so that the transaction service phases form a complete transaction.
Taking fig. 4 as an example, fig. 4 shows a schematic diagram of an example of a transaction including multiple transaction business phases of an embodiment of the present specification. The transactions shown in FIG. 4 are security transactions, and a security transaction may be performed in the order of opening an account, committing, making a deal, and clearing a deal. Opening an account includes opening a security account and a fund account, the entrusting is entrusting of a security user to a security institution, and entrusting items include buying, selling and the like. The securities mechanism performs execution of a securities trade according to the contents of the order, and the clearing deal performed after the deal includes adding money to the fund account of the person who sells securities, reducing the number of securities in the fund account, adding securities to the fund account of the person who buys securities, and reducing money in the fund account.
The transaction phase included in the transaction may be deterministic, and the order of execution of the individual transaction phases is also deterministic. In the transaction process, the next transaction service stage can be started only after the previous transaction service stage is completed. For example, the transaction process includes ordering, payment and post-sale, and the payment phase may be entered only after ordering is completed and the post-sale phase may be entered after payment is completed.
Different types of transactions may include different transaction business phases. For example, the transaction phases for a stock transaction may include opening an account, physical authentication, double recording video, placing an order, payment, transaction inquiry, transaction notification, and after-sale, and the transaction phases for a currency transaction may include physical authentication, double recording video, signing up, placing an order, and payment.
In the embodiment of the present specification, each transaction service stage may generate corresponding transaction service data during the execution process, for example, the real person authentication stage may generate data such as authentication time and authentication information, the double-recording video stage may generate data such as audio, video and corresponding time stamp, and the payment stage may generate data such as payment amount and payment time.
The acquired transaction data may include complete transaction data generated at each transaction phase included in the transaction. In one example, the complete transaction data generated by each transaction phase may include all data generated by the transaction phase, and all transaction data generated by all transaction phases may constitute a complete transaction. All transaction service data generated in each transaction service stage are used as complete transaction service data of the transaction, so that the integrity of the transaction is ensured, and convenience is provided for inquiring any data of the transaction.
Taking fig. 5 as an example, fig. 5 is a schematic diagram illustrating an example of complete transaction business data generated by a transaction according to an embodiment of the present specification. As shown in fig. 5, during a security transaction, transaction data generated during an account opening stage may include account information, real person authentication information, video data, timestamp information, and operation log, and the account information includes security account information and fund account information. The transaction data generated in the delegation phase may include delegation content information, principal identity information, an operation log, timestamp information, delegation request information, and the like, wherein the delegation content information may include a delegated security account number, time information, a transaction direction (buy or sell), a security type, a security quantity, and the like. The transaction data generated in the trading stage can include the name of the securities, the number of purchases and sales, the bidding method, the operation log, time stamp information and the like. The transaction data generated during the clearing transaction stage may include increased amount information in the fund account of the party selling the securities and decreased amount information in the fund account of the party buying the securities, decreased amount information in the fund account of the party buying the securities and increased amount information in the fund account of the party.
In another example, the data of the specified data type in all the data generated by each transaction phase is taken as the complete transaction data of the transaction phase, and the specified data types of different transaction phases may be different. The data of the specified data type of the transaction service phase may include part of the data generated by the phase, the part of the data may be data other than redundant data, and may include all data generated by the phase. The data type designated by each transaction business phase can comprise important data or main data of the business phase, privacy data, dispute-prone data and the like. In this example, when the data of the specified data type is partial data, only the partial data generated at the transaction business stage is extracted, reducing the data amount of the acquired transaction data, so that the storage space on the blockchain can be saved when the transaction data needs to be stored on the blockchain.
Taking fig. 5 as an example, the data of the specified data type in the account opening stage includes account information, real person authentication information, and video data, the data of the specified data type in the entrusting stage includes entrusting content information and offeror identity information, the data of the specified data type in the transaction stage includes security name, purchase quantity information, and timestamp information, and the data of the specified data type in the clearing and delivery stage includes increase money information and decrease security quantity information of a party selling securities, decrease money information of a party buying securities, and increase security quantity information. The above-mentioned specified data may constitute a complete stock exchange.
In one example, the complete transaction business data generated by each transaction business phase may be obtained upon completion of the transaction business phase. In another example, the complete transaction data generated by each transaction phase is stored locally in the transaction service providing segment server when the transaction phase is completed, and the transaction data generated by all transaction phases is acquired as the transaction data of the transaction when the transaction is completed.
And determining the transaction service data of the specified data type generated in each transaction service stage as the complete transaction service data of the transaction service stage, and then taking the complete transaction service data generated in all transaction service stages as the transaction data of the transaction. Therefore, only data of the specified data type is collected aiming at each transaction service stage, the data processing efficiency can be improved, and the data volume needing to be processed is reduced in the subsequent data processing.
At block 320, the acquired transaction data is packaged into a first block.
In one example, the obtained transaction data may be packaged into a first tile based on a data volume of the transaction data and a capacity of the tile. The first block may include one or more blocks, and when the first block includes a plurality of blocks, the acquired transaction data is divided into a plurality of parts, and each part of the transaction data is packed into one block. The transaction data is divided by the number corresponding to the number of the corresponding blocks.
In this example, when the data amount of the transaction data is not greater than the capacity of the tile, the transaction data may be packed into one tile as the first tile. When the data volume of the transaction data is larger than the capacity of the block, the transaction data can be divided according to the capacity of the block, and the data volume of each divided transaction data is not larger than the capacity of the block. Then packaging each transaction data into a block, wherein all the obtained blocks are the first blocks.
In one example of the present specification, the first block includes a transaction identification and a corresponding first hash value. The transaction identification is in a one-to-one correspondence with the transaction, and in one example, the first hash value may be generated based on transaction data contained in the first block. In another example, the first hash value may also be generated based on the transaction data and the transaction identification contained in the first chunk.
Before storing to the block, the transaction data needs to be subjected to hash calculation processing. In one example, the obtained transaction data may be hashed to obtain a corresponding first hash value.
The hash calculation is a process of converting an image data frame (provided as character string data) into a fixed-length first hash value (also provided as character string data). After the hash calculation is performed on the image data frame, even if the image data frame is slightly changed, a completely different first hash value is obtained. The first hash value is typically generated by hashing the frame of image data using a hash function. Examples of hash functions include, but are not limited to, Secure Hash Algorithm (SHA) -256, which outputs a 256-bit first hash value.
A plurality of transaction traffic data in the transaction data is hashed and stored in the chunk. For example, two transaction data are hashed to obtain two hash values, and then the two obtained hash values are hashed again to obtain another hash value. This process is repeated until a single hash value is obtained for all transaction traffic data to be stored in the block. This hash value is called a Merkle root hash and is stored at the head of the chunk. Any change to the transaction data will cause its hash value to change, eventually causing the Merkle root hash value to change.
In one example, when the first block includes one block, the first hash value included in the one first block is generated based on all transaction data of the transaction. When the first block comprises a plurality of blocks, each block comprises the transaction identification, and the first hash value comprised by each block is generated based on a piece of transaction data corresponding to the block. A corresponding piece of transaction data is different for each block, such that each block includes a different first hash value.
For example, transaction data for one transaction is divided into 3 shares: the transaction data processing method comprises the steps of obtaining a first hash value N1 by performing hash calculation on the first transaction data, obtaining a first hash value N2 by performing hash calculation on the second transaction data, and obtaining a first hash value N3 by performing hash calculation on the third transaction data, wherein N1, N2 and N3 are different. The first transaction data is packed into a first tile B1 comprising N1, the second transaction data is packed into a first tile B2 comprising N2, and the third transaction data is packed into a first tile B3 comprising N3.
In another example of the present specification, the first tile may further include transaction business data, whereby complete transaction business data for a transaction is also recorded on the tile chain. The transaction service data recorded on the blockchain cannot be tampered, so that a transaction dispute resolution party can directly obtain the complete transaction service data of the transaction from the blockchain, and the complete transaction service data obtained from the blockchain is credible and can be directly used as evidence for transaction dispute resolution.
In this example, when the first block includes a plurality of blocks, the transaction data of the transaction is divided into several parts, and each of the divided transaction data includes a part of the transaction service data. Each first block comprises transaction business data corresponding to one transaction data.
At block 330, the first tile is recorded on the tile chain.
In one example, a first block may be broadcast to a consensus node in a blockchain network for a consensus process, and the first block may be recorded on the blockchain after the consensus node achieves consensus.
Fig. 6 is a schematic diagram showing an example of the consensus process of the embodiments of the present specification. In this specification, the first hash value and the image index information may be considered as transaction data in a block chain. In the example of fig. 6, the block link point where the image pickup apparatus is located serves as a master node (i.e., accounting node, hereinafter referred to as master node R) of the block link network0）。
Master node R0Broadcasting the packed blocks to all common nodes in the blockchain network for common processing, e.g. master node R0Broadcasting the packed blocks to a backup node R1、R2And R3And (5) performing consensus processing. Note that the consensus process is shown to include 4 network nodes R0，R1，R2And R3The consensus process may also include any suitable number of network nodes for illustrative purposes only.
In the embodiments of the present specification, the consensus process may be implemented using PoW (workload certification algorithm), PoS (equity certification algorithm), PBFT (practical byzantine fault-tolerant algorithm), and the like. The following description will be made by taking the PBFT consensus process as an example.
As shown in fig. 6, the procedure of the PBFT consensus process includes: a Pre-preparation phase (Pre-preparation) 610, a preparation phase (preparation) 620, and a validation phase (Commit) 630.
Specifically, at 610, master node R0Packetizing vehicle data segments to be recorded into a blockchain into a message m, then generating a Pre-prepare message Pre-prepare, and sending (e.g., broadcasting) the Pre-prepare message Pre-prepare to the backup node R within a given time interval1、R2And R3. The Pre-prepare message Pre-prepare indicates the master node R0A consensus process is being initiated.
In an embodiment of the present specification, as shown in fig. 7, the format of the Pre-preparation message Pre-preparation may be:<<PRE-PREPARE，epoch，seq，D（m），signature-p>，m，j>. Here, "PRE-PREPARE" indicates the protocol identification of the Preprepare message and "epoch" indicates R0The era of the master node, "seq" represents the proposal number of the proposal that needs to be consensus (i.e., adding the block to the blockchain 216), "D (m)" represents the digest of the request message set, "signature-p" represents R0"m" denotes the specific content of the request message (i.e., the specific content of each piece of authentication information in the block), and "j" denotes R0The node identification of (2). Here, d (m) is obtained by performing a hash calculation on each authentication information set in the block.
In the preparation phase 620, for each backup node (R)1、R2Or R3) After receiving the Pre-preparation message Pre-preparation and detecting that the Pre-preparation message Pre-preparation is legitimate, the Pre-preparation message Pre-preparation may be stored in a local log, and a preparation message preparation for responding to the Pre-preparation message Pre-preparation may be generated and then broadcast to other nodes. The Prepare message Prepare indicates that the backup node has received the Pre-Prepare message Pre-Prepare from the primary node and is sending a reply in response to the Pre-Prepare message Pre-Prepare.
Accordingly, each backupThe node will also receive the Pre-prepare message Pre-prepare sent by the other backup node. With a backup node R1For example, backup node R1Receiving a master node R0After the Pre-Prepare message Pre-Prepare is transmitted, the generated Pre-Prepare message is broadcast to the master node R0Backup node R2And R3. Accordingly, the backup node R1Will also receive the master node R0Backup node R2And R3The transmitted preparation message Prepare.
In this description, the Prepare message Prepare broadcast by the backup node may be used to indicate the consensus commitment made by the backup node during the Prepare phase 620.
In this specification, as shown in fig. 7, the format of the preparation message Prepare may be: < PREPARE, epoch, seq, D (m), i, signature-i >. Here, "PREPARE" denotes a protocol identification of the preparation message PREPARE, "i" denotes a node identification of the node that transmitted the preparation message PREPARE, and "signature-i" denotes a signature of the node that transmitted the preparation message PREPARE. The meaning of "epoch", "seq", and "d (m)" in the preparation message Prepare is the same as that of "epoch", "seq", and "d (m)" in the above-described preparation message Pre-Prepare.
In the acknowledgement phase 630, when the network node receives a sufficient number of preparation messages Prepare from other network nodes, the network node determines that consensus has been reached. For example, if the primary node R0 or backup nodes R1, R2, or R3 receive qurum (e.g., 2f + 1, where f represents the number of failed network nodes) Prepare messages Prepare, it is determined that consensus is achieved between the network nodes. The master node R0 or the backup node R1, R2 or R3 then broadcasts an acknowledgement message Commit to the other nodes.
In this specification, as shown in fig. 7, the format of the acknowledgment message Commit may be: < COMMIT, epoch, seq, D (m), p, signature-p >. Wherein "COMMIT" represents a protocol identification of the acknowledgment message COMMIT, "p" represents a node identification of a node that transmits the acknowledgment message COMMIT, and "signature-p" represents a signature of the node that transmits the acknowledgment message COMMIT. The meaning of "epoch", "seq" and "d (m)" in the acknowledgment message Commit is the same as that of "epoch", "seq" and "d (m)" in the aforementioned Pre-preparation message Pre-preparation.
In this description, a node sends a confirmation message Commit and stores the confirmation message Commit in a local log to represent consensus commitments made by the node during the confirmation phase 630.
After reaching consensus for the initiated proposal as above, the master node records the block into the blockchain, thereby completing the recording of the first block into the blockchain.
In addition, before the transaction data are packaged into the first block, encryption processing can be carried out on the acquired transaction data, so that information leakage caused by the fact that the transaction data are known by other common identification nodes is avoided. Accordingly, in this case, the encrypted transaction data is used to calculate the first hash value of the transaction data. When the transaction data is stored in the block, the encrypted transaction data is also stored in the block. Further, it is to be noted that the encryption for the transaction data may include encrypting all transaction service data included in the transaction data or encrypting a part of the transaction service data included in the transaction data.
Examples of encryption methods for transaction data include, but are not limited to, symmetric encryption, asymmetric encryption, homomorphic encryption, and the like. Symmetric encryption may use a single key for both the encryption process of encrypting (generating ciphertext from plaintext) and decrypting (generating plaintext from ciphertext) transaction data. In symmetric encryption, multiple nodes may have the same key, so each node may encrypt/decrypt transaction data.
Asymmetric encryption may use a key pair to encrypt transaction data. Specifically, the data recording node 230 may encrypt the transaction data using a public key of a public/private key pair at the transaction data application side, then digitally sign the encrypted transaction data using a private key of the public/private key pair at the data recording node 230, and send the digitally signed encrypted data to a consensus node in the block chain, where the consensus node decrypts and verifies the encrypted data using the public key of the public/private key pair of the data recording node 230, and records the encrypted data on the block chain after the consensus node agrees. In this case, after obtaining the encrypted transaction data from the blockchain, the transaction data application party may decrypt the encrypted transaction data by using its own private key, thereby obtaining the plaintext data of the transaction data.
As described herein, the blockchain network 214 is provided in the form of a peer-to-peer network that includes a plurality of blockchain nodes that are each used to persist a blockchain 216 (also referred to as a blockchain ledger 216) formed by blockchain data. Only one blockchain 216 is shown in fig. 2, but there may be multiple blockchains 216 or copies thereof in the blockchain network, e.g., one blockchain 216 or copy thereof may be maintained for each blockchain link point.
It is further noted that the embodiment described in fig. 3 is implemented in a block chain recording manner based on the consensus protocol. In other embodiments of the present specification, the block chain record may be implemented without the need of consensus processing, for example, a trusted account book without the need of consensus processing.
As described above with reference to fig. 2 to 7, a transaction data processing method for recording transaction data onto a blockchain according to an embodiment of the present specification is described. By using the transaction data processing method, the acquired transaction data including the complete transaction service data generated in each transaction service stage of the transaction can be packaged into a first block, and the first block is recorded on the block chain. Therefore, the transaction data of the transaction is completely recorded on the blockchain, the transaction data is prevented from being tampered, the authenticity of the transaction data is further ensured, and the transaction data can be used as evidence for solving transaction disputes. Further, the first chunk includes a transaction identification and a first hash value generated based on the transaction data. Therefore, the transaction dispute resolution party can acquire the first hash value from the block chain based on the transaction identifier and verify the transaction data to be verified based on the first hash value to determine whether the transaction data to be verified is credible.
Further, the transaction may be performed under the specifications of a contract, e.g., the transaction may be executed before each party signs a contract for the transaction, which may be in the form of an electronic file or paper. The following description will be given taking an electronic contract as an example. The electronic contract for a transaction is used to define the responsibilities of the parties to the transaction, with the transaction being conducted under the responsibilities defined by the electronic contract. For example, the parties involved in the transaction include both the buyer and the seller, and the electronic contract for the transaction may specify the payment amount and payment method of the buyer, and may specify the transaction time limit and after-sale of the seller. If either of the buyer and seller does not fulfill the obligation of the electronic contract, it can be determined that the action is a breach.
In one example, each transaction may be one-to-one with an electronic contract, that is, each electronic contract is limited to being valid for only the corresponding one of the transactions. In another example, an electronic contract may correspond to multiple transactions that are conducted under the constraints of the electronic contract.
In one example, the second chunk recorded on the chunk chain for only the electronic contract is packaged, and the specific process may refer to the operations of blocks 320 and 330 described above. In this example, the second chunk may include a contract identification and a corresponding second hash value. The electronic contract is in one-to-one correspondence with the contract identifier. In one example, the second hash value may be generated based on the electronic contract data. In another example, the second hash value may also be generated based on the electronic contract data and the contract identification.
Based on this, after the chain is linked in the second block, the second hash value corresponding to the corresponding electronic contract can be queried in the block chain according to the contract identifier, so that the electronic contract to be verified is verified by using the second hash value.
In another example, there is one signing process for each electronic contract that produces signing data that may reflect the compliance and legitimacy of the electronic contract. Based on this, the second chunk can be packaged for the electronic contract and the signed data to be recorded on the chunk chain. At this time, in one example, the corresponding second hash value may be generated based on the electronic contract data and the signed data, and in another example, the corresponding second hash value may also be generated based on the electronic contract data, the signed data, and the contract identification.
Fig. 8 shows a flowchart of one example of packing an electronic contract and signing data into a second chunk recorded on a blockchain of an embodiment of this specification.
As shown in fig. 8, at block 810, signing data generated during various signing phases of the signing process for the electronic contract is obtained.
In this example, the signing process may be different for different electronic contracts, the signing phases included in different signing processes may be different, and the signing data produced by different signing phases is different.
In one example, the various signing phases may include identity authentication and contract signing. The identity authentication is performed before the signing operation is performed to confirm that the person who performed the signing operation is the principal, and the generated signing data includes matching personal account information, face authentication information, and the like.
The contract signing phase is to perform signing operations such as signing, fingerprint entry, etc. The signing data generated in the contract signing stage comprises information such as signatures, seals and fingerprints of both parties of the contract.
In another example, the various signing business phases may further include at least one of account creation, contract signing initiation, signing notification, contract viewing, willingness authentication, and electronic contract storage.
Fig. 9 is a schematic diagram showing an example of the signing process of the electronic contract of the embodiment of the present specification. As shown in fig. 9, in the initial stage of signing the electronic contract, an account needs to be created and the electronic contract needs to be signed to initiate a signing operation. Thus, the various signing business phases may include account creation, contract creation, and contract signing initiation.
The signature data generated in the account creation phase can include created account information, timestamp information and the like, the signature data generated in the contract creation phase can include created electronic contract data, timestamp information and the like, and the signature data generated in the contract signing initiation phase can include initiated notification information, initiator information, initiated time information and the like.
After contract signing is initiated, the signing process proceeds to a signing notification phase, which is a phase of notifying each participant of the electronic contract, and the signing data generated in the signing notification phase may include notification information issued to each participant, response information of each participant, timestamp information, and the like.
Before signing the operation, the contract needs to be viewed and authenticated. Each participant views the electronic contract in a contract viewing stage, and the signing data generated in the contract viewing stage can comprise request data for requesting to view the contract, requester information, request time information and the like. The authentication may include identity authentication and willingness authentication for confirming whether each participant is voluntary, and the signed data generated in the willingness authentication phase may include willingness authentication information and the like.
After the completion of the contract signing phase, a valid electronic contract is generated. At this time, each participant can view the generated electronic contract to confirm that the electronic contract is error-free. Then, it proceeds to an electronic contract storage stage for storing the electronic contract, and the generated signing data includes the stored address information and time information so as to acquire the electronic contract based on the address information.
At block 820, the obtained signing data and electronic contract data are packaged into a second block.
The second chunk may include one chunk or multiple chunks, and the second chunk may include the contract identification, the signing data, and a corresponding second hash value. In one example, the second hash value may be generated based on the electronic contract data, at which point the second hash value may be used to verify the corresponding electronic contract.
In another example, the second hash value may be generated based on the signing data and the electronic contract data together. In this case, the second hash value may be used to verify the corresponding electronic contract and the signing data corresponding to the electronic contract, and when the electronic contract passes the verification, the signing data passing the verification may further confirm the authenticity of the electronic contract, thereby enhancing the reliability of the electronic contract.
The second block includes signing data that allows the transaction data application to obtain or verify the electronic contract while obtaining corresponding signing data for the electronic contract from the block chain, which can be used to verify the authenticity of the electronic contract.
In one example, the second tile may also include electronic contract data. The electronic contract data is recorded on the block chain, so that malicious tampering of the electronic contract can be prevented, and the authenticity of the electronic contract is further ensured.
At block 830, a second block is recorded on the block chain.
The specific operational procedures of blocks 820 and 830 may refer to the operations of blocks 320 and 330 described above.
In addition, in the case that the transaction has an electronic contract, the first block may further include a contract identifier corresponding to the electronic contract, so that the corresponding first hash value may be queried according to the transaction identifier, the contract identifier corresponding to the transaction may be queried, and then the corresponding second hash value may be queried according to the contract identifier. And verifying the transaction data to be verified and the electronic contract based on the first hash value and the second hash value to determine whether the transaction data and the electronic contract can be used as evidence for solving the transaction dispute.
In another example of an embodiment of the present specification, the transaction has an electronic contract for defining the responsibility of a party to the transaction, the electronic contract being packaged into a second chunk recorded on the blockchain, the second chunk including the contract identification and a corresponding second hash value.
In addition, the transaction correspondence has an index for recording the correspondence of the transaction identification with the contract identification of the electronic contract. The index can correspondingly associate the transaction with the electronic contract, so that the electronic contract corresponding to the transaction recorded on the blockchain can be inquired according to the index without containing a contract identifier in the first block, the data volume included in the first block is reduced, and the storage space of the blockchain is saved.
Specifically, each transaction corresponds to a transaction identifier, after the transaction identifier of the transaction is determined, a contract identifier corresponding to the transaction identifier may be determined from the index, and then, the contract identifier matching with the determined contract identifier is queried on the blockchain, so as to obtain a corresponding second hash value. The second hash value at this time may be generated based on the electronic contract data, or may be generated based on the electronic contract data and the contract identification.
In one example of an embodiment of the present specification, the first tile may further include transaction traffic data. Therefore, the transaction data on the blockchain can be inquired based on the contract identification, the transaction data of the transaction can be prevented from being tampered, and the authenticity of the transaction data is ensured. Therefore, when a transaction dispute aiming at the transaction occurs, the transaction dispute resolution party can directly acquire the transaction data from the blockchain to serve as evidence of transaction dispute resolution, and the reliability of the evidence is ensured.
When the first block comprises transaction service data and the second block comprises electronic contract data, the transaction dispute resolution party can directly obtain the transaction data and the electronic contract of the transaction from the block chain, combine the transaction data and the electronic contract to serve as evidence of transaction dispute resolution, use the transaction data as evidence of fact process, and use the electronic contract for responsibility division.
Fig. 10 shows a flowchart of an example for acquiring transaction data from a blockchain according to an embodiment of the present disclosure. The example shown in fig. 10 may be performed by the data acquisition node 240, and the data acquisition node 240 may be a blockchain node belonging to or communicatively connected with institutions such as financial regulatory agencies, judicial accreditation centers, and notarization institutions. Data acquisition node 240 may provide evidence of the resolution of the transaction dispute for these institutions.
In the example of fig. 10, the first chunk may include transaction traffic data, a transaction identification, and a first hash value.
As shown in FIG. 10, at block 1010, a transaction data acquisition request may be received from a transaction dispute resolution party. The transaction data acquisition request may include a transaction identification. In one example, the transaction dispute resolution party may be at least one of a financial regulatory agency, a judicial accreditation center, and a notary office, among others.
At block 1020, transaction service data corresponding to the transaction identification is queried from the blockchain. The inquired transaction service data is the complete transaction service data of the transaction corresponding to the transaction identification.
In an example, when the first block includes a plurality of blocks, each first block includes a transaction identifier, all the first blocks may be determined from the block chain according to the transaction identifier in the transaction data acquisition request, and then the corresponding transaction service data is obtained from the determined first blocks.
At block 1030, the queried transaction service data is sent to the transaction dispute resolution party for the transaction dispute resolution party to use as evidence of transaction dispute resolution.
Fig. 11 shows a flowchart of an example of obtaining transaction data and electronic contracts from a blockchain according to an embodiment of the present specification. The example shown in fig. 11 may be performed by data acquisition node 240. In the example of fig. 11, the first chunk may include transaction traffic data, a contract identification, a transaction identification, and a first hash value, and the second chunk includes electronic contract data, a contract identification, and a second hash value.
As shown in FIG. 11, at block 1110, a transaction data acquisition request may be received from a transaction dispute resolution party, the transaction data acquisition request including a transaction identification and a contract identification.
At block 1120, the block chain is queried for transaction service data corresponding to the transaction identification and electronic contract data corresponding to the contract identification.
At block 1130, the queried transaction service data and electronic contract data are sent to the transaction dispute resolution party for the transaction dispute resolution party to serve as evidence of transaction dispute resolution.
Fig. 12 is a flowchart illustrating an example of verifying whether transaction service data is available based on a blockchain according to an embodiment of the present specification. The example shown in fig. 12 may be performed by data validation node 250. The data verification node 250 may be a block chain node belonging to an organization such as a financial supervision organization, a judicial appraisal center, and a notary office, or a block chain node communicatively connected to the organization such as the financial supervision organization, the judicial appraisal center, and the notary office. Data validation node 250 may validate whether transaction data provided by these institutions is available based on the blockchain.
In the example of fig. 12, the tiles on the blockchain may include a transaction identification and a corresponding first hash value. As shown in fig. 12, at block 1210, a dispute evidence data verification request may be received from a transaction dispute resolution party, where the dispute evidence data verification request includes a transaction identifier of a transaction to be resolved and transaction service data to be verified.
The transaction service data to be verified may be transaction service data acquired from a third-party transaction data storage party, where the third-party transaction data storage party may be a trusted third party or an untrusted third party.
At block 1220, a hash calculation is performed on the transaction data to be verified to obtain a third hash value of the transaction data to be verified.
At block 1230, the chain of blocks is queried for a first hash value corresponding to the transaction identification.
At block 1240, the third hash value is compared to the first hash value.
At block 1250, based on the comparison result of the third hash value and the first hash value, notification information indicating whether the transaction service data to be verified is available is sent to the transaction dispute resolution party.
In the transaction service data verification scheme shown in fig. 12, the transaction service data to be verified is stored in the third-party transaction data storage party, when the transaction dispute is resolved, the transaction service data may be obtained from the third-party transaction data storage party, and the hash value recorded on the blockchain is used to verify whether the obtained transaction service data is real, so that the transaction service data is effectively prevented from being tampered, and since the transaction service data is not stored on the blockchain, the storage space of the blockchain may be saved.
Fig. 13 shows a flowchart of an example of verifying whether transaction service data and an electronic contract are available based on a blockchain according to an embodiment of the present specification. The example shown in fig. 13 may be performed by data validation node 250.
In the example of fig. 13, the blockchain records a first block packed based on transaction service data of the transaction and a second block packed based on electronic contract data, the first block including transaction identification information and a first hash value, the first hash value being generated based on the transaction data of the transaction, the transaction data including complete transaction service data generated at each transaction service stage included in the transaction, the second block including a second hash value, the second hash value being generated based on the electronic contract data.
As shown in FIG. 13, at block 1310, a dispute evidence data validation request is received from a transaction dispute resolution party. The dispute evidence data verification request comprises transaction service data to be verified, a transaction identifier, electronic contract data to be verified and a contract identifier.
At block 1320, hash calculation is performed on the transaction data to be verified and the electronic contract data to be verified, respectively, to obtain a third hash value of the transaction data to be verified and a fourth hash value of the electronic contract data to be verified.
At block 1330, the blockchain is queried for a first hash value corresponding to the transaction identification and a second hash value corresponding to the contract identification.
At block 1340, the third hash value is compared to the first hash value and the fourth hash value is compared to the second hash value.
At block 1350, notification information indicating whether the transaction service data to be verified and the electronic contract to be verified are available is sent to the transaction dispute resolvers based on the comparison result of the third hash value and the first hash value and the comparison result of the fourth hash value and the second hash value.
Fig. 14 shows a block diagram of an example of a blockchain-based transaction data processing apparatus 1400 according to an embodiment of the present disclosure. As shown in fig. 14, the transaction data processing apparatus 1400 may include a transaction data acquisition unit 1410, a tile generation unit 1420, and a tile recording unit 1430.
The transaction data obtaining unit 1410 is configured to obtain transaction data of a transaction, which includes complete transaction service data generated at each transaction service stage included in the transaction. The operation of the transaction data acquisition unit 1410 may refer to the operation of block 310 described above with reference to fig. 3.
The block generation unit 1420 is configured to package the acquired transaction data into a first block that includes the transaction identification and a corresponding first hash value, the first hash value being generated based on the transaction data. The operation of the block generation unit 1420 may refer to the operation of the block 320 described above with reference to fig. 3.
The block recording unit 1430 is configured to record the first block on the block chain. The operation of the tile recording unit 1430 may refer to the operation of the block 330 described above with reference to fig. 3.
In one example, the tile recording unit 1430 may include a consensus processing module and a tile recording module. The block recording module is configured to record the first block on the block chain after the consensus node achieves the consensus.
In one example, the transaction has an electronic contract defining the responsibility of a party to the transaction, the electronic contract being packaged into a second chunk recorded on the blockchain, the second chunk including a contract identification and a corresponding second hash value, the first chunk including the contract identification of the electronic contract.
In one example, the transaction data processing apparatus 1400 may further include a signing data acquisition unit configured to acquire signing data generated in respective signing phases of a signing process of the electronic contract. In this example, the chunk generation unit 1420 is configured to package the obtained signed data and electronic contract data into the second chunk, which includes the contract identification, the signed data, and a corresponding second hash value. The block recording unit 1430 is configured to record the second block on the block chain.
In one example, the first block includes transaction data and/or the second block includes electronic contract data and signing data.
In one example, the transaction has an electronic contract for defining responsibility of a party to the transaction, the electronic contract being packaged into a second chunk recorded on the blockchain, the second chunk including a contract identification and a corresponding second hash value, the transaction corresponding with an index for recording a correspondence of the transaction identification with the contract identification of the electronic contract.
In one example, when the first tile includes transaction service data, the transaction data processing device 1400 may further include a data request receiving unit, a data querying unit, and a data transmitting unit. The data request receiving unit is configured to receive a transaction data obtaining request from a transaction dispute resolution party, the transaction data obtaining request comprises a transaction identifier, the data query unit is configured to query transaction service data corresponding to the transaction identifier from a block chain, and the data sending unit is configured to send the queried transaction service data to the transaction dispute resolution party so that the transaction dispute resolution party can serve as evidence of transaction dispute resolution.
In one example, when the first block includes transaction service data and the second block includes electronic contract data, the data request receiving unit may be further configured to receive a transaction data acquisition request from the transaction dispute resolution party, the transaction data acquisition request including the transaction identification and the contract identification. The data query unit may be further configured to query, from the blockchain, transaction service data corresponding to the transaction identifier and electronic contract data corresponding to the contract identifier. The data sending unit may be further configured to send the queried transaction service data and electronic contract data to the transaction dispute resolution party, so that the transaction dispute resolution party serves as evidence of transaction dispute resolution.
In one example, the transaction data processing device 1400 may further include a verification request receiving unit, a hash value processing unit, and a notification unit. The verification request receiving unit is configured to receive a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises a transaction identifier of a transaction to be resolved and transaction service data to be verified. The hash value processing unit is configured to perform hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified, query the first hash value corresponding to the transaction identifier on the block chain, and compare the third hash value with the first hash value. The notification unit is configured to send notification information indicating whether the transaction service data to be verified is available to the transaction dispute resolution party based on a comparison result of the third hash value and the first hash value.
In one example, the verification request receiving unit may be further configured to receive a dispute evidence data verification request from the transaction dispute resolution party, the dispute evidence data verification request including the transaction identification of the transaction to be resolved, the transaction business data to be verified, the contract identification of the electronic contract to be verified, and the electronic contract data of the electronic contract to be verified. The hash value processing unit may be further configured to perform hash calculation on the transaction data to be verified and the electronic contract data to be verified, respectively, to obtain a third hash value of the transaction data to be verified and a fourth hash value of the electronic contract data to be verified, query the block chain for the first hash value corresponding to the transaction identifier and the second hash value corresponding to the contract identifier, compare the third hash value with the first hash value, and compare the fourth hash value with the second hash value. The notification unit may be further configured to send notification information indicating whether the transaction service data to be verified and the electronic contract data to be verified are available to the transaction dispute resolution party based on a comparison result of the third hash value and the first hash value and a comparison result of the fourth hash value and the second hash value.
Fig. 15 shows a block diagram of an example of a transaction data processing device 1500 that obtains transaction data from a blockchain in an embodiment of the present description. As shown in fig. 15, the transaction data processing apparatus 1500 may include a data request receiving unit 1510, a data querying unit 1520, and a data transmitting unit 1530.
The data request receiving unit 1510 is configured to receive a transaction service data acquisition request from a transaction dispute resolution party, where the transaction data acquisition request includes a transaction identification. The operation of the data request receiving unit 1510 may refer to the operation of block 1010 described above with reference to fig. 10.
The data querying unit 1520 is configured to query transaction service data corresponding to the transaction identification from the blockchain. The operation of the data querying unit 1520 may refer to the operation of block 1020 described above with reference to FIG. 10.
The data sending unit 1530 is configured to send the queried transaction service data to the transaction dispute resolving party, so that the transaction dispute resolving party serves as an evidence for resolving the transaction dispute, where a blockchain records a first block formed by packaging transaction service data based on the transaction, the first block includes transaction identification information, the transaction data and a corresponding first hash value, and the transaction data includes complete transaction service data generated at each transaction service stage included in the transaction. The operation of the data transmission unit 1530 may refer to the operation of block 1030 described above with reference to fig. 10.
In one example, the blockchain records a second block packed based on the electronic contract data, the second block includes the contract identifier, the electronic contract data, and a corresponding second hash value, and the transaction data acquisition request further includes the contract identifier.
The data querying unit 1520 may be further configured to query, from the blockchain, transaction service data corresponding to the transaction identification and electronic contract data corresponding to the contract identification. In this example, the operation of the data querying unit 1520 may refer to the operation of block 1120 described above with reference to FIG. 11.
The data sending unit 1530 may also be configured to send the queried transaction service data and electronic contract data to the transaction dispute resolution party, so that the transaction dispute resolution party serves as evidence of transaction dispute resolution. In this example, the operation of the data transmission unit 1530 may refer to the operation of block 1130 described above with reference to fig. 11.
Fig. 16 is a block diagram illustrating an example of a transaction data processing device 1600 that verifies transaction data based on blockchain in accordance with an embodiment of the present disclosure. As shown in fig. 16, the transaction data processing device 1600 may include a verification request receiving unit 1610, a hash value processing unit 1620, and a notification unit 1630.
The verification request receiving unit 1610 is configured to receive a dispute evidence data verification request from a transaction dispute resolution party, where the dispute evidence data verification request includes transaction service data to be verified and a transaction identifier. The operation of the authentication request receiving unit 1610 may refer to the operation of block 1210 described above with reference to fig. 12.
The hash value processing unit 1620 is configured to perform hash calculation on the transaction data to be verified to obtain a third hash value of the transaction data to be verified, query the first hash value corresponding to the transaction identifier on the block chain, and compare the third hash value with the first hash value. The operations of the hash value processing unit 1620 may refer to the operations of blocks 1220, 1230, and 1240 described above with reference to fig. 12.
The notification unit 1630 is configured to send notification information indicating whether the transaction service data to be verified is available to the transaction dispute resolution party based on a comparison result of the third hash value and the first hash value, where a blockchain records a first block formed by packaging the transaction service data based on the transaction, the first block includes the transaction identification information and the first hash value, the first hash value is generated based on the transaction data of the transaction, and the transaction data includes complete transaction service data generated in each transaction service stage included in the transaction. The operation of the notification unit 1630 may refer to the operation of block 1250 described above with reference to FIG. 12.
In one example, the blockchain records a first block packed based on transaction service data of the transaction and a second block packed based on electronic contract data, the first block comprises transaction identification information and a first hash value, the first hash value is generated based on the transaction data of the transaction, the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction, the second block comprises a contract identification and a second hash value, and the second hash value is generated based on the electronic contract data.
The verification request receiving unit 1610 may be further configured to receive a dispute evidence data verification request from the transaction dispute resolution party, where the dispute evidence data verification request includes transaction service data to be verified, a transaction identifier, electronic contract data to be verified, and a contract identifier. In this example, the operation of the verification request receiving unit 1610 may refer to the operation of block 1310 described above with reference to fig. 13.
The hash value processing unit 1620 may be further configured to perform hash calculation on the transaction data to be verified and the electronic contract data to be verified, respectively, to obtain a third hash value of the transaction data to be verified and a fourth hash value of the electronic contract data to be verified, query the block chain for the first hash value corresponding to the transaction identifier and the second hash value corresponding to the contract identifier, compare the third hash value with the first hash value, and compare the fourth hash value with the second hash value. In this example, the operation of the hash value processing unit 1620 may refer to the operations of blocks 1320, 1330, and 1340 described above with reference to fig. 13.
The notification unit 1630 may be further configured to send notification information indicating whether the transaction service data to be verified and the electronic contract to be verified are available to the transaction dispute resolvers based on the comparison result of the third hash value and the first hash value and the comparison result of the fourth hash value and the second hash value. In this example, the operation of notification unit 1630 may refer to the operation of block 1350 described above with reference to fig. 13.
Embodiments of a method and an apparatus for processing transaction data based on a blockchain according to an embodiment of the present disclosure are described above with reference to fig. 1 to 16.
The blockchain-based transaction data processing apparatus according to the embodiments of the present disclosure may be implemented by hardware, or may be implemented by software, or a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the storage into the memory for operation through the processor of the device where the software implementation is located as a logical means. In the embodiments of the present specification, the blockchain-based transaction data processing apparatus may be implemented using, for example, an electronic device.
Fig. 17 illustrates a block diagram of an electronic device 1700 for recording transaction data in a blockchain in accordance with an embodiment of the present description.
As shown in fig. 17, the electronic device 1700 may include at least one processor 1710, storage (e.g., non-volatile storage) 1720, memory 1730, and a communication interface 1740, and the at least one processor 1710, storage 1720, memory 1730, and communication interface 1740 are connected together via a bus 1750. The at least one processor 1710 executes at least one computer-readable instruction (i.e., an element described above as being implemented in software) stored or encoded in memory.
In one embodiment, computer-executable instructions are stored in the memory that, when executed, cause the at least one processor 1710 to: acquiring transaction data of a transaction, wherein the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction; packaging the acquired transaction data into a first block, wherein the first block comprises a transaction identifier and a corresponding first hash value, and the first hash value is generated based on the transaction data; and recording the first block on the block chain.
It should be appreciated that the computer-executable instructions stored in the memory, when executed, cause the at least one processor 1710 to perform the various operations and functions described above in connection with fig. 1-16 in the various embodiments of the present description.
According to one embodiment, a program product, such as a machine-readable medium, is provided. A machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-16 in the various embodiments of the present specification.
Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
Fig. 18 shows a block diagram of an electronic device 1800 for obtaining transaction data from a blockchain in an embodiment of the present description.
As shown in fig. 18, the electronic device 1800 may include at least one processor 1810, storage (e.g., non-volatile storage) 1820, memory 1830, and a communications interface 1840, and the at least one processor 1810, storage 1820, memory 1830, and communications interface 1840 are connected together via a bus 1850. The at least one processor 1810 executes at least one computer-readable instruction (i.e., the elements described above as being implemented in software) stored or encoded in memory.
In one embodiment, computer-executable instructions are stored in the memory that, when executed, cause the at least one processor 1810 to: receiving a transaction service data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier; inquiring transaction service data corresponding to the transaction identification from the block chain; and sending the inquired transaction service data to a transaction dispute resolution party to be used as an evidence for resolving the transaction dispute by the transaction dispute resolution party, wherein the block chain records a first block formed by packaging transaction service data based on transactions, the first block comprises transaction identification information, transaction data and a corresponding first hash value, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transactions.
It should be appreciated that the computer-executable instructions stored in the memory, when executed, cause the at least one processor 1810 to perform the various operations and functions described above in connection with fig. 1-16 in the various embodiments of the present description.
According to one embodiment, a program product, such as a machine-readable medium, is provided. A machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-16 in the various embodiments of the present specification.
Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
Fig. 19 shows a block diagram of an electronic device 1900 for validating transaction data and electronic contracts based on blockchain in an embodiment of the present description.
As shown in fig. 19, electronic device 1900 may include at least one processor 1910, storage (e.g., non-volatile storage) 1920, memory 1930, and communication interface 1940, and the at least one processor 1910, storage 1920, memory 1930, and communication interface 1940 are connected together via a bus 1950. The at least one processor 1910 executes at least one computer-readable instruction (i.e., the elements described above as being implemented in software) stored or encoded in memory.
In one embodiment, computer-executable instructions are stored in the memory that, when executed, cause the at least one processor 1910 to: receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises transaction service data to be verified and a transaction identifier; performing hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified; inquiring a first hash value corresponding to the transaction identifier on the block chain; comparing the third hash value with the first hash value; and sending notification information for indicating whether the transaction service data to be verified is available to a transaction dispute resolution party based on a comparison result of the third hash value and the first hash value, wherein a first block formed by packaging the transaction service data based on the transaction is recorded in a block chain, the first block comprises transaction identification information and the first hash value, the first hash value is generated based on the transaction data of the transaction, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction.
It should be appreciated that the computer-executable instructions stored in the memory, when executed, cause the at least one processor 1910 to perform the various operations and functions described above in connection with fig. 1-16 in the various embodiments of the present description.
According to one embodiment, a program product, such as a machine-readable medium, is provided. A machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-16 in the various embodiments of the present specification.
Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
In this case, the program code itself read from the readable medium can realize the functions of any of the above-described embodiments, and thus the machine-readable code and the readable storage medium storing the machine-readable code constitute a part of the embodiments of the present specification.
Computer program code required for the operation of various portions of the present specification may be written in any one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C + +, C #, VB, NET, Python, and the like, a conventional programming language such as C, Visual Basic 2003, Perl, COBOL 2002, PHP, and ABAP, a dynamic programming language such as Python, Ruby, and Groovy, or other programming languages. The program code may execute on the user's computer, or on the user's computer as a stand-alone software package, or partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any network format, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or in a cloud computing environment, or as a service, such as a software as a service (SaaS).
Examples of the readable storage medium include floppy disks, hard disks, magneto-optical disks, optical disks (e.g., CD-ROMs, CD-R, CD-RWs, DVD-ROMs, DVD-RAMs, DVD-RWs), magnetic tapes, nonvolatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or from the cloud via a communications network.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Not all steps and elements in the above flows and system structure diagrams are necessary, and some steps or elements may be omitted according to actual needs. The execution order of the steps is not fixed, and can be determined as required. The apparatus structures described in the above embodiments may be physical structures or logical structures, that is, some units may be implemented by the same physical entity, or some units may be implemented by a plurality of physical entities, or some units may be implemented by some components in a plurality of independent devices.
The term "exemplary" used throughout this specification means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous" over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.
Although the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings, the embodiments of the present disclosure are not limited to the specific details of the embodiments, and various simple modifications may be made to the technical solutions of the embodiments of the present disclosure within the technical spirit of the embodiments of the present disclosure, and all of them fall within the scope of the embodiments of the present disclosure.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the description is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (34)

1. A transaction data processing method based on a blockchain comprises the following steps:
acquiring transaction data of a transaction, wherein the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction;
packaging the acquired transaction data into a first block, wherein the first block comprises a transaction identifier and a corresponding first hash value, and the first hash value is generated based on the transaction data; and
recording the first block on a block chain.
2. The transaction data processing method of claim 1, wherein recording the first block on a block chain comprises:
broadcasting the first block to a consensus node in a block chain network for consensus processing; and
after the consensus node achieves consensus, recording the first block on a block chain.
3. The transaction data processing method according to claim 1, wherein the transaction has an electronic contract defining the responsibility of a party to the transaction, the electronic contract being packaged into a second block recorded on a blockchain, the second block comprising a contract identification and a corresponding second hash value,
the first block includes a contract identification for the electronic contract.
4. The transaction data processing method of claim 3, wherein the electronic contract is packaged into the second blockrecord on the blockchain using the following process:
acquiring signing data generated in each signing phase of the signing process of the electronic contract;
packaging the obtained signing data and the electronic contract data into the second block, wherein the second block comprises the contract identifier, the signing data and a corresponding second hash value; and
recording the second block on the block chain.
5. The transaction data processing method according to claim 4, wherein the first block includes the transaction service data and/or the second block includes the electronic contract data and the signing data.
6. The transaction data processing method of claim 4, wherein the respective signing phases include identity authentication and contract signing.
7. The transaction data processing method of claim 6, wherein the respective signing business phases further comprise at least one of account creation, contract signing initiation, signing notification, contract viewing, willingness authentication, and electronic contract storage.
8. The transaction data processing method according to claim 1, wherein the transaction has an electronic contract defining the responsibility of a party to the transaction, the electronic contract being packaged into a second block recorded on a blockchain, the second block comprising a contract identification and a corresponding second hash value,
the transaction corresponds to an index, and the index is used for recording the corresponding relation between the transaction identification and the contract identification of the electronic contract.
9. The transaction data processing method of claim 1, wherein the first block includes transaction data, the transaction data processing method further comprising:
receiving a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier;
inquiring transaction service data corresponding to the transaction identification from the block chain; and
and sending the inquired transaction service data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
10. The transaction data processing method according to claim 3, wherein the first block includes transaction service data, the second block includes the electronic contract data, the transaction data processing method includes:
receiving a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier and a contract identifier;
inquiring transaction service data corresponding to the transaction identification and electronic contract data corresponding to the contract identification from the block chain; and
and sending the inquired transaction service data and the electronic contract data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
11. The transaction data processing method of claim 1, further comprising:
receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises a transaction identifier of a transaction to be resolved and transaction service data to be verified;
performing hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified;
querying a first hash value corresponding to the transaction identification on the blockchain;
comparing the third hash value to the first hash value; and
and sending notification information used for indicating whether the transaction service data to be verified is available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value.
12. The transaction data processing method of claim 3, further comprising:
receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises a transaction identifier of a transaction to be resolved, transaction service data to be verified, a contract identifier of an electronic contract to be verified and electronic contract data of the electronic contract to be verified;
performing hash calculation on the transaction service data to be verified and the electronic contract data to be verified respectively to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified;
querying a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier on the blockchain;
comparing the third hash value to the first hash value, and comparing the fourth hash value to the second hash value; and
and sending notification information for indicating whether the transaction service data to be verified and the electronic contract data to be verified are available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value and the comparison result of the fourth hash value and the second hash value.
13. A transaction data processing method based on a blockchain comprises the following steps:
receiving a transaction service data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier;
inquiring transaction service data corresponding to the transaction identification from the block chain; and
sending the inquired transaction service data to the transaction dispute resolution party for the transaction dispute resolution party to serve as evidence for resolving the transaction dispute,
the block chain records a first block formed by packaging transaction service data based on transactions, the first block comprises transaction identification information, transaction data and a corresponding first hash value, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transactions.
14. The transaction data processing method according to claim 13, wherein the blockchain records a second chunk packed based on the electronic contract data, the second chunk including a contract identification, the electronic contract data, and a corresponding second hash value, the transaction data acquisition request further including the contract identification,
inquiring transaction service data corresponding to the transaction identification from the block chain comprises the following steps:
and inquiring transaction service data corresponding to the transaction identification and electronic contract data corresponding to the contract identification from the block chain.
15. A transaction data processing method based on a blockchain comprises the following steps:
receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises transaction service data to be verified and a transaction identifier;
performing hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified;
querying a first hash value corresponding to the transaction identifier on a blockchain;
comparing the third hash value to the first hash value; and
sending notification information indicating whether the transaction service data to be verified is available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value,
the block chain records a first block formed by packaging transaction service data based on transactions, the first block comprises transaction identification information and a first hash value, the first hash value is generated based on the transaction data of the transactions, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transactions.
16. A transaction data processing method based on a blockchain comprises the following steps:
receiving a dispute evidence data verification request from a transaction dispute resolution party, wherein the dispute evidence data verification request comprises transaction service data to be verified, a transaction identifier, electronic contract data to be verified and a contract identifier;
performing hash calculation on the transaction service data to be verified and the electronic contract data to be verified respectively to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified;
querying a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier on a blockchain;
comparing the third hash value to the first hash value and the fourth hash value to the second hash value; and
sending notification information indicating whether the transaction service data to be verified and the electronic contract to be verified are available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value and the comparison result of the fourth hash value and the second hash value,
wherein the blockchain records a first block formed by packaging transaction service data based on transaction and a second block formed by packaging transaction service data based on electronic contract data,
the first block includes transaction identification information and a first hash value, the first hash value being generated based on transaction data of a transaction, the transaction data including complete transaction service data generated at each transaction service stage included in the transaction,
the second chunk includes a contract identification and a second hash value, the second hash value generated based on the electronic contract data.
17. A blockchain-based transaction data processing apparatus comprising:
the transaction data acquisition unit is used for acquiring transaction data of a transaction, wherein the transaction data comprises complete transaction service data generated in each transaction service stage included in the transaction;
the block generation unit is used for packaging the acquired transaction data into a first block, wherein the first block comprises a transaction identifier and a corresponding first hash value, and the first hash value is generated based on the transaction data; and
and the block recording unit is used for recording the first block on a block chain.
18. The transaction data processing device of claim 17, wherein the tile recording unit comprises:
the consensus processing module broadcasts the first block to a consensus node in a block chain network to perform consensus processing; and
and the block recording module records the first block on a block chain after the consensus node achieves consensus.
19. The transaction data processing apparatus according to claim 17, wherein the transaction has an electronic contract defining the responsibility of a party to the transaction, the electronic contract being packaged into a second block recorded on a blockchain, the second block comprising a contract identification and a corresponding second hash value,
the first block includes a contract identification for the electronic contract.
20. The transaction data processing device of claim 19, further comprising:
a signing data acquisition unit that acquires signing data generated in each signing phase of a signing process of the electronic contract;
the block generation unit is used for packaging the acquired signing data and the electronic contract data into the second block, and the second block comprises the contract identification, the signing data and a corresponding second hash value; and
the block recording unit records the second block on the block chain.
21. The transaction data processing apparatus according to claim 20, wherein the first block includes the transaction data and/or the second block includes the electronic contract data and the signing data.
22. The transaction data processing apparatus according to claim 17, wherein the transaction has an electronic contract defining the responsibility of a party to the transaction, the electronic contract being packaged into a second block recorded on a blockchain, the second block comprising a contract identification and a corresponding second hash value,
the transaction corresponds to an index, and the index is used for recording the corresponding relation between the transaction identification and the contract identification of the electronic contract.
23. The transaction data processing device of claim 17, wherein the first block includes transaction data, the transaction data processing device further comprising:
the data request receiving unit is used for receiving a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier;
the data query unit is used for querying the transaction service data corresponding to the transaction identification from the block chain; and
and the data sending unit is used for sending the inquired transaction service data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
24. The transaction data processing device of claim 19, wherein the first block includes transaction data and the second block includes the electronic contract data, the transaction data processing device further comprising:
the data request receiving unit is used for receiving a transaction data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier and a contract identifier;
the data query unit is used for querying the transaction service data corresponding to the transaction identifier and the electronic contract data corresponding to the contract identifier from the block chain; and
and the data sending unit is used for sending the inquired transaction service data and the electronic contract data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
25. The transaction data processing device of claim 17, further comprising:
the dispute evidence data verification request comprises a transaction identifier of a transaction to be solved and transaction service data to be verified;
the hash value processing unit is used for carrying out hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified, inquiring a first hash value corresponding to the transaction identifier on the block chain, and comparing the third hash value with the first hash value; and
and the notification unit is used for sending notification information used for indicating whether the transaction business data to be verified is available to the transaction dispute resolution party based on the comparison result of the third hash value and the first hash value.
26. The transaction data processing device of claim 19, further comprising:
the dispute evidence data verification request comprises a transaction identifier of a transaction to be solved, transaction service data to be verified, a contract identifier of an electronic contract to be verified and electronic contract data of the electronic contract to be verified;
a hash value processing unit, configured to perform hash calculation on the transaction service data to be verified and the electronic contract data to be verified, respectively, to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified, query the block chain for a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier, compare the third hash value with the first hash value, and compare the fourth hash value with the second hash value; and
and a notification unit, configured to send notification information indicating whether the transaction service data to be verified and the electronic contract data to be verified are available to the transaction dispute resolution party based on a comparison result between the third hash value and the first hash value and a comparison result between the fourth hash value and the second hash value.
27. A blockchain-based transaction data processing apparatus comprising:
the data request receiving unit is used for receiving a transaction service data acquisition request from a transaction dispute resolution party, wherein the transaction data acquisition request comprises a transaction identifier;
the data query unit is used for querying the transaction service data corresponding to the transaction identification from the block chain; and
the data sending unit is used for sending the inquired transaction service data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for resolving the transaction dispute,
the block chain records a first block formed by packaging transaction service data based on transactions, the first block comprises transaction identification information, transaction data and a corresponding first hash value, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transactions.
28. The transaction data processing device of claim 27, wherein the blockchain records a second chunk packaged based on the electronic contract data, the second chunk including a contract identification, the electronic contract data, and a corresponding second hash value, the transaction data acquisition request further including a contract identification,
the data query unit is used for querying transaction service data corresponding to the transaction identifier and electronic contract data corresponding to the contract identifier from a block chain;
and the data sending unit is used for sending the inquired transaction service data and the electronic contract data to the transaction dispute resolution party so that the transaction dispute resolution party can be used as evidence for transaction dispute resolution.
29. A blockchain-based transaction data processing apparatus comprising:
the dispute evidence data verification request comprises transaction service data to be verified and a transaction identifier;
the hash value processing unit is used for carrying out hash calculation on the transaction service data to be verified to obtain a third hash value of the transaction service data to be verified, inquiring a first hash value corresponding to the transaction identifier on a block chain, and comparing the third hash value with the first hash value; and
a notification unit, configured to send notification information indicating whether the transaction service data to be verified is available to the transaction dispute resolution party based on a comparison result of the third hash value and the first hash value,
the block chain records a first block formed by packaging transaction service data based on transactions, the first block comprises transaction identification information and a first hash value, the first hash value is generated based on the transaction data of the transactions, and the transaction data comprises complete transaction service data generated in each transaction service stage included in the transactions.
30. A blockchain-based transaction data processing apparatus comprising:
the dispute evidence data verification request comprises transaction service data to be verified, a transaction identifier, electronic contract data to be verified and a contract identifier;
the hash value processing unit is used for respectively carrying out hash calculation on the transaction service data to be verified and the electronic contract data to be verified so as to obtain a third hash value of the transaction service data to be verified and a fourth hash value of the electronic contract data to be verified, inquiring a first hash value corresponding to the transaction identifier and a second hash value corresponding to the contract identifier on a block chain, comparing the third hash value with the first hash value and comparing the fourth hash value with the second hash value; and
a notification unit that sends notification information indicating whether the transaction service data to be verified and the electronic contract to be verified are available to the transaction dispute resolvers based on a comparison result of the third hash value and the first hash value and a comparison result of the fourth hash value and the second hash value,
wherein the blockchain records a first block formed by packaging transaction service data based on transaction and a second block formed by packaging transaction service data based on electronic contract data,
the first block includes transaction identification information and a first hash value, the first hash value being generated based on transaction data of a transaction, the transaction data including complete transaction service data generated at each transaction service stage included in the transaction,
the second chunk includes a contract identification and a second hash value, the second hash value generated based on the electronic contract data.
31. An electronic device, comprising:
at least one processor, and
a memory coupled with the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method of any of claims 1-12.
32. A machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the method of any one of claims 1 to 12.
33. An electronic device, comprising:
at least one processor, and
a memory coupled with the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method of any of claims 13-16.
34. A machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the method of any of claims 13 to 16.
CN202010330348.2A 2020-04-24 2020-04-24 Transaction data processing method and device based on block chain Pending CN111353893A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010330348.2A CN111353893A (en) 2020-04-24 2020-04-24 Transaction data processing method and device based on block chain

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010330348.2A CN111353893A (en) 2020-04-24 2020-04-24 Transaction data processing method and device based on block chain

Publications (1)

Publication Number Publication Date
CN111353893A true CN111353893A (en) 2020-06-30

Family

ID=71197768

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010330348.2A Pending CN111353893A (en) 2020-04-24 2020-04-24 Transaction data processing method and device based on block chain

Country Status (1)

Country Link
CN (1) CN111353893A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113094209A (en) * 2021-04-08 2021-07-09 中国工商银行股份有限公司 Block chain-based backup record data processing method, device, medium and product
CN113763185A (en) * 2021-09-10 2021-12-07 支付宝(杭州)信息技术有限公司 Data processing method and device for cash investment based on block chain
CN113961905A (en) * 2021-12-20 2022-01-21 四川特号商盟科技有限公司 Storage method of on-line agreement signing data
CN113965336A (en) * 2020-07-03 2022-01-21 航天信息股份有限公司 Data processing method and device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180113752A1 (en) * 2016-10-20 2018-04-26 International Business Machines Corporation Inter-ledger messaging in a blockchain
CN110287732A (en) * 2019-05-15 2019-09-27 杭州趣链科技有限公司 One kind depositing card method based on block chain electronic contract
CN110930151A (en) * 2019-11-29 2020-03-27 中国工商银行股份有限公司 Transaction processing method and device based on block chain, computing equipment and medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180113752A1 (en) * 2016-10-20 2018-04-26 International Business Machines Corporation Inter-ledger messaging in a blockchain
CN110287732A (en) * 2019-05-15 2019-09-27 杭州趣链科技有限公司 One kind depositing card method based on block chain electronic contract
CN110930151A (en) * 2019-11-29 2020-03-27 中国工商银行股份有限公司 Transaction processing method and device based on block chain, computing equipment and medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
冒小乐: "基于区块链技术的电子数据存证系统", 《万方学位论文》 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113965336A (en) * 2020-07-03 2022-01-21 航天信息股份有限公司 Data processing method and device
CN113094209A (en) * 2021-04-08 2021-07-09 中国工商银行股份有限公司 Block chain-based backup record data processing method, device, medium and product
CN113763185A (en) * 2021-09-10 2021-12-07 支付宝(杭州)信息技术有限公司 Data processing method and device for cash investment based on block chain
CN113961905A (en) * 2021-12-20 2022-01-21 四川特号商盟科技有限公司 Storage method of on-line agreement signing data
CN113961905B (en) * 2021-12-20 2022-03-11 四川特号商盟科技有限公司 Storage method of on-line agreement signing data

Similar Documents

Publication Publication Date Title
US12079200B2 (en) Method and system for audit and payment clearing of electronic trading systems using blockchain database
US11004067B2 (en) Methods and devices for protecting sensitive data of transaction activity based on smart contract in blockchain
CN112651740B (en) Block chain transaction method and device and electronic equipment
CN107038578B (en) Multi-signature transaction information processing method in data transaction platform based on block chain
US11232415B2 (en) Method for cryptographically managing title transactions
US11599858B2 (en) Blockchain settlement network
US20150356523A1 (en) Decentralized identity verification systems and methods
CN113728351A (en) Trusted certification transactions in blockchain systems
CN111353893A (en) Transaction data processing method and device based on block chain
CN111461622B (en) Block chain-based warehouse credit rating, result acquisition and verification method and device
CN111160998B (en) Comment data processing method and device based on block chain and comment system
JPH09507729A (en) Cryptographic system and method with key escrow function
WO2022109851A1 (en) Blockchain-based trusted platform
CN112435026B (en) Method and device for protecting file transaction information by using zero-knowledge proof and electronic equipment
WO2022109840A1 (en) Blockchain-based trusted platform
CN112801778A (en) Federated bad asset blockchain
CN111160997A (en) Advertisement supervision method and device based on block chain and advertisement delivery system
CN115456613A (en) Digital collection transaction method and equipment
CN112507369A (en) Service processing method and device based on block chain, readable medium and electronic equipment
CN115130147A (en) Copyright declaration method and copyright declaration device based on block chain
WO2022109850A1 (en) Blockchain-based trusted platform
WO2022109848A1 (en) Blockchain-based trusted platform
JP2018022346A (en) Data transaction system and program
CN114896616B (en) Policy processing method and system based on block chain
CN115099800A (en) Block chain based method and device for transferring poor asset data

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
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40030936

Country of ref document: HK

RJ01 Rejection of invention patent application after publication

Application publication date: 20200630

RJ01 Rejection of invention patent application after publication