CN112488680B - Private transaction processing method and device based on blockchain - Google Patents

Private transaction processing method and device based on blockchain Download PDF

Info

Publication number
CN112488680B
CN112488680B CN202011412394.3A CN202011412394A CN112488680B CN 112488680 B CN112488680 B CN 112488680B CN 202011412394 A CN202011412394 A CN 202011412394A CN 112488680 B CN112488680 B CN 112488680B
Authority
CN
China
Prior art keywords
transaction
private
visible
data
parties
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.)
Active
Application number
CN202011412394.3A
Other languages
Chinese (zh)
Other versions
CN112488680A (en
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.)
WeBank Co Ltd
Original Assignee
WeBank 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 WeBank Co Ltd filed Critical WeBank Co Ltd
Priority to CN202011412394.3A priority Critical patent/CN112488680B/en
Publication of CN112488680A publication Critical patent/CN112488680A/en
Application granted granted Critical
Publication of CN112488680B publication Critical patent/CN112488680B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • 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/23—Updating
    • G06F16/2365—Ensuring data consistency and integrity
    • 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
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • 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

Abstract

The invention discloses a private transaction processing method and device based on a blockchain, wherein the method comprises the steps that a transaction initiating party sends inquiry information to a plurality of transaction visible parties of private transaction in the blockchain, after receiving execution confirmation information returned by the transaction visible parties, the private transaction is executed to obtain an execution result, the private transaction and the execution result are broadcast to the transaction visible parties, after receiving execution success information returned by the transaction visible parties in preset time, data related to executing the private transaction are stored in a private database, verification data of the private transaction are determined, the verification data of the private transaction are stored in the blockchain, and data storage notification is broadcast to the transaction visible parties. By executing the private transaction locally, storing the data related to executing the private transaction in the private database and sending the verification data of the private transaction to the blockchain storage, compared with the existing scheme, the method has the advantages that the low resource occupancy rate can be realized, and the blockchain processing complexity is not increased.

Description

