CN111783151A - Management method and device of block chain account book and computer equipment - Google Patents
Management method and device of block chain account book and computer equipment Download PDFInfo
- Publication number
- CN111783151A CN111783151A CN202010621782.6A CN202010621782A CN111783151A CN 111783151 A CN111783151 A CN 111783151A CN 202010621782 A CN202010621782 A CN 202010621782A CN 111783151 A CN111783151 A CN 111783151A
- Authority
- CN
- China
- Prior art keywords
- transaction
- user
- data
- pair
- chain network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title description 8
- 238000000034 method Methods 0.000 claims abstract description 75
- 230000001360 synchronised effect Effects 0.000 claims abstract description 46
- 238000012790 confirmation Methods 0.000 claims abstract description 31
- 230000008569 process Effects 0.000 claims description 46
- 239000002245 particle Substances 0.000 claims description 41
- 238000012795 verification Methods 0.000 claims description 20
- 238000013475 authorization Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008859 change Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- 230000009467 reduction Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- RTZKZFJDLAIYFH-UHFFFAOYSA-N Diethyl ether Chemical compound CCOCC RTZKZFJDLAIYFH-UHFFFAOYSA-N 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- 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 application discloses a method for managing a block chain account book, which comprises the following steps: receiving first transaction data written by a first user in a alliance chain network, wherein the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data; storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed account book of the alliance chain network; associating a second user having a transaction relationship with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair; judging whether the first transaction and the second transaction in the appointed transaction pair are executed correctly or not; if yes, judging whether a confirmation result of zero knowledge proof of the transaction relation of the third user to the first transaction pair in the alliance chain network is received; if yes, the transaction states of the first transaction and the second transaction in the distributed account book are changed into confirmed states and are distributed in the alliance chain network, and privacy and safety of the transaction are improved.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and an apparatus for managing a blockchain ledger book, and a computer device.
Background
With the advent of encrypted digital currency represented by bitcoin and ether house, the use of digital assets based on blockchain technology has increased. The digital assets generally correspond to a set of digital asset ledgers. At present, information cleartext such as transaction amount, transaction balance and the like of two transaction parties of a digital asset account is written on a chain, and the data privacy digital asset account book management method of the two transaction parties cannot be well protected, so that the defects exist in the aspects of transaction privacy and safety. Moreover, the existing transaction is generally carried out in a single stroke, the state modification happens when the transaction is executed, and the transaction cannot be retrieved if an error occurs.
Disclosure of Invention
The application mainly aims to provide a method for managing a blockchain account book, and aims to solve the technical problem that the privacy and the safety of the existing blockchain transaction are not sufficient.
The application provides a method for managing a block chain account book, which comprises the following steps:
receiving first transaction data written by a first user in a alliance chain network, wherein the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data;
storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed ledger of the federation chain network;
associating a second user having a transaction relationship with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair;
judging whether a first transaction and a second transaction in the appointed transaction pair are executed correctly or not, wherein the first transaction is a process that the first user sends a first transaction object to the second user, and the second transaction is a process that the second user feeds back a second transaction object to the first user according to the first transaction object;
if yes, judging whether a confirmation result of a third user in a alliance chain network for zero knowledge proof of the transaction relationship of the first transaction pair is received, wherein the third user is other users except the first user and the second user in the alliance chain network;
and if so, changing the transaction states of the first transaction and the second transaction in the distributed ledger into confirmed states, and distributing the confirmed states in the alliance-link network.
Preferably, the step of receiving first transaction data written by a first user in a alliance-link network includes:
receiving data content written by the first user;
splitting the data content written by the first user into a plurality of data particles according to the content of a preset task configuration file;
respectively calling a preset encryption program to encrypt according to transaction objects respectively corresponding to the data particles, wherein the transaction objects correspond to the preset encryption program one by one;
and combining the respectively encrypted data particles into the first transaction data according to the arrangement sequence before encryption.
Preferably, the step of associating a second user having a transaction relationship with the first user according to the first transaction data comprises:
acquiring a task association relation corresponding to the first transaction data according to a preset task configuration file;
setting a first user and a second user in the task association relation corresponding to the first transaction data as the designated transaction pair;
and setting the particle data corresponding to the first user and the second user in the appointed transaction pair as interface data for completing the corresponding task of the appointed transaction pair, so as to execute the corresponding task of the appointed transaction pair by calling the interface data.
Preferably, the step of determining whether a confirmation result of zero-knowledge proof of the transaction relationship of the first transaction pair is received from a third user in a federation chain network includes:
sending the transaction relation certification data corresponding to the first transaction and the second transaction to the third user;
receiving a query result of the third user for querying the transaction relation certification data corresponding to the first transaction and the second transaction, and comparing the query result with the synchronous ciphertext corresponding to the first transaction and the second transaction to obtain a verification result;
if the verification result is transaction relationship certification data corresponding to the first transaction and the second transaction and corresponds to the content of the synchronous ciphertext corresponding to the first transaction and the second transaction, determining that a confirmation result of a zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network is received, otherwise, not receiving the confirmation result of the zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network.
Preferably, the step of receiving the first transaction data written by the first user in the alliance-link network is preceded by:
judging whether each user applying for joining the alliance link network receives the authorization file or not;
if so, associating nodes respectively corresponding to all users receiving the authorization file as the alliance chain network;
and initializing a distributed account book in the alliance chain network according to the asset information of each user, wherein the initialized distributed account book comprises an account corresponding to each user and an account initial balance.
Preferably, the step of determining whether the first transaction and the second transaction in the designated transaction pair have been executed correctly includes:
acquiring a transaction execution sequence of the first transaction and the second transaction according to the preset task configuration file;
judging whether execution feedback corresponding to the first transaction and the second transaction is received in sequence or not according to the transaction execution sequence;
if yes, judging whether each execution feedback is normal in the execution process and correct in the execution result;
if yes, judging whether the first transaction and the second transaction in the appointed transaction pair are executed correctly or not, otherwise, not executing.
The application also provides a management device of the block chain account book, which comprises:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving first transaction data written by a first user in a alliance chain network, and the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data;
the storage module is used for storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed account book of the alliance chain network;
the first association module is used for associating a second user with a transaction relation with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair;
a first judging module, configured to judge whether a first transaction and a second transaction in the designated transaction pair are both executed correctly, where the first transaction is a process in which the first user sends a first transaction object to the second user, and the second transaction is a process in which the second user feeds back a second transaction object to the first user according to the first transaction object;
a second determining module, configured to determine whether a confirmation result of a zero knowledge proof of a transaction relationship of a first transaction pair is received from a third user in a federation chain network if all the first and second users have been correctly executed, where the third user is another user in the federation chain network except the first user and the second user;
and the issuing module is used for changing the transaction states of the first transaction and the second transaction in the distributed account book into confirmed states and issuing the confirmed states into the alliance chain network if a confirmation result of zero knowledge proof of the transaction relationship of the first transaction pair by a third user in the alliance chain network is received.
The present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method as described above.
The method supports the authority of the owner of the digital asset account for encrypting the transaction data written into the alliance chain network, other users of the alliance chain network can check the encrypted transaction data after obtaining authorization, and by setting the transaction pair, when all transactions in the transaction pair are executed and the transaction relationship in the transaction pair is proved to be really stored according to zero knowledge, the transaction state in the transaction pair can be confirmed and changed from 'to be confirmed' to 'confirmed', and the privacy and the safety of the transaction are improved.
Drawings
Fig. 1 is a schematic flow chart illustrating a method for managing a block chain account book according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a device for managing a blockchain account book according to an embodiment of the present application;
fig. 3 is a schematic diagram of an internal structure of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Referring to fig. 1, a method for managing a blockchain account book according to an embodiment of the present application includes:
s1: receiving first transaction data written by a first user in a alliance chain network, wherein the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data;
s2: storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed ledger of the federation chain network;
s3: associating a second user having a transaction relationship with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair;
s4: judging whether a first transaction and a second transaction in the appointed transaction pair are executed correctly or not, wherein the first transaction is a process that the first user sends a first transaction object to the second user, and the second transaction is a process that the second user feeds back a second transaction object to the first user according to the first transaction object;
s5: if yes, judging whether a confirmation result of a third user in a alliance chain network for zero knowledge proof of the transaction relationship of the first transaction pair is received, wherein the third user is other users except the first user and the second user in the alliance chain network;
s6: and if so, changing the transaction states of the first transaction and the second transaction in the distributed ledger into confirmed states, and distributing the confirmed states in the alliance-link network.
The account book of the alliance chain network is a distributed account book, the structure and the data of the account book of the corresponding node of each user in the alliance chain network are the same, when the account book of the corresponding node of each user shows the data, only the account column data of the user at the current node is shown, and the account column data corresponding to other nodes are in an encrypted hidden state. When the user writes data, the distributed account book is encrypted at the same time, and the user corresponding to the unauthorized other node cannot view the data, namely, the data is in an encrypted hidden state. When the distributed account book is initialized, information such as the address of each account, the account balance and the like is stored in the distributed account book in an encrypted manner, and each user can only see the address and the balance of the account belonging to the user. The above-mentioned every account column data includes information such as account transaction amount, account balance, etc. When a transaction occurs, the transaction safety is realized through a transaction pair mechanism, the transaction pair refers to the association binding of two or more transaction parties, for example, the transaction behavior points to the same transaction object, the transaction pair is set, and the synchronous confirmation of all transaction execution states related to the transaction pair is carried out through the binding, so that the problem that the transaction is unsafe because the state change is completed after the transaction of one party is completed and the error marking of transaction data occurs when the transaction cannot be executed or is executed incorrectly to the other party is avoided. For example, the transaction task is to purchase a lot of goods, and the pending transaction is changed to be confirmed when the supplier sends the goods. When the other party receiving the goods does not pay money or the payment is wrong, the determined state of the delivery party has been released to the alliance chain network, and the change cannot be made, so that the transaction safety is poor. According to the method and the device, the first transaction of the goods sent by the goods sending party and the second transaction of the payment of the goods from the goods receiving party are related to form the transaction pair, and when all the transactions related to the transaction pair are determined to be completed, the transaction state in the transaction pair is changed simultaneously, so that the transaction safety is promoted. The first user and the second user are users in a transaction pair, the transaction pair may include two or more users, and the third user represents a user other than the transaction pair, but the first user, the second user, and the third user are not limited to the distinction, and are all users in the alliance-link network.
Further, the step S1 of receiving the first transaction data written by the first user in the alliance-link network includes:
s11: receiving data content written by the first user;
s12: splitting the data content written by the first user into a plurality of data particles according to the content of a preset task configuration file;
s12: respectively calling a preset encryption program to encrypt according to transaction objects respectively corresponding to the data particles, wherein the transaction objects correspond to the preset encryption program one by one;
s13: and combining the respectively encrypted data particles into the first transaction data according to the arrangement sequence before encryption.
The first transaction data written by the first user can be encrypted and authorized by field division, so that the authorization fineness is improved. The data content of the first transaction data is composed of a plurality of fields, each field is a data particle, and the fields are divided according to the participants involved in the transaction process in the preset task configuration file and the functions of the participants in the transaction. For example, if the number of the parties involved in the transaction pair includes ten, the number of the fields in the first transaction data includes at least ten, and the encryption programs of the data particles corresponding to the ten parties are different from each other, so that the ten parties are authorized separately. The encryption program comprises an encryption mode and an encryption assignment, wherein the encryption mode comprises symmetric encryption or asymmetric encryption and the like. The encryption programs corresponding to different participants can be edited in a task configuration file in advance or stored in a database in a mapping table mode, so that the data particles corresponding to the corresponding participants can be called and encrypted conveniently and timely.
Further, step S3, associating a second user having a transaction relationship with the first user according to the first transaction data, includes:
s31: acquiring a task association relation corresponding to the first transaction data according to a preset task configuration file;
s32: setting a first user and a second user in the task association relation corresponding to the first transaction data as the designated transaction pair;
s32: and setting the particle data corresponding to the first user and the second user in the appointed transaction pair as interface data for completing the corresponding task of the appointed transaction pair, so as to execute the corresponding task of the appointed transaction pair by calling the interface data.
The above-mentioned transaction pair is a combination of two or more related transactions, and this embodiment will be described in detail by taking an example that two transactions are included in the transaction pair, and the implementation process of including multiple transactions in the transaction pair is similar to the implementation process of including two transactions in the transaction pair, and is not described in detail. The first transaction data carries a synchronous ciphertext encrypted by the first user for the first transaction data, the first user and the second user are opposite parties of two transactions included in the transaction pair, such as a goods issuer and a goods payment issuer, and the second user can receive data of the decrypted synchronous ciphertext. The task association relationship comprises that the transaction objects point to corresponding or same objects. According to the embodiment, the particle data combined into the transaction pairs are configured as the interface calling data, so that the particle data in the transaction team are associated through the calling interface, and the task is conveniently executed. The alliance-link network of this embodiment includes a plurality of transaction pairs, and the user nodes in the alliance-link network included in each transaction pair are also different, and the execution of each transaction pair has mutual independence. "transaction pairs" map two or more transactions in the real world that are related to each other, which are a combination of transactions, often performed in their entirety or not.
Further, the step S5 of determining whether a confirmation result of the zero-knowledge proof of the transaction relationship of the first transaction pair is received from the third user in the alliance-link network includes:
s51: sending the transaction relation certification data corresponding to the first transaction and the second transaction to the third user;
s52: receiving a query result of the third user for querying the transaction relation certification data corresponding to the first transaction and the second transaction, and comparing the query result with the synchronous ciphertext corresponding to the first transaction and the second transaction to obtain a verification result;
s53: if the verification result is transaction relationship certification data corresponding to the first transaction and the second transaction and corresponds to the content of the synchronous ciphertext corresponding to the first transaction and the second transaction, determining that a confirmation result of a zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network is received, otherwise, not receiving the confirmation result of the zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network.
When a transaction occurs, information such as addresses of both transaction parties, transaction amount, account balance before and after the transaction and the like is also stored in the distributed account book in an encrypted manner, each user can only see the information such as the address of the account, the transaction amount, the account balance before and after the transaction and the like, and the authenticity and correctness of the transaction need to be verified so as to ensure the transaction safety. The third user of this embodiment can determine the authenticity of the transaction of each participant in the transaction pair according to the transaction relationship certification data provided by the participants in the transaction pair, corresponding to the content of the synchronization ciphertext, without knowing the encryption key of each participant in the transaction pair. The transaction relation proving data comprises the number of the target objects of the transaction and the like; the content of the synchronous ciphertext is different according to different responsibilities of the participants, and comprises a goods reduction amount of a sender, a balance reduction amount of a receiver and the like. The zero-knowledge proof process of this embodiment can verify not only the total assets of the entire alliance-link network, but also the specific data corresponding to each field because each field of the transaction data is encrypted respectively. The verified content includes: whether the sum of the balances of all accounts is correct, whether the account balance of a particular or single account overflows, whether the transaction amount of a particular or single transaction overflows, whether two transactions in a "transaction pair" match, etc. The specific verification process of the zero-knowledge proof comprises the following steps: the transaction participant writes the specified particle data synchronous ciphertext into the alliance chain network; decrypting the data of the synchronous ciphertext through a consensus mechanism of the alliance chain network, and sending the decrypted data to a transaction participant corresponding to the specified particle data in the transaction pair and other users participating in verification in the alliance chain network; all the participants of the transaction provide the certification of the transaction relationship and issue the certification data of the transaction relationship in the alliance chain network so that the users participating in the verification can verify the transaction information; and other users on the alliance chain network inquire and verify the transaction relationships, and after the verification confirms the authenticity and passes, the transaction state is changed into confirmed state and is distributed in the alliance chain network.
Further, before the step S1 of receiving the first transaction data written by the first user in the alliance-link network, the method includes:
s101: judging whether each user applying for joining the alliance link network receives the authorization file or not;
s102: if so, associating nodes respectively corresponding to all users receiving the authorization file as the alliance chain network;
s103: and initializing a distributed account book in the alliance chain network according to the asset information of each user, wherein the initialized distributed account book comprises an account corresponding to each user and an account initial balance.
Each user in the alliance chain network can be added after being authorized, the network nodes in the alliance chain network are mapped according to the user information, distributed accounts are initialized in the alliance chain network according to the asset information of each user added in the alliance chain network, and each user node corresponds to one column of data or one row of data in the distributed accounts. The asset information of each user comprises assets such as real estate, accounts receivable and bills of the user. The initialization process described above includes two steps: and creating a user account and setting an account initial balance so as to anchor the association relationship between each user and each user node through the user account.
Further, the step S4 of determining whether the first transaction and the second transaction in the designated transaction pair have been correctly executed includes:
s41: acquiring a transaction execution sequence of the first transaction and the second transaction according to the preset task configuration file;
s42: judging whether execution feedback corresponding to the first transaction and the second transaction is received in sequence or not according to the transaction execution sequence;
s43: if yes, judging whether each execution feedback is normal in the execution process and correct in the execution result;
s44: if yes, judging whether the first transaction and the second transaction in the appointed transaction pair are executed correctly or not, otherwise, not executing.
The completion orders of the first transaction and the second transaction corresponding to different transaction tasks are different, and the completion orders comprise a tandem continuous completion mode and a synchronous concurrent completion mode. The completion sequence of the first transaction and the second transaction can be edited in a preset task configuration file in advance according to the task implementation process to form an automatic operation process. Executing the first transaction and the second transaction in a tandem and successive completion mode as an example, executing a first transaction of a transaction pair, and recording a transaction result as 'to be confirmed' after the execution is finished; then executing a second transaction of the transaction pair, and recording a transaction result as 'to be confirmed' after the execution is finished; if the first transaction and the second transaction are both normally executed and ended, updating the transaction states of the first transaction and the second transaction to be confirmed; if the transaction of the first transaction and the second transaction is abnormal, the transaction states of the first transaction and the second transaction are still to be confirmed, and the transaction safety is improved.
Referring to fig. 2, a management apparatus of a blockchain account book according to an embodiment of the present application includes:
the system comprises a receiving module 1, a sending module and a receiving module, wherein the receiving module is used for receiving first transaction data written by a first user in a alliance chain network, and the first transaction data carries a synchronous ciphertext of the first user for encrypting the first transaction data;
the storage module 2 is configured to store the first transaction data and the synchronous ciphertext of the first transaction data in a distributed ledger of the federation chain network;
a first association module 3, configured to associate, according to the first transaction data, a second user having a transaction relationship with the first user, where the second user and the first user are associated as a designated transaction pair;
a first judging module 4, configured to judge whether a first transaction and a second transaction in the designated transaction pair are both executed correctly, where the first transaction is a process in which the first user sends a first transaction object to the second user, and the second transaction is a process in which the second user feeds back a second transaction object to the first user according to the first transaction object;
a second determining module 5, configured to determine whether a confirmation result of a zero knowledge proof of a transaction relationship of the first transaction pair is received from a third user in a federation chain network if all the first and second transactions are correctly executed, where the third user is another user in the federation chain network except the first user and the second user;
and the issuing module 6 is configured to change the transaction states of the first transaction and the second transaction in the distributed ledger into a confirmed state and issue the changed transaction states in the alliance-link network if a confirmation result of zero knowledge proof of the transaction relationship of the first transaction pair by a third user in the alliance-link network is received.
The account book of the alliance chain network is a distributed account book, the structure and the data of the account book of the corresponding node of each user in the alliance chain network are the same, when the account book of the corresponding node of each user shows the data, only the account column data of the user at the current node is shown, and the account column data corresponding to other nodes are in an encrypted hidden state. When the user writes data, the distributed account book is encrypted at the same time, and the user corresponding to the unauthorized other node cannot view the data, namely, the data is in an encrypted hidden state. When the distributed account book is initialized, information such as the address of each account, the account balance and the like is stored in the distributed account book in an encrypted manner, and each user can only see the address and the balance of the account belonging to the user. The above-mentioned every account column data includes information such as account transaction amount, account balance, etc. When a transaction occurs, the transaction safety is realized through a transaction pair mechanism, the transaction pair refers to the association binding of two or more transaction parties, for example, the transaction behavior points to the same transaction object, the transaction pair is set, and the synchronous confirmation of all transaction execution states related to the transaction pair is carried out through the binding, so that the problem that the transaction is unsafe because the state change is completed after the transaction of one party is completed and the error marking of transaction data occurs when the transaction cannot be executed or is executed incorrectly to the other party is avoided. For example, the transaction task is to purchase a lot of goods, and the pending transaction is changed to be confirmed when the supplier sends the goods. When the other party receiving the goods does not pay money or the payment is wrong, the determined state of the delivery party has been released to the alliance chain network, and the change cannot be made, so that the transaction safety is poor. According to the method and the device, the first transaction of the goods sent by the goods sending party and the second transaction of the payment of the goods from the goods receiving party are related to form the transaction pair, and when all the transactions related to the transaction pair are determined to be completed, the transaction state in the transaction pair is changed simultaneously, so that the transaction safety is promoted. The first user and the second user are users in a transaction pair, the transaction pair may include two or more users, and the third user represents a user other than the transaction pair, but the first user, the second user, and the third user are not limited to the distinction, and are all users in the alliance-link network.
Further, the receiving module 1 includes:
a receiving unit, configured to receive data content written by the first user;
the splitting unit is used for splitting the data content written by the first user into a plurality of data particles according to the content of a preset task configuration file;
the encryption unit is used for respectively calling a preset encryption program to encrypt according to transaction objects respectively corresponding to the data particles, wherein the transaction objects correspond to the preset encryption program one by one;
and the combination unit is used for combining the encrypted data particles into the first transaction data according to the arrangement sequence before encryption.
The first transaction data written by the first user can be encrypted and authorized by field division, so that the authorization fineness is improved. The data content of the first transaction data is composed of a plurality of fields, each field is a data particle, and the fields are divided according to the participants involved in the transaction process in the preset task configuration file and the functions of the participants in the transaction. For example, if the number of the parties involved in the transaction pair includes ten, the number of the fields in the first transaction data includes at least ten, and the encryption programs of the data particles corresponding to the ten parties are different from each other, so that the ten parties are authorized separately. The encryption program comprises an encryption mode and an encryption assignment, wherein the encryption mode comprises symmetric encryption or asymmetric encryption and the like. The encryption programs corresponding to different participants can be edited in a task configuration file in advance or stored in a database in a mapping table mode, so that the data particles corresponding to the corresponding participants can be called and encrypted conveniently and timely.
Further, the first association module 3 includes:
the first acquisition unit is used for acquiring a task association relation corresponding to the first transaction data according to a preset task configuration file;
the first setting unit is used for setting a first user and a second user in the task association relation corresponding to the first transaction data as the appointed transaction pair;
and the second setting unit is used for setting the particle data corresponding to the first user and the second user in the appointed transaction pair as interface data for completing the corresponding task of the appointed transaction pair, so that the corresponding task of the appointed transaction pair is executed by calling the interface data.
The above-mentioned transaction pair is a combination of two or more related transactions, and this embodiment will be described in detail by taking an example that two transactions are included in the transaction pair, and the implementation process of including multiple transactions in the transaction pair is similar to the implementation process of including two transactions in the transaction pair, and is not described in detail. The first transaction data carries a synchronous ciphertext encrypted by the first user for the first transaction data, the first user and the second user are opposite parties of two transactions included in the transaction pair, such as a goods issuer and a goods payment issuer, and the second user can receive data of the decrypted synchronous ciphertext. The task association relationship comprises that the transaction objects point to corresponding or same objects. According to the embodiment, the particle data combined into the transaction pairs are configured as the interface calling data, so that the particle data in the transaction team are associated through the calling interface, and the task is conveniently executed. The alliance-link network of this embodiment includes a plurality of transaction pairs, and the user nodes in the alliance-link network included in each transaction pair are also different, and the execution of each transaction pair has mutual independence. "transaction pairs" map two or more transactions in the real world that are related to each other, which are a combination of transactions, often performed in their entirety or not.
Further, the second determining module 5 includes:
a sending unit, configured to send transaction relationship certification data corresponding to the first transaction and the second transaction to the third user;
the comparison unit is used for receiving a query result of the third user for querying the transaction relation certification data corresponding to the first transaction and the second transaction, and comparing the query result with the synchronous ciphertext corresponding to the first transaction and the second transaction to obtain a verification result;
and a first determination unit, configured to determine that a confirmation result of the zero knowledge proof of the transaction relationship of the first transaction pair is received from a third user in the alliance-link network if the verification result is the transaction relationship proof data corresponding to the first transaction and the second transaction and corresponds to the content of the synchronous ciphertext corresponding to the first transaction and the second transaction, and otherwise, that a confirmation result of the zero knowledge proof of the transaction relationship of the first transaction pair is not received from the third user in the alliance-link network.
When a transaction occurs, information such as addresses of both transaction parties, transaction amount, account balance before and after the transaction and the like is also stored in the distributed account book in an encrypted manner, each user can only see the information such as the address of the account, the transaction amount, the account balance before and after the transaction and the like, and the authenticity and correctness of the transaction need to be verified so as to ensure the transaction safety. The third user of this embodiment can determine the authenticity of the transaction of each participant in the transaction pair according to the transaction relationship certification data provided by the participants in the transaction pair, corresponding to the content of the synchronization ciphertext, without knowing the encryption key of each participant in the transaction pair. The transaction relation proving data comprises the number of the target objects of the transaction and the like; the content of the synchronous ciphertext is different according to different responsibilities of the participants, and comprises a goods reduction amount of a sender, a balance reduction amount of a receiver and the like. The zero-knowledge proof process of this embodiment can verify not only the total assets of the entire alliance-link network, but also the specific data corresponding to each field because each field of the transaction data is encrypted respectively. The verified content includes: whether the sum of the balances of all accounts is correct, whether the account balance of a particular or single account overflows, whether the transaction amount of a particular or single transaction overflows, whether two transactions in a "transaction pair" match, etc. The specific verification process of the zero-knowledge proof comprises the following steps: the transaction participant writes the specified particle data synchronous ciphertext into the alliance chain network; decrypting the data of the synchronous ciphertext through a consensus mechanism of the alliance chain network, and sending the decrypted data to a transaction participant corresponding to the specified particle data in the transaction pair and other users participating in verification in the alliance chain network; all the participants of the transaction provide the certification of the transaction relationship and issue the certification data of the transaction relationship in the alliance chain network so that the users participating in the verification can verify the transaction information; and other users on the alliance chain network inquire and verify the transaction relationships, and after the verification confirms the authenticity and passes, the transaction state is changed into confirmed state and is distributed in the alliance chain network.
Further, the management device of the blockchain account book comprises:
the third judging module is used for judging whether each user applying for joining the alliance chain network receives the authorization file;
the second association module is used for associating the nodes respectively corresponding to the users receiving the authorization file as the alliance link network if the authorization file is received;
and the initialization module is used for initializing a distributed account book in the alliance link network according to the asset information of each user, wherein the initialized distributed account book comprises an account and an account initial balance corresponding to each user.
Each user in the alliance chain network can be added after being authorized, the network nodes in the alliance chain network are mapped according to the user information, distributed accounts are initialized in the alliance chain network according to the asset information of each user added in the alliance chain network, and each user node corresponds to one column of data or one row of data in the distributed accounts. The asset information of each user comprises assets such as real estate, accounts receivable and bills of the user. The initialization process described above includes two steps: and creating a user account and setting an account initial balance so as to anchor the association relationship between each user and each user node through the user account.
Further, the first determining module 4 includes:
the second acquisition unit is used for acquiring the transaction execution sequence of the first transaction and the second transaction according to the preset task configuration file;
the first judging unit is used for judging whether execution feedback corresponding to the first transaction and the second transaction is received in sequence according to the transaction execution sequence;
the second judging unit is used for judging whether the execution feedback is normal in the execution process and correct in the execution result if the execution feedback corresponding to the first transaction and the second transaction is received in sequence;
and the second judging unit is used for judging whether the first transaction and the second transaction in the appointed transaction pair are correctly executed or not if the execution processes are normal and the execution result is correct, and otherwise, the execution is not finished.
The completion orders of the first transaction and the second transaction corresponding to different transaction tasks are different, and the completion orders comprise a tandem continuous completion mode and a synchronous concurrent completion mode. The completion sequence of the first transaction and the second transaction can be edited in a preset task configuration file in advance according to the task implementation process to form an automatic operation process. Executing the first transaction and the second transaction in a tandem and successive completion mode as an example, executing a first transaction of a transaction pair, and recording a transaction result as 'to be confirmed' after the execution is finished; then executing a second transaction of the transaction pair, and recording a transaction result as 'to be confirmed' after the execution is finished; if the first transaction and the second transaction are both normally executed and ended, updating the transaction states of the first transaction and the second transaction to be confirmed; if the transaction of the first transaction and the second transaction is abnormal, the transaction states of the first transaction and the second transaction are still to be confirmed, and the transaction safety is improved.
Referring to fig. 3, a computer device, which may be a server and whose internal structure may be as shown in fig. 3, is also provided in the embodiment of the present application. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer designed processor is used to provide computational and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used for storing all data required by the management process of the blockchain account book. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of managing a blockchain ledger.
The processor executes the management method of the block chain account book, and the method comprises the following steps: receiving first transaction data written by a first user in a alliance chain network, wherein the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data; storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed ledger of the federation chain network; associating a second user having a transaction relationship with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair; judging whether a first transaction and a second transaction in the appointed transaction pair are executed correctly or not, wherein the first transaction is a process that the first user sends a first transaction object to the second user, and the second transaction is a process that the second user feeds back a second transaction object to the first user according to the first transaction object; if yes, judging whether a confirmation result of a third user in a alliance chain network for zero knowledge proof of the transaction relationship of the first transaction pair is received, wherein the third user is other users except the first user and the second user in the alliance chain network; and if so, changing the transaction states of the first transaction and the second transaction in the distributed ledger into confirmed states, and distributing the confirmed states in the alliance-link network.
The computer equipment supports the authority of the owner of the digital asset account for encrypting the transaction data written into the alliance chain network, other users of the alliance chain network can check the encrypted transaction data after obtaining authorization, and by setting the transaction pairs, when all transactions in the transaction pairs are executed and the transaction relationship in the transaction pairs is proved to be really stored according to zero knowledge, the transaction state in the transaction pairs can be confirmed and is changed from 'to be confirmed' to 'confirmed', and the privacy and the safety of the transactions are improved.
In one embodiment, the step of receiving, by the processor, first transaction data written by a first user in a federation chain network includes: receiving data content written by the first user; splitting the data content written by the first user into a plurality of data particles according to the content of a preset task configuration file; respectively calling a preset encryption program to encrypt according to transaction objects respectively corresponding to the data particles, wherein the transaction objects correspond to the preset encryption program one by one; and combining the respectively encrypted data particles into the first transaction data according to the arrangement sequence before encryption.
In one embodiment, the step of associating, by the processor, a second user having a transaction relationship with the first user based on the first transaction data includes: acquiring a task association relation corresponding to the first transaction data according to a preset task configuration file; setting a first user and a second user in the task association relation corresponding to the first transaction data as the designated transaction pair; and setting the particle data corresponding to the first user and the second user in the appointed transaction pair as interface data for completing the corresponding task of the appointed transaction pair, so as to execute the corresponding task of the appointed transaction pair by calling the interface data.
In an embodiment, the step of determining whether a confirmation result of zero-knowledge proof of the transaction relationship of the first transaction pair is received from a third user in the alliance-link network includes: sending the transaction relation certification data corresponding to the first transaction and the second transaction to the third user; receiving a query result of the third user for querying the transaction relation certification data corresponding to the first transaction and the second transaction, and comparing the query result with the synchronous ciphertext corresponding to the first transaction and the second transaction to obtain a verification result; if the verification result is transaction relationship certification data corresponding to the first transaction and the second transaction and corresponds to the content of the synchronous ciphertext corresponding to the first transaction and the second transaction, determining that a confirmation result of a zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network is received, otherwise, not receiving the confirmation result of the zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network.
In one embodiment, the step of receiving, by the processor, first transaction data written by a first user in the alliance-link network is preceded by: judging whether each user applying for joining the alliance link network receives the authorization file or not; if so, associating nodes respectively corresponding to all users receiving the authorization file as the alliance chain network; and initializing a distributed account book in the alliance chain network according to the asset information of each user, wherein the initialized distributed account book comprises an account corresponding to each user and an account initial balance.
In one embodiment, the step of determining whether the first transaction and the second transaction in the designated transaction pair have been executed correctly by the processor includes: acquiring a transaction execution sequence of the first transaction and the second transaction according to the preset task configuration file; judging whether execution feedback corresponding to the first transaction and the second transaction is received in sequence or not according to the transaction execution sequence; if yes, judging whether each execution feedback is normal in the execution process and correct in the execution result; if yes, judging whether the first transaction and the second transaction in the appointed transaction pair are executed correctly or not, otherwise, not executing.
Those skilled in the art will appreciate that the architecture shown in fig. 3 is only a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects may be applied.
An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for managing a blockchain ledger, and the method includes: receiving first transaction data written by a first user in a alliance chain network, wherein the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data; storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed ledger of the federation chain network; associating a second user having a transaction relationship with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair; judging whether a first transaction and a second transaction in the appointed transaction pair are executed correctly or not, wherein the first transaction is a process that the first user sends a first transaction object to the second user, and the second transaction is a process that the second user feeds back a second transaction object to the first user according to the first transaction object; if yes, judging whether a confirmation result of a third user in a alliance chain network for zero knowledge proof of the transaction relationship of the first transaction pair is received, wherein the third user is other users except the first user and the second user in the alliance chain network; and if so, changing the transaction states of the first transaction and the second transaction in the distributed ledger into confirmed states, and distributing the confirmed states in the alliance-link network.
The computer-readable storage medium supports the authority of the owner of the digital asset account to encrypt the transaction data written into the alliance chain network, other users of the alliance chain network can check the encrypted transaction data after obtaining authorization, and by setting the transaction pairs, when all transactions in the transaction pairs are completed and the transaction relationship in the transaction pairs is proved to be really stored according to zero knowledge, the transaction state in the transaction pairs can be confirmed and changed from 'to be confirmed' to 'confirmed', so that the privacy and the safety of the transactions are improved.
In one embodiment, the step of receiving, by the processor, first transaction data written by a first user in a federation chain network includes: receiving data content written by the first user; splitting the data content written by the first user into a plurality of data particles according to the content of a preset task configuration file; respectively calling a preset encryption program to encrypt according to transaction objects respectively corresponding to the data particles, wherein the transaction objects correspond to the preset encryption program one by one; and combining the respectively encrypted data particles into the first transaction data according to the arrangement sequence before encryption.
In one embodiment, the step of associating, by the processor, a second user having a transaction relationship with the first user based on the first transaction data includes: acquiring a task association relation corresponding to the first transaction data according to a preset task configuration file; setting a first user and a second user in the task association relation corresponding to the first transaction data as the designated transaction pair; and setting the particle data corresponding to the first user and the second user in the appointed transaction pair as interface data for completing the corresponding task of the appointed transaction pair, so as to execute the corresponding task of the appointed transaction pair by calling the interface data.
In an embodiment, the step of determining whether a confirmation result of zero-knowledge proof of the transaction relationship of the first transaction pair is received from a third user in the alliance-link network includes: sending the transaction relation certification data corresponding to the first transaction and the second transaction to the third user; receiving a query result of the third user for querying the transaction relation certification data corresponding to the first transaction and the second transaction, and comparing the query result with the synchronous ciphertext corresponding to the first transaction and the second transaction to obtain a verification result; if the verification result is transaction relationship certification data corresponding to the first transaction and the second transaction and corresponds to the content of the synchronous ciphertext corresponding to the first transaction and the second transaction, determining that a confirmation result of a zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network is received, otherwise, not receiving the confirmation result of the zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network.
In one embodiment, the step of receiving, by the processor, first transaction data written by a first user in the alliance-link network is preceded by: judging whether each user applying for joining the alliance link network receives the authorization file or not; if so, associating nodes respectively corresponding to all users receiving the authorization file as the alliance chain network; and initializing a distributed account book in the alliance chain network according to the asset information of each user, wherein the initialized distributed account book comprises an account corresponding to each user and an account initial balance.
In one embodiment, the step of determining whether the first transaction and the second transaction in the designated transaction pair have been executed correctly by the processor includes: acquiring a transaction execution sequence of the first transaction and the second transaction according to the preset task configuration file; judging whether execution feedback corresponding to the first transaction and the second transaction is received in sequence or not according to the transaction execution sequence; if yes, judging whether each execution feedback is normal in the execution process and correct in the execution result; if yes, judging whether the first transaction and the second transaction in the appointed transaction pair are executed correctly or not, otherwise, not executing.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium provided herein and used in the examples may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (SSRSDRAM), Enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A method for managing a block chain account book is characterized by comprising the following steps:
receiving first transaction data written by a first user in a alliance chain network, wherein the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data;
storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed ledger of the federation chain network;
associating a second user having a transaction relationship with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair;
judging whether a first transaction and a second transaction in the appointed transaction pair are executed correctly or not, wherein the first transaction is a process that the first user sends a first transaction object to the second user, and the second transaction is a process that the second user feeds back a second transaction object to the first user according to the first transaction object;
if yes, judging whether a confirmation result of a third user in a alliance chain network for zero knowledge proof of the transaction relationship of the first transaction pair is received, wherein the third user is other users except the first user and the second user in the alliance chain network;
and if so, changing the transaction states of the first transaction and the second transaction in the distributed ledger into confirmed states, and distributing the confirmed states in the alliance-link network.
2. The method for managing a blockchain ledger of claim 1 wherein said step of receiving first transaction data written by a first user in a federation chain network comprises:
receiving data content written by the first user;
splitting the data content written by the first user into a plurality of data particles according to the content of a preset task configuration file;
respectively calling a preset encryption program to encrypt according to transaction objects respectively corresponding to the data particles, wherein the transaction objects correspond to the preset encryption program one by one;
and combining the respectively encrypted data particles into the first transaction data according to the arrangement sequence before encryption.
3. The method of managing a blockchain ledger of claim 1 wherein the step of associating a second user having a transactional relationship with the first user based on the first transaction data comprises:
acquiring a task association relation corresponding to the first transaction data according to a preset task configuration file;
setting a first user and a second user in the task association relation corresponding to the first transaction data as the designated transaction pair;
and setting the particle data corresponding to the first user and the second user in the appointed transaction pair as interface data for completing the corresponding task of the appointed transaction pair, so as to execute the corresponding task of the appointed transaction pair by calling the interface data.
4. The method for managing a blockchain ledger of claim 1 wherein said step of determining whether a confirmation of zero knowledge proof of transaction relationship of said first transaction pair is received from a third user in a federation chain network comprises:
sending the transaction relation certification data corresponding to the first transaction and the second transaction to the third user;
receiving a query result of the third user for querying the transaction relation certification data corresponding to the first transaction and the second transaction, and comparing the query result with the synchronous ciphertext corresponding to the first transaction and the second transaction to obtain a verification result;
if the verification result is transaction relationship certification data corresponding to the first transaction and the second transaction and corresponds to the content of the synchronous ciphertext corresponding to the first transaction and the second transaction, determining that a confirmation result of a zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network is received, otherwise, not receiving the confirmation result of the zero knowledge certification of the third user for the transaction relationship of the first transaction pair in the alliance chain network.
5. The method for managing a blockchain ledger of claim 1 wherein the step of receiving first transaction data written by a first user in a federation chain network is preceded by:
judging whether each user applying for joining the alliance link network receives the authorization file or not;
if so, associating nodes respectively corresponding to all users receiving the authorization file as the alliance chain network;
and initializing a distributed account book in the alliance chain network according to the asset information of each user, wherein the initialized distributed account book comprises an account corresponding to each user and an account initial balance.
6. The method of claim 1, wherein the step of determining whether the first transaction and the second transaction in the designated transaction pair have been properly executed comprises:
acquiring a transaction execution sequence of the first transaction and the second transaction according to the preset task configuration file;
judging whether execution feedback corresponding to the first transaction and the second transaction is received in sequence or not according to the transaction execution sequence;
if yes, judging whether each execution feedback is normal in the execution process and correct in the execution result;
if yes, judging whether the first transaction and the second transaction in the appointed transaction pair are executed correctly or not, otherwise, not executing.
7. A management device of a block chain account book is characterized by comprising:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving first transaction data written by a first user in a alliance chain network, and the first transaction data carries a synchronous ciphertext encrypted by the first user on the first transaction data;
the storage module is used for storing the first transaction data and the synchronous ciphertext of the first transaction data in a distributed account book of the alliance chain network;
the first association module is used for associating a second user with a transaction relation with the first user according to the first transaction data, wherein the second user and the first user are associated to be a designated transaction pair;
a first judging module, configured to judge whether a first transaction and a second transaction in the designated transaction pair are both executed correctly, where the first transaction is a process in which the first user sends a first transaction object to the second user, and the second transaction is a process in which the second user feeds back a second transaction object to the first user according to the first transaction object;
a second determining module, configured to determine whether a confirmation result of a zero knowledge proof of a transaction relationship of a first transaction pair is received from a third user in a federation chain network if all the first and second users have been correctly executed, where the third user is another user in the federation chain network except the first user and the second user;
and the issuing module is used for changing the transaction states of the first transaction and the second transaction in the distributed account book into confirmed states and issuing the confirmed states into the alliance chain network if a confirmation result of zero knowledge proof of the transaction relationship of the first transaction pair by a third user in the alliance chain network is received.
8. The apparatus for managing a blockchain ledger of claim 7 wherein said receiving module comprises:
a receiving unit, configured to receive data content written by the first user;
the splitting unit is used for splitting the data content written by the first user into a plurality of data particles according to the content of a preset task configuration file;
the encryption unit is used for respectively calling a preset encryption program to encrypt according to transaction objects respectively corresponding to the data particles, wherein the transaction objects correspond to the preset encryption program one by one;
and the combination unit is used for combining the encrypted data particles into the first transaction data according to the arrangement sequence before encryption.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010621782.6A CN111783151A (en) | 2020-06-30 | 2020-06-30 | Management method and device of block chain account book and computer equipment |
| PCT/CN2021/097547 WO2022001549A1 (en) | 2020-06-30 | 2021-05-31 | Blockchain ledger management method and apparatus, and computer device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010621782.6A CN111783151A (en) | 2020-06-30 | 2020-06-30 | Management method and device of block chain account book and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111783151A true CN111783151A (en) | 2020-10-16 |
Family
ID=72760559
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010621782.6A Pending CN111783151A (en) | 2020-06-30 | 2020-06-30 | Management method and device of block chain account book and computer equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111783151A (en) |
| WO (1) | WO2022001549A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377768A (en) * | 2021-06-02 | 2021-09-10 | 浙江数秦科技有限公司 | Distributed account book access method based on alliance chain |
| WO2022001549A1 (en) * | 2020-06-30 | 2022-01-06 | 平安科技（深圳）有限公司 | Blockchain ledger management method and apparatus, and computer device |
| WO2022089237A1 (en) * | 2020-10-29 | 2022-05-05 | 深圳壹账通智能科技有限公司 | Blockchain-based value verification method and apparatus, computer device and medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106549749A (en) * | 2016-12-06 | 2017-03-29 | 杭州趣链科技有限公司 | A kind of block chain method for secret protection encrypted based on additive homomorphism |
| CN108764874A (en) * | 2018-05-17 | 2018-11-06 | 深圳前海微众银行股份有限公司 | Anonymous refund method, system and storage medium based on block chain |
| CN109242485A (en) * | 2018-08-13 | 2019-01-18 | 阿里巴巴集团控股有限公司 | Block chain method of commerce and device, electronic equipment |
| CN110264193A (en) * | 2019-05-20 | 2019-09-20 | 阿里巴巴集团控股有限公司 | In conjunction with the receipt storage method and node of user type and type of transaction |
| CN111159308A (en) * | 2020-04-02 | 2020-05-15 | 支付宝(杭州)信息技术有限公司 | Transaction record sharing method and device based on block chain network and electronic equipment |
| CN111191280A (en) * | 2019-12-24 | 2020-05-22 | 远光软件股份有限公司 | Block chain transaction method based on encrypted data, electronic equipment and storage medium |
| CN111191292A (en) * | 2019-12-16 | 2020-05-22 | 平安壹钱包电子商务有限公司 | Accounting method, accounting device, accounting system and computer-readable storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756582B (en) * | 2019-03-15 | 2022-08-12 | 腾讯科技（深圳）有限公司 | Information recording method, device, node and storage medium in block chain network |
| US10652019B1 (en) * | 2019-08-28 | 2020-05-12 | Qed-It Systems Ltd. | Atomic swap using zero-knowledge proofs, and applications thereof |
| CN110633309A (en) * | 2019-08-30 | 2019-12-31 | 阿里巴巴集团控股有限公司 | Block chain transaction processing method and device |
| CN111783151A (en) * | 2020-06-30 | 2020-10-16 | 平安科技（深圳）有限公司 | Management method and device of block chain account book and computer equipment |
-
2020
- 2020-06-30 CN CN202010621782.6A patent/CN111783151A/en active Pending
-
2021
- 2021-05-31 WO PCT/CN2021/097547 patent/WO2022001549A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106549749A (en) * | 2016-12-06 | 2017-03-29 | 杭州趣链科技有限公司 | A kind of block chain method for secret protection encrypted based on additive homomorphism |
| CN108764874A (en) * | 2018-05-17 | 2018-11-06 | 深圳前海微众银行股份有限公司 | Anonymous refund method, system and storage medium based on block chain |
| CN109242485A (en) * | 2018-08-13 | 2019-01-18 | 阿里巴巴集团控股有限公司 | Block chain method of commerce and device, electronic equipment |
| CN110264193A (en) * | 2019-05-20 | 2019-09-20 | 阿里巴巴集团控股有限公司 | In conjunction with the receipt storage method and node of user type and type of transaction |
| CN111191292A (en) * | 2019-12-16 | 2020-05-22 | 平安壹钱包电子商务有限公司 | Accounting method, accounting device, accounting system and computer-readable storage medium |
| CN111191280A (en) * | 2019-12-24 | 2020-05-22 | 远光软件股份有限公司 | Block chain transaction method based on encrypted data, electronic equipment and storage medium |
| CN111159308A (en) * | 2020-04-02 | 2020-05-15 | 支付宝(杭州)信息技术有限公司 | Transaction record sharing method and device based on block chain network and electronic equipment |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022001549A1 (en) * | 2020-06-30 | 2022-01-06 | 平安科技（深圳）有限公司 | Blockchain ledger management method and apparatus, and computer device |
| WO2022089237A1 (en) * | 2020-10-29 | 2022-05-05 | 深圳壹账通智能科技有限公司 | Blockchain-based value verification method and apparatus, computer device and medium |
| CN113377768A (en) * | 2021-06-02 | 2021-09-10 | 浙江数秦科技有限公司 | Distributed account book access method based on alliance chain |
| CN113377768B (en) * | 2021-06-02 | 2022-07-15 | 浙江数秦科技有限公司 | Distributed account book access method based on alliance chain |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022001549A1 (en) | 2022-01-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11792017B2 (en) | Systems and methods of secure provenance for distributed transaction databases | |
| CN111144862B (en) | Method, device, equipment and storage medium for realizing digital currency double-off-line payment | |
| CN108961030B (en) | Data processing method, apparatus, system, medium, and device for electronic ticket | |
| US20200334674A1 (en) | Systems and methods for blockchain administration | |
| JP5186790B2 (en) | Electronic money transaction method and electronic money system | |
| US20200145373A1 (en) | System for blockchain based domain name and ip number register | |
| CN111783151A (en) | Management method and device of block chain account book and computer equipment | |
| CN109165943A (en) | About the data processing method of electronic bill, device, storage medium and equipment | |
| CN112100635B (en) | Law enforcement return system and method based on intelligent contract and workflow architecture | |
| US11343074B2 (en) | Block-chain based identity system | |
| CN111915308A (en) | Transaction processing method of blockchain network and blockchain network | |
| CN115292684A (en) | Block chain based inquiry letter data processing method and block chain system | |
| CN110955699A (en) | Decentralized electronic academic certificate checking method and system | |
| CN109584028B (en) | Virtual resource allocation method and device | |
| CN112287311A (en) | Service implementation method and device based on block chain | |
| CN110727735B (en) | Method, device and equipment for cooperatively completing task event based on block chain technology | |
| JP6840319B1 (en) | Transaction information processing system | |
| CN114240588A (en) | Annuity plan reconciliation method, device, equipment and medium based on block chain | |
| CN111027992A (en) | Asset transaction method and device based on blockchain system and hardware equipment | |
| JP2005521970A (en) | Authentication and use of digital objects | |
| US20200104228A1 (en) | Asynchronous self-proving transactions | |
| CN111402037A (en) | User data processing method and device | |
| CN110599347A (en) | Bill processing method, device, computer readable storage medium and computer equipment | |
| CN109871678A (en) | Procurement business data ciphering method, device, equipment and storage medium | |
| KR20200065507A (en) | Systems for regulating authority of the private key in blockchain and method thereof |
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 |