Private transaction processing method and device based on blockchain
Technical Field
The invention relates to the technical field of financial science (Fintech), in particular to an anti-bifurcation detection method and device of a Block Chain (Block Chain).
Background
With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changed into financial technology, but due to the requirements of safety and instantaneity of the financial industry, the technology is also required to be higher. Private transaction processing is an important research problem in blockchain technology in the financial arts.
There are two types of schemes for implementing private transactions at present: the first is to identify the private transaction and then process the private transaction separately in the transaction processing process; one type is to implement private transactions between specific nodes through a multi-group scheme. However, the first class of processing method can increase the processing complexity for the blockchain, and for the second class of processing method, the created group can have the problem of long-term occupation of resources, thus causing resource waste.
Disclosure of Invention
The embodiment of the invention provides a private transaction processing method and device based on a blockchain, which can realize low resource occupancy rate without increasing the processing complexity of the blockchain compared with the prior art.
In a first aspect, an embodiment of the present invention provides a private transaction processing method based on blockchain, including:
the method comprises the steps that a transaction initiating party sends inquiry information to a plurality of transaction visible parties of private transactions in a blockchain, so that the plurality of transaction visible parties can confirm whether the private transactions can be executed or not;
After receiving the execution confirmation information returned by the transaction visible parties, the transaction initiator executes the private transaction to obtain an execution result;
the transaction initiating party broadcasts the private transaction and the execution result to the transaction visible parties so that the transaction visible parties execute the private transaction and compare the execution result;
after receiving the execution success information returned by the transaction visible parties within a preset time, the transaction initiator stores data related to executing the private transaction into a private database, determines verification data of the private transaction, and stores the verification data of the private transaction into the blockchain;
the transaction initiation broadcasts a data storage notification to the plurality of transaction-visible parties to cause the plurality of transaction-visible parties to store data related to executing the private transaction to their own private databases.
According to the technical scheme, the private transaction is executed locally, the data related to executing the private transaction is stored in the private database, and the verification data of the private transaction is sent to the blockchain storage.
Optionally, the executing the private transaction by the transaction initiator, to obtain an execution result, includes:
and the transaction initiator locks the account resource related to the private transaction, locally executes the private transaction based on the current data state of the account related to the private transaction, obtains the data state after the execution of the private transaction, and stores the data state in a local cache.
Optionally, the transaction initiator stores data related to executing the private transaction in a private database, and determines verification data of the private transaction, including:
the transaction initiator stores the data related to executing the private transaction in a local cache into a local private database;
the transaction initiator determines a hash value of the private transaction; determining a hash value of a root node of a merck tree of the private transaction according to data related to executing the private transaction; determining a verification path of the merck tree corresponding to unmodified data according to the unmodified data in the data related to executing the private transaction;
the transaction initiator determines the hash value of the private transaction, the hash value of the root node of the merck tree of the private transaction, the verification path of the merck tree corresponding to the unmodified data and the identification information of the transaction visible party of the private transaction as the verification data of the private transaction.
Optionally, the method further comprises:
and if the transaction initiator does not receive the execution success information returned by all the transaction visible parties within the preset time, sending a notification for ending the transaction to the transaction visible parties so that the transaction visible parties end executing the transaction and release the locked account resources.
In a second aspect, an embodiment of the present invention provides a private transaction processing method based on blockchain, including:
the method comprises the steps that a transaction visible party obtains private transaction broadcast by a transaction initiator in a blockchain and an execution result of the transaction initiator;
the transaction visible party locally executes the private transaction to obtain an execution result, compares the execution result with the execution result of the transaction initiator, and sends information about whether the execution is successful or not to the transaction initiator;
and after receiving the data storage notification sent by the transaction initiator, the transaction visible party stores the data related to executing the private transaction into a private database.
Optionally, the transaction visible party locally executes the private transaction to obtain an execution result, compares the execution result with the execution result of the transaction initiator, and sends the transaction initiator whether to execute the successful information, including:
The transaction visible party locks account resources related to the private transaction, executes the private transaction locally based on the current data state of the account related to the private transaction, obtains the data state after the private transaction is executed, and stores the data state in a local cache;
the transaction visible party compares whether the execution result of the transaction initiator is consistent with the data state after the private transaction is executed, if so, the transaction visible party determines that the execution is successful and sends execution success information to the transaction initiator; otherwise, determining that the execution fails, and sending execution failure information to the transaction initiator.
Optionally, the transaction visible party stores data related to executing the private transaction in a private database, and determines verification data of the private transaction, including:
the transaction facilitator stores the data in the local cache that is involved in executing the private transaction into a local private database.
Optionally, the method further comprises:
when confirming that the transaction initiator is in a downtime state, the transaction visible party sends a query to a first transaction visible party in the blockchain, and if the first transaction visible party is confirmed to submit data in a local cache, the same operation as the first transaction visible party is executed; the first transaction visible party is any one of the other transaction visible parties in the blockchain;
The transaction initiator terminating the transaction if the transaction visible party determines that the first transaction visible party does not execute the private transaction;
and if the transaction visible party determines that the first transaction visible party executes and completes the private transaction, the transaction visible party continuously inquires other transaction visible parties except the first transaction visible party in the blockchain until the fact that all transaction visible parties in the blockchain execute the private transaction is confirmed, and then a system blocking notification is sent to staff.
Optionally, the method further comprises:
after restarting or periodically monitoring verification data on the blockchain by the transaction visible party, if determining that missing data exists, acquiring the verification data from other visible parties on the blockchain;
the transaction visible party verifies the correctness and the integrity of the private transaction according to the hash value of the private transaction in the verification data, and executes the private transaction after the verification is passed, so that an execution result is obtained;
the transaction visible party determines a hash value of a root node of the merck tree of the private transaction based on the execution result and a verification path of the merck tree of unmodified data in the verification data;
The transaction visible party stores the data related to executing the private transaction into a local private database when determining that the hash value of the root node of the merck tree of the private transaction is consistent with the hash value of the root node of the merck tree in the verification data.
In a third aspect, an embodiment of the present invention provides a private transaction processing apparatus based on blockchain, including:
a transmitting unit configured to transmit query information to a plurality of transaction visible parties of a private transaction in a blockchain, so that the plurality of transaction visible parties confirm whether the private transaction can be executed;
the processing unit is used for executing the private transaction after receiving the execution confirmation information returned by the transaction visible parties to obtain an execution result;
the sending unit is further configured to broadcast the private transaction and the execution result to the transaction visible parties, so that the transaction visible parties execute the private transaction and compare the execution results;
the processing unit is further configured to store data related to executing the private transaction into a private database after receiving execution success information returned by the plurality of transaction visible parties within a preset time, determine verification data of the private transaction, and store the verification data of the private transaction into the blockchain;
The sending unit is further configured to broadcast a data storage notification to the transaction visible parties, so that the transaction visible parties store relevant data of the private transaction in their own private databases.
Optionally, the processing unit is specifically configured to:
and locking account resources related to the private transaction, locally executing the private transaction based on the current data state of the account related to the private transaction, obtaining the data state of the private transaction after execution, and storing the data state in a local cache.
Optionally, the processing unit is specifically configured to:
storing data related to executing the private transaction in a local cache into a local private database;
determining a hash value of the private transaction; determining a hash value of a root node of a merck tree of the private transaction according to data related to executing the private transaction; determining a verification path of the merck tree corresponding to unmodified data according to the unmodified data in the data related to executing the private transaction;
and determining the hash value of the private transaction, the hash value of the root node of the merck tree of the private transaction, the verification path of the merck tree corresponding to the unmodified data and the identification information of the transaction visible party of the private transaction as verification data of the private transaction.
Optionally, the processing unit is further configured to:
and if the execution success information returned by all the transaction visible parties is not received within the preset time, sending a notification for ending the transaction to the transaction visible parties so that the transaction visible parties end the execution of the transaction and release the locked account resources.
In a fourth aspect, an embodiment of the present invention provides a private transaction processing apparatus based on blockchain, including:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is specifically used for acquiring private transactions broadcasted by a transaction initiator in a blockchain and execution results of the transaction initiator;
the processing unit is specifically used for locally executing the private transaction to obtain an execution result, comparing the execution result with the execution result of the transaction initiator, and sending information whether the execution is successful or not to the transaction initiator; and after receiving the data storage notification sent by the transaction initiator, storing the data related to executing the private transaction into a private database.
Optionally, the processing unit is specifically configured to:
locking account resources related to the private transaction, locally executing the private transaction based on the current data state of the account related to the private transaction, obtaining the data state of the private transaction after execution, and storing the data state in a local cache;
Comparing whether the execution result of the transaction initiator is consistent with the data state after the private transaction is executed, if so, determining that the execution is successful, and sending execution success information to the transaction initiator; otherwise, determining that the execution fails, and sending execution failure information to the transaction initiator.
Optionally, the processing unit is specifically configured to:
storing data related to executing the private transaction in the local cache in a local private database.
Optionally, the processing unit is further configured to:
when the transaction initiator is confirmed to be in a downtime state, sending a query to a first transaction visible party in the blockchain, and if the first transaction visible party is confirmed to submit data in a local cache, executing the same operation as the first transaction visible party; the first transaction visible party is any one of the other transaction visible parties in the blockchain;
if it is determined that the first transaction visible party does not perform the private transaction, the transaction initiator has terminated the transaction;
if the first transaction visible party is confirmed to execute and complete the private transaction, the other transaction visible parties except the first transaction visible party in the blockchain are continuously inquired until all the transaction visible parties in the blockchain are confirmed to execute and complete the private transaction, and then a system blocking notification is sent to staff.
Optionally, the processing unit is further configured to:
after restarting or periodically monitoring verification data on the blockchain, if determining that missing data exists, acquiring the verification data from other visible parties on the blockchain;
verifying the correctness and the integrity of the private transaction according to the hash value of the private transaction in the verification data, and executing the private transaction after the verification is passed, so as to obtain an execution result;
determining a hash value of a root node of the merck tree of the private transaction based on the execution result and a verification path of the merck tree of unmodified data in the verification data;
and when the hash value of the root node of the merck tree of the private transaction is consistent with the hash value of the root node of the merck tree in the verification data, storing the data related to executing the private transaction into a local private database.
In a fifth aspect, embodiments of the present invention further provide a computing device, including:
a memory for storing program instructions;
and the processor is used for calling the program instructions stored in the memory and executing the private transaction processing method based on the blockchain according to the obtained program.
In a sixth aspect, embodiments of the present invention further provide a computer-readable nonvolatile storage medium, including computer-readable instructions, which when read and executed by a computer, cause the computer to perform the private transaction processing method based on blockchain as described above.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of a private transaction processing method based on blockchain according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a private transaction processing system according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a private transaction processing device based on blockchain according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a private transaction processing device based on blockchain according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail below with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Fig. 1 is a system architecture according to an embodiment of the present invention. As shown in fig. 1, the system architecture may include a blockchain 100 and a plurality of user clients 200;
wherein, a plurality of user clients 200 can be clients used by different institutions, and part of the user clients 200 are provided with a local private database for processing private transactions locally.
The blockchain 100 includes a plurality of blockchain nodes that are composed of a plurality of blocks for storing authentication data transmitted by the user client 200.
It should be noted that the structure shown in fig. 1 is merely an example, and the embodiment of the present invention is not limited thereto.
Based on the above description, fig. 2 shows in detail a flow of a private transaction processing method based on a blockchain, which may be executed by a private transaction processing device based on a blockchain according to an embodiment of the present invention. The flow of this private transaction process will be described below in terms of transaction initiator interactions with transaction visualizers.
As shown in fig. 2, the process specifically includes:
in step 201, the transaction initiator sends query information.
In the embodiment of the invention, when the transaction initiator needs to process the private transaction, inquiry information can be sent to a plurality of transaction visible parties of the private transaction in the blockchain so that the plurality of transaction visible parties can confirm whether the private transaction can be executed or not.
At step 202, the transaction facilitator sends a confirmation of execution.
After receiving the inquiry information of the transaction initiator, the transaction visible party can determine whether the private transaction can be executed according to the situation of the transaction visible party, if so, the transaction visible party returns execution confirmation information, and if not, the transaction visible party returns execution negative information.
In step 203, the transaction initiator executes the private transaction to obtain an execution result.
After the transaction initiator receives the execution confirmation information returned by all the transaction visible parties, the private transaction can be executed, specifically, the transaction initiator locks account resources related to the private transaction, executes the private transaction locally based on the current data state of the account related to the private transaction, obtains the data state after the private transaction is executed, and stores the data state in a local cache.
In step 204, the transaction initiator broadcasts the private transaction and the execution result.
When the private transaction is executed by the transaction initiator, the private transaction and the execution result can be broadcast to a plurality of transaction visible parties in the blockchain, so that the plurality of transaction visible parties execute the private transaction and compare the execution results.
In step 205, the transaction visible party executes the private transaction to obtain an execution result.
After the transaction visible party obtains the private transaction and the execution result broadcasted by the transaction initiator, the private transaction can be locally executed, specifically, the transaction visible party locks the account resource related to the private transaction, the private transaction is locally executed based on the current data state of the account related to the private transaction, the data state after the private transaction is executed is obtained, and the data state is stored in the local cache. The transaction visible party compares whether the execution result of the transaction initiator is consistent with the data state after the private transaction is executed, and if so, the transaction visible party determines that the execution is successful; otherwise, determining that the execution fails.
At step 206, the transaction visible party sends execution success information.
In step 205, if the transaction visible party determines that the execution was successful, an execution success message is sent to the transaction initiator. And if the transaction visible party determines that the execution fails, sending the execution failure information to the transaction initiator.
In step 207, the transaction initiator stores the data involved in executing the private transaction in the private database, determines the verification data of the private transaction, and stores the verification data of the private transaction in the blockchain.
After the private transaction is executed in step 203, the transaction initiator starts a timer, sets a preset time, and after receiving the execution success information sent by all the visible transaction parties in the preset time, the transaction initiator can perform the operation of submitting data, specifically, the transaction initiator can store the data related to executing the private transaction in the local cache into the local private database. Determining a hash value of the private transaction; determining a hash value of a root node of a merck tree of a private transaction according to data related to executing the private transaction; and determining a verification path of the merck tree corresponding to the unmodified data according to the unmodified data in the data involved in executing the private transaction. And finally, determining the hash value of the private transaction, the hash value of the root node of the merck tree of the private transaction, the verification path of the merck tree corresponding to the unmodified data and the identification information of the transaction visible party of the private transaction as the verification data of the private transaction.
After the verification data is obtained, the verification data can be subjected to a chaining operation. Any node in the blockchain can see the validation data. The verification data may ensure the integrity of the private transaction.
Optionally, if the execution success information returned by all the transaction visible parties is not received within the preset time, the transaction initiator can send a notification of ending the transaction to the transaction visible parties, so that the transaction visible parties end the execution of the transaction, and the locked account resources are released.
The transaction viewers may discard the cached data upon receiving notification to terminate the transaction and release the locked account resources after the operation is completed.
At step 208, the transaction initiator broadcasts a data store notification.
After the transaction initiator submits the data, a data storage notification may be broadcast to the plurality of transaction sees in the blockchain to cause the plurality of transaction sees to store data related to performing the private transaction in their own private database and to store verification data for the private transaction in the blockchain.
In step 209, the transaction facilitator stores the data related to executing the private transaction in the private database, determines the verification data of the private transaction, and stores the verification data of the private transaction in the blockchain.
After receiving the data storage notification broadcast by the transaction initiator, the transaction visible party can conduct data submitting operation, and specifically, the transaction visible party stores data related to executing private transaction in the local cache into the local private database.
It should be noted that, the embodiment of the present invention is further provided with an abnormal situation handling mechanism, specifically, when confirming that the transaction initiator is in a downtime state, the first transaction visible party in the transaction visible direction blockchain sends a query, and performs the following processes:
first kind:
the transaction party performs the same operation as the first transaction party if it is determined that the first transaction party has submitted data in the local cache. The first transaction visible party is any one of the other transaction visible parties in the blockchain.
Second kind:
the transaction initiator has terminated the transaction if the transaction facilitator determines that the first transaction facilitator did not perform the private transaction.
Third kind:
if the transaction visible party determines that the first transaction visible party executes the private transaction, the transaction visible party continuously inquires other transaction visible parties except the first transaction visible party in the blockchain until all transaction visible parties in the blockchain are confirmed to execute the private transaction, and then a system blocking notification is sent to staff.
In addition, the problem of inconsistent data can be solved, specifically, after restarting or periodically monitoring verification data on the blockchain by the transaction visible party, if the missing data is determined to exist, the verification data is acquired from other visible parties on the blockchain. And then verifying the correctness and the integrity of the private transaction according to the hash value of the private transaction in the verification data, and executing the private transaction after the verification is passed, so as to obtain an execution result. Based on the execution result and the verification path of the merck tree of unmodified data in the verification data, a hash value of a root node of the merck tree of the private transaction is determined. And finally, when the hash value of the root node of the merck tree of the private transaction is consistent with the hash value of the root node of the merck tree in the verification data, storing the data related to executing the private transaction into a local private database, and storing the verification data into a blockchain.
In order to better explain the embodiment of the present invention, the process of the private transaction processing will be described below in a specific implementation scenario.
The private transaction processing system provided by the embodiment of the invention consists of user service and blockchain node service. Each user service is respectively provided with one or more block chain nodes to form a block chain network, and the nodes interact with the block chain to realize the writing and reading of data on the chain. The subsequent example assumes that four users (labeled 1234) have correspondingly deployed node ABCD component blockchains. The specific architecture may be as shown in fig. 3.
The user's data store has two locations, a public database and a private database, respectively.
Wherein the public database is a blockchain network, i.e., the public database of each user is consistent and visible to other users. Each user can interact with the blockchain through its deployed blockchain nodes, writing or reading information on the chain. The public database mainly records the hash contents such as private transaction, data state and the like and is used for verifying the transaction.
The private databases of each user are partitioned according to the visible parties to the private transaction, distinguished by an ordered identification of the visible parties (for this example, user 1 has two private databases of "1_2" and "1_2_3"). The private transactions that occur between user 1 and user 2 will be recorded in the respective private databases "1_2" for user 1 and user 2, and the private transactions that occur between users 1, 2, and 3 will be recorded in the respective private databases "1_2_3" for users 1, 2, and 3.
The following flow assumes that user 1 initiates a private transaction with user 123 being visible to the transaction.
Scheme (1): the transaction initiator queries the status.
The transaction initiator (user 1) starts a timer during which it is asked whether the other transaction visible party (user 23) is able to perform the transaction. The transaction visible party returns a determination or negative information according to the situation (whether the account resource related to the private transaction is locked or not) of the transaction visible party. If the transaction initiator does not receive the determination information of all transaction visible parties within the timeout time of the timer (namely, the timeout or the existence of at least one transaction visible party returns negative information), the transaction flow of the round is ended. After receiving the determination information of all transaction visible parties, the transaction initiator enters a flow (2).
Flow (2): the transaction initiator broadcasts the transaction.
The transaction initiator (user 1) locks the account resources involved in the private transaction, and performs the transaction. After the execution, another timer is started, during which the transaction contents and the local execution result are broadcast to the transaction visible party (user 23), and the execution result of the transaction by the transaction visible party is waited.
Flow (3): the transaction visible party locking resource performs the transaction.
After receiving the private transaction, the transaction visible party locks account resources related to the private transaction. The transaction visible party performs the transaction locally based on the current data state of the locked account. The data states before and after transaction execution are recorded in the memory, and the data states stored in the original disk can not be influenced. The transaction visible party compares the result of the transaction execution with the transaction initiator and notifies the transaction initiator (success or failure). The relevant account resource remains locked at this point.
Flow (4): transaction initiator decisions.
(1) The transaction initiator notifies the transaction visible party to submit the cached data if and only if a reply is received that all transaction visible parties are successful within a defined time. The initiator also submits the data locally to the private database while initiating a normal transaction links the following information: A. a hash value of the private transaction; B. all private data construct a hash value of a Merkle tree root node; C. merkle verification paths constructed by other unmodified private data; D. identification of the party to the transaction. The data is synchronized between node nodes and is accessible to users other than the party visible to the transaction. (2) If the transaction initiator does not receive a reply that all the transaction visible parties are successful within a limited time, a notification is sent to the transaction visible party to terminate the transaction.
Flow (5): the transaction is visible to the party response.
The transaction visible party performs corresponding operation according to the content (submitting data/terminating transaction) notified by the transaction initiator in the process (4), or submits the locally cached data to a private database, or discards the locally cached data. And releasing the locked account resource after the operation is completed.
Some abnormal conditions possibly exist in the process and corresponding processing schemes.
(1) Single point problem:
the transaction initiator plays a role in coordination in the whole flow, and once the service of the transaction initiator is down, the normal operation of all transaction visible parties is affected, and other transactions cannot be executed in a blocking state because the resources are locked.
For the above case, embodiments of the present invention introduce a "mutual-polling mechanism". Part of the transaction visualizer (e.g., user 2) asks for execution by the other visualizer (e.g., user 3). If user 3 completes flow (5), either submitting data or terminating the transaction operation, user 2 may perform the same operations directly as user 3; if the user 3 has not entered the process (3), it can be inferred that the transaction initiator has issued a notification of "terminate transaction"; if user 3 completes process (3), user 2 may continue to query additional transaction visualizers. Only when all transaction visible parties only complete the process (3) but do not enter the process (5), the system is in a long-time blocking state, and manual intervention is needed.
(2) Data inconsistency:
the above-described flow has the possibility of data inconsistency. For example, in the process (4), the transaction initiator notifies the transaction visible party to submit data, possibly due to network reasons or due to downtime of the service of some transaction visible parties, the system will have the situation that some transaction visible parties submit data and other transaction visible parties do not submit data, so that data inconsistency is generated.
For the above case, embodiments of the present invention introduce a "snoop mechanism". All transaction observers can monitor the information such as the hash value of the uplink in the process (4) after restarting or periodically. Transaction-related information may be obtained from other parties to the transaction and verification performed, with the transaction-visible parties missing part of the private transaction. The hash value of the private transaction may verify the correctness and integrity of the private transaction content. After executing the private transaction, the transaction visible party calculates the hash value of the Merkle tree root node in series with the acquired verification path based on the modified data state of the transaction, and compares the hash value with the acquired hash value of the root node. If the two values are the same, the transaction executive modifies the local private database to realize the data consistency among all transaction visible parties.
In the embodiment of the invention, the transaction initiating party sends inquiry information to a plurality of transaction visible parties of private transaction in a blockchain, after receiving execution confirmation information returned by the transaction visible parties, executes the private transaction to obtain an execution result, broadcasts the private transaction and the execution result to the transaction visible parties, receives execution success information returned by the transaction visible parties in preset time, stores data related to executing the private transaction into a private database, determines verification data of the private transaction, stores the verification data of the private transaction into the blockchain, and broadcasts a data storage notice to the transaction visible parties so that the transaction visible parties store the data related to executing the private transaction into the private database chain of the transaction visible parties. By executing the private transaction locally, storing the data related to executing the private transaction in the private database and sending the verification data of the private transaction to the blockchain storage, compared with the existing scheme, the method has the advantages that the low resource occupancy rate can be realized, and the blockchain processing complexity is not increased.
Based on the same technical concept, fig. 4 illustrates an exemplary architecture of a private transaction processing device based on a blockchain, which may perform a private transaction processing flow based on the blockchain, according to an embodiment of the present invention.
As shown in fig. 4, the apparatus specifically includes:
a transmitting unit 401 for transmitting inquiry information to a plurality of transaction visible parties of a private transaction in a blockchain, so that the plurality of transaction visible parties confirm whether the private transaction can be executed;
a processing unit 402, configured to execute a private transaction after receiving execution confirmation information returned by the transaction visible parties, to obtain an execution result;
the sending unit 401 is further configured to broadcast the private transaction and the execution result to the transaction visible parties, so that the transaction visible parties execute the private transaction and compare the execution results;
the processing unit 402 is further configured to store data related to executing the private transaction in a private database after receiving execution success information returned by the plurality of transaction visible parties within a preset time, determine verification data of the private transaction, and store the verification data of the private transaction in the blockchain;
the sending unit 401 is further configured to broadcast a data storage notification to the transaction visible parties, so that the transaction visible parties store relevant data of the private transaction in their own private databases.
Optionally, the processing unit 402 is specifically configured to:
and locking account resources related to the private transaction, locally executing the private transaction based on the current data state of the account related to the private transaction, obtaining the data state of the private transaction after execution, and storing the data state in a local cache.
Optionally, the processing unit 402 is specifically configured to:
storing data related to executing the private transaction in a local cache into a local private database;
determining a hash value of the private transaction; determining a hash value of a root node of a merck tree of the private transaction according to data related to executing the private transaction; determining a verification path of the merck tree corresponding to unmodified data according to the unmodified data in the data related to executing the private transaction;
and determining the hash value of the private transaction, the hash value of the root node of the merck tree of the private transaction, the verification path of the merck tree corresponding to the unmodified data and the identification information of the transaction visible party of the private transaction as verification data of the private transaction.
Optionally, the processing unit 402 is further configured to:
and if the execution success information returned by all the transaction visible parties is not received within the preset time, sending a notification for ending the transaction to the transaction visible parties so that the transaction visible parties end the execution of the transaction and release the locked account resources.
Based on the same technical concept, fig. 5 illustrates an exemplary architecture of a private transaction processing device based on a blockchain, which may perform a private transaction processing flow based on the blockchain, according to an embodiment of the present invention.
As shown in fig. 5, the apparatus specifically includes:
an obtaining unit 501, configured to obtain a private transaction broadcast by a transaction initiator in a blockchain and an execution result of the transaction initiator;
the processing unit 502 is specifically configured to locally execute the private transaction to obtain an execution result, compare the execution result with an execution result of the transaction initiator, and send information about whether the execution is successful to the transaction initiator; and after receiving the data storage notification sent by the transaction initiator, storing the data related to executing the private transaction into a private database.
Optionally, the processing unit 502 is specifically configured to:
locking account resources related to the private transaction, locally executing the private transaction based on the current data state of the account related to the private transaction, obtaining the data state of the private transaction after execution, and storing the data state in a local cache;
comparing whether the execution result of the transaction initiator is consistent with the data state after the private transaction is executed, if so, determining that the execution is successful, and sending execution success information to the transaction initiator; otherwise, determining that the execution fails, and sending execution failure information to the transaction initiator.
Optionally, the processing unit 502 is specifically configured to:
storing data related to executing the private transaction in the local cache in a local private database.
Optionally, the processing unit 502 is further configured to:
when the transaction initiator is confirmed to be in a downtime state, sending a query to a first transaction visible party in the blockchain, and if the first transaction visible party is confirmed to submit data in a local cache, executing the same operation as the first transaction visible party; the first transaction visible party is any one of the other transaction visible parties in the blockchain;
if it is determined that the first transaction visible party does not perform the private transaction, the transaction initiator has terminated the transaction;
if the first transaction visible party is confirmed to execute and complete the private transaction, the other transaction visible parties except the first transaction visible party in the blockchain are continuously inquired until all the transaction visible parties in the blockchain are confirmed to execute and complete the private transaction, and then a system blocking notification is sent to staff.
Optionally, the processing unit 502 is further configured to:
after restarting or periodically monitoring verification data on the blockchain, if determining that missing data exists, acquiring the verification data from other visible parties on the blockchain;
Verifying the correctness and the integrity of the private transaction according to the hash value of the private transaction in the verification data, and executing the private transaction after the verification is passed, so as to obtain an execution result;
determining a hash value of a root node of the merck tree of the private transaction based on the execution result and a verification path of the merck tree of unmodified data in the verification data;
and when the hash value of the root node of the merck tree of the private transaction is consistent with the hash value of the root node of the merck tree in the verification data, storing the data related to executing the private transaction into a local private database.
Based on the same technical concept, the embodiment of the invention further provides a computing device, which comprises:
a memory for storing program instructions;
and the processor is used for calling the program instructions stored in the memory and executing the private transaction processing method based on the blockchain according to the obtained program.
Based on the same technical concept, the embodiment of the invention also provides a computer readable nonvolatile storage medium, which comprises computer readable instructions, wherein when the computer reads and executes the computer readable instructions, the computer executes the private transaction processing method based on the blockchain.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims (14)

1. A blockchain-based private transaction processing method, comprising:
The method comprises the steps that a transaction initiating party sends inquiry information to a plurality of transaction visible parties of private transactions in a blockchain, so that the plurality of transaction visible parties can confirm whether the private transactions can be executed or not;
after receiving the execution confirmation information returned by the transaction visible parties, the transaction initiator locks account resources related to the private transaction, locally executes the private transaction based on the current data state of the account related to the private transaction, obtains the data state of the private transaction after execution and stores the data state in a local cache as an execution result;
the transaction initiating party broadcasts the private transaction and the execution result to the transaction visible parties so that the transaction visible parties execute the private transaction and compare the execution result;
after receiving execution success information returned by the transaction visible parties within preset time, the transaction initiator stores data related to executing the private transaction in a local cache into a local private database, determines verification data of the private transaction, and stores the verification data of the private transaction into the blockchain;
the transaction initiation broadcasts a data storage notification to the plurality of transaction-visible parties to cause the plurality of transaction-visible parties to store data related to executing the private transaction to their own private databases.
2. The method of claim 1, wherein the transaction initiator determining authentication data for the private transaction comprises:
the transaction initiator determines a hash value of the private transaction; determining a hash value of a root node of a merck tree of the private transaction according to data related to executing the private transaction; determining a verification path of the merck tree corresponding to unmodified data according to the unmodified data in the data related to executing the private transaction;
the transaction initiator determines the hash value of the private transaction, the hash value of the root node of the merck tree of the private transaction, the verification path of the merck tree corresponding to the unmodified data and the identification information of the transaction visible party of the private transaction as the verification data of the private transaction.
3. The method of claim 1 or 2, wherein the method further comprises:
and if the transaction initiator does not receive the successful execution information returned by all the transaction visible parties within the preset time, sending a notification for ending the transaction to the transaction visible parties so that the transaction visible parties end the execution of the transaction and release the locked account resources.
4. A blockchain-based private transaction processing method, comprising:
the method comprises the steps that a transaction visible party obtains private transaction broadcast by a transaction initiator in a blockchain and an execution result of the transaction initiator;
the transaction visible party locks account resources related to the private transaction, executes the private transaction locally based on the current data state of the account related to the private transaction, obtains the data state of the private transaction after execution and stores the data state in a local cache as an execution result;
the transaction visible party compares whether the execution result of the transaction initiator is consistent with the data state after the private transaction is executed, if so, the transaction visible party determines that the execution is successful and sends execution success information to the transaction initiator; otherwise, determining that the execution fails, and sending execution failure information to the transaction initiator;
and after receiving the data storage notification sent by the transaction initiator, the transaction visible party stores the data related to executing the private transaction in the local cache into a local private database.
5. The method of claim 4, wherein the method further comprises:
when confirming that the transaction initiator is in a downtime state, the transaction visible party sends a query to a first transaction visible party in the blockchain, and if the first transaction visible party is confirmed to submit data in a local cache, the same operation as the first transaction visible party is executed; the first transaction visible party is any one of the other transaction visible parties in the blockchain;
The transaction initiator terminating the transaction if the transaction visible party determines that the first transaction visible party does not execute the private transaction;
and if the transaction visible party determines that the first transaction visible party executes and completes the private transaction, the transaction visible party continuously inquires other transaction visible parties except the first transaction visible party in the blockchain until the fact that all transaction visible parties in the blockchain execute the private transaction is confirmed, and then a system blocking notification is sent to staff.
6. The method of claim 4, wherein the method further comprises:
after restarting or periodically monitoring verification data on the blockchain by the transaction visible party, if determining that missing data exists, acquiring the verification data from other visible parties on the blockchain;
the transaction visible party verifies the correctness and the integrity of the private transaction according to the hash value of the private transaction in the verification data, and executes the private transaction after the verification is passed, so that an execution result is obtained;
the transaction visible party determines a hash value of a root node of the merck tree of the private transaction based on the execution result and a verification path of the merck tree of unmodified data in the verification data;
The transaction visible party stores the data related to executing the private transaction into a local private database when determining that the hash value of the root node of the merck tree of the private transaction is consistent with the hash value of the root node of the merck tree in the verification data.
7. A blockchain-based private transaction processing device, comprising:
a transmitting unit configured to transmit query information to a plurality of transaction visible parties of a private transaction in a blockchain, so that the plurality of transaction visible parties confirm whether the private transaction can be executed;
the processing unit is used for locking account resources related to the private transaction by the transaction initiator after receiving the execution confirmation information returned by the transaction visible parties, locally executing the private transaction based on the current data state of the account related to the private transaction, obtaining the data state of the private transaction after execution and storing the data state as an execution result in a local cache; the sending unit is further configured to broadcast the private transaction and the execution result to the transaction visible parties, so that the transaction visible parties execute the private transaction and compare the execution results;
The processing unit is further configured to store data related to executing the private transaction in a local cache into a local private database after receiving execution success information returned by the plurality of transaction visible parties within a preset time, determine verification data of the private transaction, and store the verification data of the private transaction into the blockchain;
the sending unit is further configured to broadcast a data storage notification to the plurality of transaction visible parties, so that the plurality of transaction visible parties store data related to executing the private transaction in their own private databases.
8. The apparatus of claim 7, wherein the processing unit is specifically configured to:
determining a hash value of the private transaction; determining a hash value of a root node of a merck tree of the private transaction according to data related to executing the private transaction; determining a verification path of the merck tree corresponding to unmodified data according to the unmodified data in the data related to executing the private transaction;
and determining the hash value of the private transaction, the hash value of the root node of the merck tree of the private transaction, the verification path of the merck tree corresponding to the unmodified data and the identification information of the transaction visible party of the private transaction as verification data of the private transaction.
9. The apparatus of claim 7 or 8, wherein the processing unit is further to:
and if the execution success information returned by all the transaction visible parties is not received within the preset time, sending a notification for ending the transaction to the transaction visible parties, so that the transaction visible parties end the execution of the transaction, and releasing the locked account resources.
10. A blockchain-based private transaction processing device, comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is specifically used for acquiring private transactions broadcasted by a transaction initiator in a blockchain and execution results of the transaction initiator;
the processing unit is specifically configured to lock an account resource related to the private transaction, locally execute the private transaction based on a current data state of an account related to the private transaction, obtain a data state after the private transaction is executed, and store the data state as an execution result in a local cache; the transaction visible party compares whether the execution result of the transaction initiator is consistent with the data state after the private transaction is executed, if so, the transaction visible party determines that the execution is successful and sends execution success information to the transaction initiator; otherwise, determining that the execution fails, and sending execution failure information to the transaction initiator; after receiving the data storage notification sent by the transaction initiator, storing the data related to executing the private transaction in the local cache into a local private database.
11. The apparatus of claim 10, wherein the processing unit is further to:
when the transaction initiator is confirmed to be in a downtime state, sending a query to a first transaction visible party in the blockchain, and if the first transaction visible party is confirmed to submit data in a local cache, executing the same operation as the first transaction visible party; the first transaction visible party is any one of the other transaction visible parties in the blockchain;
if it is determined that the first transaction visible party does not perform the private transaction, the transaction initiator has terminated the transaction;
if the first transaction visible party is confirmed to execute and complete the private transaction, the other transaction visible parties except the first transaction visible party in the blockchain are continuously inquired until all the transaction visible parties in the blockchain are confirmed to execute and complete the private transaction, and then a system blocking notification is sent to staff.
12. The apparatus of claim 10, wherein the processing unit is further to:
after restarting or periodically monitoring verification data on the blockchain, if determining that missing data exists, acquiring the verification data from other visible parties on the blockchain;
Verifying the correctness and the integrity of the private transaction according to the hash value of the private transaction in the verification data, and executing the private transaction after the verification is passed, so as to obtain an execution result;
determining a hash value of a root node of the merck tree of the private transaction based on the execution result and a verification path of the merck tree of unmodified data in the verification data;
and when the hash value of the root node of the merck tree of the private transaction is consistent with the hash value of the root node of the merck tree in the verification data, storing the data related to executing the private transaction into a local private database.
13. A computing device, comprising:
a memory for storing program instructions;
a processor for invoking program instructions stored in said memory to perform the method of any of claims 1 to 6 in accordance with the obtained program.
14. A computer readable non-transitory storage medium comprising computer readable instructions which, when read and executed by a computer, cause the computer to perform the method of any of claims 1 to 6.
CN202011412394.3A 2020-12-04 2020-12-04 Private transaction processing method and device based on blockchain Active CN112488680B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011412394.3A CN112488680B (en) 2020-12-04 2020-12-04 Private transaction processing method and device based on blockchain

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011412394.3A CN112488680B (en) 2020-12-04 2020-12-04 Private transaction processing method and device based on blockchain

Publications (2)

Publication Number Publication Date
CN112488680A CN112488680A (en) 2021-03-12
CN112488680B true CN112488680B (en) 2024-02-20

Family

ID=74938257

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011412394.3A Active CN112488680B (en) 2020-12-04 2020-12-04 Private transaction processing method and device based on blockchain

Country Status (1)

Country Link
CN (1) CN112488680B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10102265B1 (en) * 2017-04-12 2018-10-16 Vijay K. Madisetti Method and system for tuning blockchain scalability for fast and low-cost payment and transaction processing
CA3041162A1 (en) * 2018-11-07 2019-04-18 Alibaba Group Holding Limited Managing private transactions on blockchain networks based on workflow
CN110147684A (en) * 2019-05-24 2019-08-20 众安信息技术服务有限公司 For realizing the method and apparatus of block chain data-privacy protection
CN110147996A (en) * 2019-05-21 2019-08-20 中央财经大学 A kind of data trade localization difference method for secret protection and device based on block chain
CN111164935A (en) * 2019-05-31 2020-05-15 阿里巴巴集团控股有限公司 System and method for providing privacy and security protection in blockchain based private transactions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10102265B1 (en) * 2017-04-12 2018-10-16 Vijay K. Madisetti Method and system for tuning blockchain scalability for fast and low-cost payment and transaction processing
CA3041162A1 (en) * 2018-11-07 2019-04-18 Alibaba Group Holding Limited Managing private transactions on blockchain networks based on workflow
CN110147996A (en) * 2019-05-21 2019-08-20 中央财经大学 A kind of data trade localization difference method for secret protection and device based on block chain
CN110147684A (en) * 2019-05-24 2019-08-20 众安信息技术服务有限公司 For realizing the method and apparatus of block chain data-privacy protection
CN111164935A (en) * 2019-05-31 2020-05-15 阿里巴巴集团控股有限公司 System and method for providing privacy and security protection in blockchain based private transactions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于双层协同的联盟区块链隐私数据保护方法;蔡亮;端豪;鄢萌;夏鑫;;软件学报(第08期);第279-295页 *

Also Published As

Publication number Publication date
CN112488680A (en) 2021-03-12

Similar Documents

Publication Publication Date Title
WO2021042790A1 (en) Master node, slave node, system and method for distributed container cluster mirroring management
CN108769173B (en) Block chain implementation method and equipment for running intelligent contracts
CN111784518B (en) Block chain cross-chain processing method and device, computer equipment and storage medium
WO2020258846A1 (en) Method and apparatus for sending certifiable messages across chains
CN111080449B (en) Cross-chain transaction method of blockchain, management node and blockchain network
CN112800129B (en) Block state updating method, device, system and electronic equipment
WO2021109809A1 (en) Cross-chain transaction method and device
WO2021098139A1 (en) Method and device for storing state data of cross-chain transaction, and storage medium
CN110222085B (en) Processing method and device for certificate storage data and storage medium
WO2022206454A1 (en) Method and apparatus for providing cross-chain messages
CN111899019A (en) Method and system for cross validation and sharing of blacklist and multiple parties
CN111401904B (en) Consensus method and system in alliance chain
CN111582845A (en) Cross-chain transaction method and device of block chain and electronic equipment
CN110096511B (en) Data consistency verification method, device, equipment and medium based on private chain
CN110535933B (en) Parallel chain consensus method, device and storage medium
CN112488680B (en) Private transaction processing method and device based on blockchain
CN113689216A (en) Cross-chain transaction processing method and device, equipment, storage medium and program product
CN111143041B (en) Data consistency method, distributed coordinator and central coordinator
CN113326272A (en) Distributed transaction processing method, device and system
EP4128107A1 (en) Method and apparatus maintaining private data with consortium blockchain
EP4220518A1 (en) Blockchain network-based device management method, related device, and storage medium
CN115544034A (en) Data consistency method and service system
CN112235110B (en) Cross-chain service processing method and device of block chain and electronic equipment
CN112950180A (en) Community certificate method and system based on alliance chain, electronic device and storage medium
CN110765193A (en) Method and device for exporting block chain 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
GR01 Patent grant
GR01 Patent grant