WO2021017338A1 - Procédé de vérification à connaissance nulle multi-plateforme pour des données cryptées de fournisseurs de données multiples, et dispositif associé - Google Patents

Procédé de vérification à connaissance nulle multi-plateforme pour des données cryptées de fournisseurs de données multiples, et dispositif associé Download PDF

Info

Publication number
WO2021017338A1
WO2021017338A1 PCT/CN2019/120907 CN2019120907W WO2021017338A1 WO 2021017338 A1 WO2021017338 A1 WO 2021017338A1 CN 2019120907 W CN2019120907 W CN 2019120907W WO 2021017338 A1 WO2021017338 A1 WO 2021017338A1
Authority
WO
WIPO (PCT)
Prior art keywords
share
verification
transaction
ciphertext
ledger
Prior art date
Application number
PCT/CN2019/120907
Other languages
English (en)
Chinese (zh)
Inventor
陆陈一帆
来学嘉
贾牧
谢丹力
张鹏程
Original Assignee
深圳壹账通智能科技有限公司
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 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2021017338A1 publication Critical patent/WO2021017338A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • 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/388—Payment protocols; Details thereof using mutual authentication without cards, e.g. challenge-response
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/008—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols involving homomorphic encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0869—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving random numbers or seeds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • H04L9/3066—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Definitions

  • This application relates to the field of Internet technology, and in particular to a cross-platform zero-knowledge verification method and related equipment for encrypted data of multiple data providers.
  • Zero-Knowledge Proof (Zero-Knowledge Proof) was proposed by S. Gold wasser, S. Micali and C. Rackoff in the early 1980s. It refers to the ability of the prover to convince the verifier that a certain assertion is correct without providing any useful information to the verifier.
  • Zero-knowledge proof is essentially an agreement involving two or more parties, that is, a series of steps that two or more parties need to take to complete a task. The prover proves to the verifier and makes it believe that he knows or possesses a certain message, but the certification process cannot leak any information about the certified message to the verifier.
  • zero-knowledge proof technology there are more and more applications of zero-knowledge proof technology in fields involving data security.
  • the existing technology usually only supports encrypted data from one data provider (for example, Zero-knowledge verification of encrypted transaction data in a ledger.
  • the independent data storage system can be a blockchain network, distributed database, cloud server, distributed system and other third-party platforms
  • zero-knowledge verification of the four arithmetic operations of ciphertext across data storage which is not recognized by those skilled in the art
  • the four arithmetic operations of cross-platform ciphertext can be performed on the data of more than two independent data storage systems to achieve zero-knowledge verification.
  • This technology status makes it impossible for multiple data providers to verify each other's encrypted data. This problem is especially serious in the blockchain field, because it involves the existence of multiple data providers, and data providers are unwilling to share Data but hope to verify data with each other.
  • the inventor realized how to perform cross-platform ciphertext operations on the data of two or more independent data storage systems to achieve zero-knowledge verification, and to achieve mutual verification of their encrypted data by multiple data providers, thereby ensuring data security It has become an urgent technical problem to realize zero-knowledge verification of encrypted data of multiple data providers at the same time.
  • this application provides a cross-platform zero-knowledge verification method and related equipment for encrypted data of multiple data providers, the main purpose of which is to achieve zero-knowledge verification of encrypted data of multiple data providers while ensuring data security.
  • this application provides a cross-platform zero-knowledge verification method for encrypted data of multiple data providers.
  • the method is based on a transaction processing protocol that supports multi-party cross-platform transactions.
  • the transaction processing protocol includes a user terminal of a first user and a first user terminal.
  • the collaboration of the user terminals of the two users, or the transaction processing protocol includes the collaboration of the first independent data storage system and the second independent data storage system, and the cross-platform zero-knowledge verification method for encrypted data of multiple data providers includes:
  • the transaction processing protocol obtains the first account book of the first independent data storage system and the second account book of the second independent data storage system
  • the transaction parameters corresponding to the transaction request where the first user manages the first account book, and the second user manages the second account book, and the transaction parameters include the update share cipher text of the first account book, and the verification share password of the second account book
  • the transaction processing protocol performs a preset type legality verification on the transaction corresponding to the transaction parameter between the first ledger and the second ledger according to the acquired transaction parameter corresponding to the transaction request, and verifies the legality of the preset type After passing, update the account data of the first user in the first ledger with the updated share ciphertext corresponding to the first ledger.
  • the preset type of legality verification includes verifying whether the verification share corresponding to the transaction request is the same as that of the second ledger. The actual transaction shares are equal.
  • this application also provides a transaction processing device, which includes a memory and a processor, and the memory stores a transaction processing program corresponding to the transaction processing protocol supporting multi-party cross-platform transactions
  • the transaction processing program is executed by the processor, the steps of the cross-platform zero-knowledge verification method for encrypted data of multiple data providers can be realized.
  • this application also provides a transaction processing system, which includes:
  • the obtaining module is used to obtain the first account book and the second independent data storage of the first independent data storage system by the transaction processing protocol after the user terminal of the first user initiates a transaction request to the first account book of the first independent data storage system
  • the transaction parameters of the second ledger of the system corresponding to the transaction request, where the first user manages the first ledger, and the second user manages the second ledger, and the transaction parameters include the updated share ciphertext of the first ledger, and the second ledger
  • the update module is used for the transaction processing protocol to perform a preset type legality verification on the transaction corresponding to the transaction parameter between the first ledger and the second ledger according to the acquired transaction parameter corresponding to the transaction request, and to verify the validity of the transaction in advance
  • the account data of the first user in the first ledger is updated with the updated share cipher text corresponding to the first ledger.
  • the preset type legality verification includes verifying whether the verification share corresponding to the transaction request is It is equal to the actual transaction share of the second ledger.
  • the present application also provides a computer-readable storage medium in which computer instructions are stored.
  • the computer instructions When the computer instructions are executed on a computer, the computer can execute the above-mentioned multiple data.
  • the cross-platform zero-knowledge verification method, transaction processing device and computer storage medium for multi-data provider encrypted data proposed in this application perform cross-platform ciphertext four arithmetic operations on the data of two or more independent data storage systems to achieve zero-knowledge verification , Realize that multiple data providers mutually verify their encrypted data, and then realize zero-knowledge verification of encrypted data of multiple data providers while ensuring data security.
  • FIG. 1 is a flowchart of a preferred embodiment of a cross-platform zero-knowledge verification method for encrypted data of multiple data providers in this application;
  • Fig. 2 is a schematic diagram of a preferred embodiment of a transaction processing device according to the application.
  • Fig. 3 is a structural diagram of a preferred embodiment of a transaction processing device according to the application.
  • FIG. 4 is a schematic diagram of a preferred embodiment of the user terminal of the first user in FIG. 3;
  • Fig. 5 is a schematic diagram of a preferred embodiment of the user terminal of the second user in Fig. 3.
  • This application provides a cross-platform zero-knowledge verification method for encrypted data of multiple data providers.
  • FIG. 1 a flowchart of a preferred embodiment of a cross-platform zero-knowledge verification method for encrypted data of multiple data providers according to this application.
  • the method is based on a transaction processing protocol that supports multi-party cross-platform transactions, and the transaction processing protocol includes the user terminal of the first user and the user terminal of the second user.
  • the collaboration of the user terminal, or the transaction processing protocol includes the collaboration of the first independent data storage system and the second independent data storage system, the method includes:
  • Step S1 After the user terminal of the first user initiates a transaction request to the first account book of the first independent data storage system, the transaction processing protocol obtains the first account book of the first independent data storage system and the second independent data storage system.
  • Step S2 The transaction processing protocol performs a preset type legality verification on the transaction corresponding to the transaction parameter between the first ledger and the second ledger according to the acquired transaction parameter corresponding to the transaction request, and confirms the validity of the preset type
  • the account data of the first user in the first ledger is updated with the updated share ciphertext corresponding to the first ledger.
  • the preset type of legality verification includes verifying whether the verification share corresponding to the transaction request is the same as the first account. The actual transaction shares of the two ledgers are equal.
  • the above independent data storage system refers to third-party platforms such as blockchain networks, distributed databases, cloud servers, and distributed systems.
  • h g ⁇ n in the operation of, where g is the basis. Due to the complexity of the discrete logarithm problem, it is difficult to calculate the value of the integer n when h and g are known. Therefore, the calculation environment involved in this application is based on calculations on an elliptic curve. In an elliptic curve, the basis is a point, not a number.
  • the transaction processing protocol includes the cooperation of the user terminal of the first user and the user terminal of the second user.
  • the transaction parameters corresponding to the transaction request include the updated share ciphertext tz1 corresponding to the first ledger; the uncorrected and verified share ciphertext psm, the verified share ciphertext ps, the share comparison verification key p_sk, and the correction corresponding to the second ledger.
  • T0 Any user terminal receives the exchange rate and exchange rate key corresponding to the first account book, and uses the received exchange rate and exchange rate key to obtain the exchange rate ciphertext using the first formula.
  • the above exchange rate can be agreed in advance, can be determined during the transaction, or can be a parameter from a third party; the above exchange rate cipher text can be the first account of the first independent data storage system.
  • the user unilaterally determines and enters the first independent data storage system by the user terminal of the first user, or it may be the second user of the second account of the second independent data storage system negotiated with the first user and entered by the first user.
  • a trusted third party can also enter the first independent data storage system.
  • the first user or a third party generates the exchange rate, encrypts the exchange rate and stores it in the first independent data storage system that stores the first ledger. It can also be stored in any applicable and available to third parties. Independent data storage system. If the exchange rate is generated by a third party and encrypted and stored in the first independent data storage system, the third party needs to pass the key to the user terminal of the first user.
  • the above-mentioned first formula may be the Pedersen Commitment Encryption Algorithm formula.
  • T1 The user terminal of the first user receives and responds to the first ledger update transaction request initiated by the first user, and generates the update share key corresponding to the first ledger, and the update share of the first ledger corresponding to the update transaction request and generated The updated share key corresponding to the first ledger is used to generate the updated share ciphertext corresponding to the first ledger.
  • the aforementioned first ledger update transaction request is a ledger update request corresponding to a transaction
  • the update share ciphertext corresponding to the first ledger is the transaction share ciphertext corresponding to the transaction.
  • the updated share ciphertext tz1 of the first ledger can be created through the second formula.
  • T2 The user terminal of the first user updates the share, exchange rate, exchange rate key, and update share key according to the first account book, and calculates the updated share cipher text of the first account book corresponding to the verification share cipher text sum of the second account book transaction Verify the verification share key corresponding to the share ciphertext, and send the calculated verification share ciphertext and the verification share key to the user terminal of the second user of the second account of the second independent data storage system, where The first account book and the second account book respectively represent two different business data accounts.
  • the first independent data storage system may also calculate the verification share corresponding to the second ledger based on the update share and exchange rate of the first ledger, and send the calculated verification share to the second independent data storage system.
  • the second user of the ledger may also calculate the verification share corresponding to the second ledger based on the update share and exchange rate of the first ledger, and send the calculated verification share to the second independent data storage system. The second user of the ledger.
  • both the first independent data storage system and the second independent data storage system are pre-created with 3 bases, namely g, h, and i.
  • g is a public parameter
  • h and i are set by a trusted third party or multiple trusted third parties collaboratively and uploaded to the first independent data storage system and the second independent data storage system.
  • the user terminal of the first user can calculate the transaction share ciphertext of the second ledger corresponding to the first ledger transaction (that is, the verification share ciphertext of the second ledger), and send the verification share ciphertext to the second user ,
  • the verification share ciphertext and the corresponding actual transaction share actually carried out in the second ledger should be the same, but the key used in the ciphertext is different. If the two encryption shares are equal, then the second user can create A proof to prove that the ciphertext share of the second ledger transaction share calculated by the first user is equal to the corresponding ciphertext share of the second ledger transaction share.
  • the user terminal of the first user may send the calculated verification share ciphertext ps and verification share key s of the second ledger to the second user, and the second user compares the verification of the second ledger Whether the verification share p in the share ciphertext ps is equal to the actual transaction share t2 of the second ledger. If it is equal to, it means the verification is successful.
  • the second user sends the verification signature p_sig of the successful share comparison to the first user.
  • the verification share ciphertext ps of the second account book can be calculated by the third formula, and the above third formula can be:
  • the user terminal of the first user sends the verification share ciphertext ps, verification share key s, and the actual transaction share account address t2_address to be compared to the second independent data storage system based on the first independent data storage system.
  • the user terminal of the second user of the ledger can also calculate the verification share p based on the first independent data storage system and send it to the user terminal of the second user of the second account of the second independent data storage system.
  • T3 The user terminal of the first user calculates the correction parameter private key i_sk. Any third party can be used to prove that the encrypted shares of the verified share ciphertext ps and the uncorrected verified share ciphertext psm are the same.
  • the function of the correction parameter private key i_sk is: for a third party to verify that the verification share ciphertext ps is (and only) the uncorrected verification share ciphertext psm after removing the i base point parameter (the two parameters Encryption shares are equal).
  • the first user obtains the correction parameter private key i_sk based on the following fourth formula, and uses it as the private key to digitally sign the verification share ciphertext ps to obtain the corresponding correction parameter signature i_sig.
  • any third party can verify the verification share ciphertext ps and the uncorrected verification share ciphertext through the signature i_sig of the correction parameter and the correction parameter public key i_pk obtained based on the fifth formula below Whether the share of psm encryption is the same.
  • rz1 represents the value of the correction parameter private key i_sk. If the user terminal of the first user knows the value of rz1, it can be used to generate the signature i_sig of the correction parameter. Any third party can use the above fifth formula to calculate the calibration parameter public key i_pk to verify the signature i_sig of the calibration parameter.
  • T4 After the user terminal of the second user receives the transaction share verification request of the second ledger, it calculates the verification share p corresponding to the second ledger according to the verification share ciphertext ps and the corresponding verification share key s, and compares and calculates Whether the calculated verification share is equal to the actual transaction share t2 corresponding to the second ledger, if they are equal, the share comparison verification private key p_sk is calculated according to the verification share key s and the actual transaction share key z2, and will be generated
  • the share comparison verification key p_sk and the actual transaction share ciphertext tz2 are sent to the user terminal of the first user of the first independent data storage system.
  • the user terminal of the second user may calculate the verification share p corresponding to the second account book according to the verification share ciphertext ps and the corresponding verification share key s.
  • the user terminal of the second user can find the actual transaction share ciphertext tz2 according to the actual transaction share account address t2_address to be compared.
  • the user terminal of the second user may calculate the share comparison verification public key p_pk according to the verification share ciphertext ps key and the actual transaction share ciphertext tz2 based on the following sixth formula, and according to the verification The share key s and the actual transaction share key z2 are calculated based on the following seventh formula to obtain the share comparison verification private key p_sk:
  • (s–z2) represents the share comparison verification private key p_sk.
  • the discrete logarithm puzzle problem ensures that user two cannot calculate p_sk; similarly, the user terminal of the second user without the exchange rate cannot analyze the update share corresponding to the first ledger.
  • the share comparison verification private key p_sk After the share comparison verification private key p_sk is calculated, the share comparison verification private key p_sk and the actual transaction share ciphertext tz2 are sent to the user terminal of the first user.
  • the user terminal of the second user issues an instruction to the first independent data storage system, so that the first independent data storage system can check the actual transaction share account address t2_address and the actual transaction share
  • the ciphertext tz2 is permanently backed up and saved. Let the third party be able to find the t2_address and tz2 corresponding to the private key p_sk that provides the share comparison verification.
  • T5 The user terminal of the first user initiates a transaction request to the first data storage.
  • the first independent data storage system compares the first ledger with the first account based on the received transaction parameters. 2.
  • the transactions corresponding to the transaction parameters between the ledgers are verified for the validity of the preset type, and after the validity verification of the preset type is passed, the update share ciphertext corresponding to the first account is used to update the first user’s account in the first account.
  • Account data The user terminal of the first user initiates a transaction request to the first data storage.
  • the verification logic is executed on the smart contract.
  • the transaction parameters of the first preset type include: update share ciphertext tz1 corresponding to the first ledger, check share ciphertext ps corresponding to the second ledger transaction, and share ratio corresponding to the second ledger transaction.
  • the verification of the validity of the preset type includes: verifying whether the verification share of the second ledger corresponding to the transaction request is equal to the actual transaction share of the second ledger. Specifically:
  • the verification share ciphertext and the actual transaction share ciphertext, the share comparison verification public key is calculated, and calculated according to the seventh calculation formula, the verification share key and the actual transaction share key Share comparison verification private key;
  • the eighth formula it is checked whether the private key of the share comparison verification corresponds to the public key of the share comparison verification. If so, the verification share of the second ledger corresponding to the transaction request is equal to the actual transaction share of the second ledger, and the verification is judged to pass.
  • the eighth formula is:
  • the second user’s user terminal may provide The share comparison verification key p_sk corresponding to the share comparison verification public key p_pk.
  • the verification of the validity of the preset type further includes: verifying whether the unchecked verification share ciphertext is generated according to the updated share ciphertext and the exchange rate ciphertext. Specifically:
  • the tenth formula is: verify that the following two-way pairing equations are equal,
  • e(g,psm) e(g,g ⁇ et1*h ⁇ (ez1+rt1)*i ⁇ rz1)
  • e(tz1,er) e(g ⁇ t1*h ⁇ z1, g ⁇ e*h ⁇ r)
  • the first independent data storage system can update the updated share ciphertext tz1 corresponding to the first account book to the first user account on the first account book through the following eleventh formula.
  • the first user account balance ciphertext is ax1
  • the eleventh formula is:
  • the transaction parameters of the preset type are also recorded in the first independent data storage. Any third party can verify the legality of the first ledger transaction through the preset type of transaction parameters.
  • T6 Any third-party user terminal can verify the legality of the first ledger transaction at any time through the transaction parameters of the second preset type.
  • the transaction parameters include the second preset type transaction parameters stored in the first data and the actual transaction share ciphertext tz2 stored in the second data.
  • the verification steps include:
  • the first independent data storage system After receiving the second preset type transaction parameter acquisition request sent by the user terminal of the third party, the first independent data storage system sends the stored second preset type transaction parameter corresponding to the acquisition request to the third party ;
  • the second independent data storage system After the second independent data storage system receives the request for obtaining the actual transaction share ciphertext tz2 with the actual transaction share account address t2_address of the second ledger from the user terminal of the third ledger, it will transfer the actual transaction share account of the second ledger
  • the actual transaction share ciphertext tz2 of the address is sent to the user terminal of the third party;
  • the third-party user terminal verifies the accuracy of the preset type according to the acquired ciphertext of the actual transaction share and the second preset type transaction parameter corresponding to the acquisition request.
  • the second preset type of transaction parameters include: exchange rate cipher text er, update share cipher text tz1, verification share cipher text ps, correction parameter public key i_pk, correction parameter signature i_sig, share comparison Verification key p_sk.
  • the preset type accuracy verification includes: verifying whether the verification share ciphertext ps is generated according to the corresponding update share ciphertext tz1 and the exchange rate ciphertext er of the first ledger; verifying that the verification share p is equal to the actual transaction share t2 of the second ledger .
  • the transaction parameters further include the exchange rate ciphertext corresponding to the transaction request, the unchecked verification share ciphertext, and the updated share ciphertext of the first ledger, and the preset type of legality verification further includes:
  • FIG. 2 is a schematic diagram of a preferred embodiment of a transaction processing device of this application.
  • the transaction processing device 1 is applicable to the cross-platform zero-knowledge verification method for encrypted data of multiple data providers.
  • the transaction processing device 1 includes a memory 11, a processor 12, and a network interface 13.
  • the memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), magnetic memory, magnetic disk, optical disk, etc.
  • the memory 11 may be an internal storage unit of the transaction processing device 1 in some embodiments, such as a hard disk of the transaction processing device 1.
  • the memory 11 may also be an external storage device of the transaction processing device 1, for example, a plug-in hard disk, a smart media card (SMC), and a secure digital ( Secure Digital, SD card, Flash Card, etc.
  • the memory 11 may also include both an internal storage unit of the transaction processing apparatus 1 and an external storage device.
  • the memory 11 can be used not only to store application software and various data installed in the transaction processing device 1, for example, the transaction processing program 10 corresponding to the transaction processing protocol supporting multi-party cross-platform transactions, etc., but also to temporarily Store the data that has been output or will be output.
  • the processor 12 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip, and is used to run the program code or processing stored in the memory 11 Data, for example, the transaction processing program 10 corresponding to the transaction processing protocol supporting multi-party cross-platform transactions.
  • CPU central processing unit
  • controller microcontroller
  • microprocessor microprocessor
  • the network interface 13 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface), and is usually used to establish a communication connection between the transaction processing device 1 and other electronic equipment, such as meeting record managers and meeting Record the terminal used by the inquirer.
  • the components 11-13 of the transaction processing device 1 communicate with each other via a communication bus.
  • FIG 2 only shows the transaction processing device 1 with components 11-13.
  • FIG 4 does not constitute a limitation on the transaction processing device 1, and may include less Or more components, or a combination of certain components, or different component arrangements.
  • FIG. 3 is a structural diagram of a preferred embodiment of a transaction processing apparatus according to this application.
  • the transaction processing device 1 includes: a user terminal 2 of a first user and a user terminal 3 of a second user.
  • the first user manages the first account book through the user terminal 2 of the first user
  • the second user manages the second account book through the user terminal 3 of the second user.
  • the first book is stored in the first independent data storage system
  • the second account book is stored in the first independent data storage system.
  • the data is stored in a second independent data storage system.
  • the user terminal 2 of the first user and the user terminal 3 of the second user perform collaborative operations based on a transaction processing protocol supporting multi-party cross-platform transactions.
  • FIG. 4 is a schematic diagram of a preferred embodiment of the user terminal of the first user in FIG. 3.
  • the user terminal 2 of the first user may be a terminal device with a data processing function, such as a server, a smart phone, a tablet computer, a portable computer, a desktop computer, and the like.
  • a data processing function such as a server, a smart phone, a tablet computer, a portable computer, a desktop computer, and the like.
  • the user terminal 2 of the first user includes a first memory 21, a second processor 22, and a first network interface 23.
  • the first memory 21 stores a first transaction processing program 20.
  • the first memory 21 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), magnetic memory, magnetic disk, and optical disk. Wait.
  • the first storage 21 may be an internal storage unit of the user terminal 2 of the first user, for example, a hard disk of the user terminal 2 of the first user.
  • the first memory 21 may also be an external storage device of the user terminal 2 of the first user, such as a plug-in hard disk equipped on the user terminal 2 of the first user, and a smart memory card (Smart Media Card, SMC), Secure Digital (SD) card, Flash Card, etc.
  • the first memory 21 may also include both an internal storage unit of the user terminal 2 of the first user and an external storage device.
  • the first memory 21 can be used not only to store application software and various data installed in the user terminal 2 of the first user, for example, the first transaction processing program 20, etc., but also to temporarily store output or to be output. data.
  • the first processor 22 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments, and is used to run data stored in the first memory 21 Program code or processing data, for example, the first transaction processing program 20 and so on.
  • CPU central processing unit
  • controller microcontroller
  • microprocessor or other data processing chip in some embodiments, and is used to run data stored in the first memory 21 Program code or processing data, for example, the first transaction processing program 20 and so on.
  • the first network interface 23 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface), and is usually used to establish a communication connection between the user terminal 2 of the first user and other electronic devices, for example, 2.
  • the user terminal of the user The components 21-23 of the user terminal 2 of the first user communicate with each other via a communication bus.
  • Fig. 4 only shows the user terminal 2 of the first user with components 21-23. Those skilled in the art can understand that the structure shown in Fig. 4 does not constitute a limitation on the user terminal 2 of the first user. Including fewer or more components than shown, or combining certain components, or different component arrangements.
  • the user terminal 2 of the first user may also include a user interface
  • the user interface may include a display (Display), an input unit such as a keyboard (Keyboard), and the optional user interface may also include a standard wired interface and a wireless interface.
  • Display Display
  • Keyboard an input unit
  • the optional user interface may also include a standard wired interface and a wireless interface.
  • the display may be an LED display, a liquid crystal display, a touch liquid crystal display, an organic light-emitting diode (OLED) touch device, and the like.
  • the display may also be called a display screen or a display unit, which is used to display the information processed in the user terminal 2 of the first user and to display a visualized user interface.
  • FIG. 5 it is a schematic diagram of a preferred embodiment of the user terminal of the second user in FIG. 3.
  • the user terminal 3 of the second user includes a second memory 31 and a second processor 32, and a second transaction processing program 30 is stored in the second memory 31.
  • the user terminal 3 of the second user may be a terminal device with a data processing function, such as a server, a smart phone, a tablet computer, a portable computer, a desktop computer, and the like.
  • a data processing function such as a server, a smart phone, a tablet computer, a portable computer, a desktop computer, and the like.
  • the user terminal 3 of the second user includes a second memory 31, a second processor 22, and a second network interface 33.
  • the second memory 31 stores a second transaction processing program 30.
  • the second memory 31 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), magnetic memory, magnetic disk, and optical disk. Wait.
  • the second memory 31 may be an internal storage unit of the user terminal 3 of the second user, for example, a hard disk of the user terminal 3 of the second user.
  • the second memory 31 may also be an external storage device of the user terminal 3 of the second user, for example, a plug-in hard disk equipped on the user terminal 3 of the second user, and a smart memory card (Smart Media Card, SMC), Secure Digital (SD) card, Flash Card, etc.
  • the second memory 31 may also include both an internal storage unit of the user terminal 3 of the second user and an external storage device.
  • the second memory 31 can not only be used to store application software and various data installed in the user terminal 3 of the second user, for example, the second transaction processing program 30, etc., but also can be used to temporarily store output or to be output. data.
  • the second processor 32 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip, and is used to run the data stored in the second memory 31 Program code or processing data, for example, the second transaction processing program 30 and so on.
  • CPU central processing unit
  • controller microcontroller
  • microprocessor microprocessor
  • the second network interface 23 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface), and is usually used to establish a communication connection between the user terminal 3 of the second user and other electronic devices, for example, the first A user's user terminal.
  • the components 31-33 of the user terminal 3 of the second user communicate with each other via a communication bus.
  • FIG. 5 only shows the user terminal 3 of the second user with the components 31-33. Those skilled in the art can understand that the structure shown in FIG. 5 does not constitute a limitation on the user terminal 3 of the second user. Including fewer or more components than shown, or combining certain components, or different component arrangements.
  • the user terminal 3 of the second user may also include a user interface
  • the user interface may include a display (Display), an input unit such as a keyboard (Keyboard), and the optional user interface may also include a standard wired interface and a wireless interface.
  • Display Display
  • Keyboard an input unit
  • the optional user interface may also include a standard wired interface and a wireless interface.
  • the display may be an LED display, a liquid crystal display, a touch liquid crystal display, an organic light-emitting diode (OLED) touch device, and the like.
  • the display may also be called a display screen or a display unit, which is used to display the information processed in the user terminal 3 of the second user and to display a visualized user interface.
  • the embodiment of the present application also provides a transaction processing system suitable for a cross-platform zero-knowledge verification method for encrypted data of multiple data providers.
  • the transaction processing system includes:
  • the obtaining module is used to obtain the first account book and the second independent data storage of the first independent data storage system by the transaction processing protocol after the user terminal of the first user initiates a transaction request to the first account book of the first independent data storage system
  • the transaction parameters of the second ledger of the system corresponding to the transaction request, where the first user manages the first ledger, and the second user manages the second ledger.
  • the transaction parameters include the updated share ciphertext of the first ledger, and the correction of the second ledger.
  • the update module is used for the transaction processing protocol to verify the validity of the preset type of the transaction corresponding to the transaction parameter between the first ledger and the second ledger according to the acquired transaction parameter corresponding to the transaction request, and to verify the validity of the preset type
  • the preset type of legality verification includes verifying whether the verification share corresponding to the transaction request is the same as the second ledger. The actual transaction share is equal.
  • update module is specifically used for:
  • the share comparison verification public key is calculated, and the share comparison verification private key is calculated according to the verification share key and the actual transaction share key;
  • the aforementioned update module includes:
  • the verification unit is configured to verify whether the unchecked share ciphertext is generated according to the updated share ciphertext and the exchange rate ciphertext.
  • the foregoing transaction parameters further include: a correction parameter signature, a correction parameter public key, and a correction parameter private key
  • the verification unit is specifically used for:
  • the formula for verifying whether the uncorrected share ciphertext is generated based on the updated share ciphertext and the exchange rate ciphertext includes:
  • psm represents the unchecked verification share cipher text
  • tz1 represents the updated share cipher text
  • er represents the exchange rate cipher text
  • ps represents the verification share cipher text
  • i_pk represents the correction parameter public key
  • rz1 represents the value of the correction parameter private key i_sk.
  • the specific implementation of the transaction processing system of the present application is substantially the same as the specific implementation of the cross-platform zero-knowledge verification method for encrypted data of multiple data providers, and will not be repeated here.
  • the embodiment of the present application also proposes a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium.
  • the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on the computer, the computer executes the following steps:
  • the transaction processing protocol obtains the first account book of the first independent data storage system and the second account book of the second independent data storage system
  • the transaction parameters corresponding to the transaction request where the first user manages the first ledger, the second user manages the second ledger, and the transaction parameters include the updated share ciphertext of the first ledger, the verification share ciphertext of the second ledger, The actual transaction share ciphertext, and the exchange rate ciphertext between the first account book and the second account book, and the unchecked share ciphertext;
  • the transaction processing protocol performs a preset type legality verification on the transactions corresponding to the transaction parameters between the first ledger and the second ledger according to the acquired transaction parameters corresponding to the transaction request, and after the preset type legality verification is passed , Use the updated share ciphertext corresponding to the first ledger to update the account data of the first user in the first ledger, the preset type of legality verification includes verifying whether the verification share corresponding to the transaction request is equal to the actual transaction share of the second ledger .
  • the specific implementation of the computer-readable storage medium of the present application is substantially the same as the specific implementation of the cross-platform zero-knowledge verification method for encrypted data of multiple data providers, and will not be repeated here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Algebra (AREA)
  • Mathematical Analysis (AREA)
  • Mathematical Optimization (AREA)
  • Mathematical Physics (AREA)
  • Pure & Applied Mathematics (AREA)
  • Computing Systems (AREA)
  • Storage Device Security (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un procédé de vérification à connaissance nulle multi-plateforme pour des données cryptées de fournisseurs de données multiples, ainsi qu'un dispositif associé. Le procédé selon l'invention consiste : après qu'un terminal d'un premier utilisateur a initié une demande de transaction sur un premier livre comptable d'un premier système de stockage de données indépendant, à acquérir par le protocole de traitement de transaction des paramètres de transaction, correspondant à la demande de transaction, du premier livre comptable du premier système de stockage de données indépendant et d'un deuxième livre comptable d'un deuxième système de stockage de données indépendant ; selon les paramètres de transaction acquis correspondant à la demande de transaction, à réaliser une vérification de validité de type prédéfini sur une transaction correspondant aux paramètres de transaction entre le premier et le deuxième livre comptable et, après le succès de la vérification de validité de type prédéfinie, à mettre à jour des données de compte du premier utilisateur dans le premier livre comptable au moyen d'un cryptogramme de partage mis à jour correspondant au premier livre comptable. La présente invention réalise une vérification à connaissance nulle de données de cryptage d'une pluralité de fournisseurs de données, tout en assurant la sécurité des données.
PCT/CN2019/120907 2019-07-29 2019-11-26 Procédé de vérification à connaissance nulle multi-plateforme pour des données cryptées de fournisseurs de données multiples, et dispositif associé WO2021017338A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910691109.7A CN110505046B (zh) 2019-07-29 2019-07-29 多数据提供方加密数据跨平台零知识校验方法、装置及介质
CN201910691109.7 2019-07-29

Publications (1)

Publication Number Publication Date
WO2021017338A1 true WO2021017338A1 (fr) 2021-02-04

Family

ID=68587684

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/120907 WO2021017338A1 (fr) 2019-07-29 2019-11-26 Procédé de vérification à connaissance nulle multi-plateforme pour des données cryptées de fournisseurs de données multiples, et dispositif associé

Country Status (2)

Country Link
CN (1) CN110505046B (fr)
WO (1) WO2021017338A1 (fr)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111160909B (zh) * 2019-12-31 2024-01-16 深圳市迅雷网络技术有限公司 区块链供应链交易隐藏静态监管系统及方法
CN111079190A (zh) * 2019-12-31 2020-04-28 深圳市网心科技有限公司 区块链供应链交易隐藏动态监管系统及方法
CN111245626B (zh) * 2020-01-19 2021-05-18 平安科技（深圳）有限公司 零知识证明方法、装置及存储介质
CN111552736A (zh) * 2020-03-30 2020-08-18 深圳壹账通智能科技有限公司 加密数据对等关系比对方法、装置及存储介质
CN111628865B (zh) * 2020-04-23 2021-06-29 平安科技（深圳）有限公司 加密数据对等关系参数检验方法、装置及存储介质
CN111639347A (zh) * 2020-04-29 2020-09-08 深圳壹账通智能科技有限公司 电子仓单验证方法、装置、终端及存储介质
CN111340494B (zh) * 2020-05-15 2020-08-28 支付宝(杭州)信息技术有限公司 资产类型一致性证据生成、交易、交易验证方法及系统
CN111885056A (zh) * 2020-07-22 2020-11-03 北京金山云网络技术有限公司 基于区块链的零知识证明方法、装置及电子设备
CN111817859A (zh) * 2020-07-30 2020-10-23 深圳壹账通智能科技有限公司 基于零知识证明的数据共享方法、装置、设备及存储介质
CN111935146B (zh) * 2020-08-11 2022-08-26 北华航天工业学院 一种网络通讯安全防护系统及其防护方法
CN112116400A (zh) * 2020-09-28 2020-12-22 平安壹钱包电子商务有限公司 基于区块链的虚拟资源的互通方法、装置及相关设备
CN114844647B (zh) * 2022-04-21 2024-04-12 浪潮云信息技术股份公司 一种多中心的群签名密钥生成方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108335106A (zh) * 2018-01-24 2018-07-27 深圳壹账通智能科技有限公司 基于区块链的零知识多账本兑换转账方法、装置及存储介质
CN109102286A (zh) * 2018-08-02 2018-12-28 平安科技（深圳）有限公司 跨账本交易方法及装置
US20190034923A1 (en) * 2017-07-31 2019-01-31 Chronicled, Inc Secure and confidential custodial transaction system, method and device using zero-knowledge protocol
CN109756582A (zh) * 2019-03-15 2019-05-14 腾讯科技（深圳）有限公司 区块链网络中的信息记录方法、装置、节点及存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170132621A1 (en) * 2015-11-06 2017-05-11 SWFL, Inc., d/b/a "Filament" Systems and methods for autonomous device transacting
US11017387B2 (en) * 2016-03-24 2021-05-25 International Business Machines Corporation Cryptographically assured zero-knowledge cloud services for elemental transactions
CN107274184A (zh) * 2017-05-11 2017-10-20 上海点融信息科技有限责任公司 基于零知识证明的区块链数据处理
CN108021821A (zh) * 2017-11-28 2018-05-11 北京航空航天大学 多中心区块链交易隐私保护系统及方法
CN108241979B (zh) * 2017-12-20 2021-03-16 深圳壹账通智能科技有限公司 基于区块链的多账本转账方法、电子装置及可读存储介质
CN108288159A (zh) * 2018-03-07 2018-07-17 物数（上海）信息科技有限公司 基于多区块链的跨链交易方法、系统、设备及存储介质
CN109559223A (zh) * 2018-10-10 2019-04-02 远光软件股份有限公司 一种基于区块链技术的交易方法、装置及区块链网络
CN109558517B (zh) * 2018-10-24 2023-02-03 中山大学 一种基于区块链的多方安全选举系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190034923A1 (en) * 2017-07-31 2019-01-31 Chronicled, Inc Secure and confidential custodial transaction system, method and device using zero-knowledge protocol
CN108335106A (zh) * 2018-01-24 2018-07-27 深圳壹账通智能科技有限公司 基于区块链的零知识多账本兑换转账方法、装置及存储介质
CN109102286A (zh) * 2018-08-02 2018-12-28 平安科技（深圳）有限公司 跨账本交易方法及装置
CN109756582A (zh) * 2019-03-15 2019-05-14 腾讯科技（深圳）有限公司 区块链网络中的信息记录方法、装置、节点及存储介质

Also Published As

Publication number Publication date
CN110505046A (zh) 2019-11-26
CN110505046B (zh) 2020-11-24

Similar Documents

Publication Publication Date Title
WO2021017338A1 (fr) Procédé de vérification à connaissance nulle multi-plateforme pour des données cryptées de fournisseurs de données multiples, et dispositif associé
CN110224837B (zh) 基于分布式身份标识的零知识证明方法及终端
US10505949B2 (en) Blockchain-based system, and electronic apparatus and method in the system
WO2019144612A1 (fr) Procédé et appareil de transfert de devises entre livres de comptes multiples à divulgation nulle de connaissance fondés sur une chaîne de blocs, et support d'informations
CN109889497B (zh) 一种去信任的数据完整性验证方法
CN113569294B (zh) 一种零知识证明方法及装置、电子设备、存储介质
US20130326602A1 (en) Digital Signatures
CN111835526B (zh) 一种生成匿名凭证的方法及系统
WO2021143457A1 (fr) Procédé et appareil d'authentification d'identité sur la base d'un algorithme sm9, et dispositif informatique
CN111245626B (zh) 零知识证明方法、装置及存储介质
WO2021042737A1 (fr) Procédé et appareil de vérification de connaissance nulle pour des données chiffrées, et support
KR20120091618A (ko) 연쇄 해시에 의한 전자서명 시스템 및 방법
CN113901424A (zh) 一种数字身份属性的选择性披露方法和装置
WO2021196478A1 (fr) Procédé de comparaison de relation d'égalité de données de chiffrement, dispositif, appareil informatique et support de stockage
CN112385181B (zh) 用于证明公钥的可靠性的装置、方法及程序
CN114128213B (zh) 用于验证公钥的可靠性的装置、方法以及其程序
CN113792282A (zh) 身份数据验证方法、装置、计算机设备和存储介质
CN113112269A (zh) 多重签名方法、计算机设备和存储介质
WO2021212611A1 (fr) Procédé et appareil d'inspection de paramètre de relation pair à pair de données chiffrées, et dispositif et support de stockage
CN115499247B (zh) 基于零知识证明的属性凭证的验证方法及装置
TWI746235B (zh) 基於既有憑證換取新憑證之系統、方法及電腦可讀媒介
Zhang et al. Self-Certified Public Auditing for Data Integrity in Cloud Storage
WO2019216435A1 (fr) Dispositif et procédé destinés à certifier la fiabilité d'une clé publique, et programme associé
KR102245382B1 (ko) 블록체인 네트워크 기반의 가상 공통 아이디 서비스 방법 및 이를 이용한 서비스 제공 서버
JP2010197980A (ja) ソーシャルネット内の各ユーザの公開鍵の正当性を保証する認証局を設定する認証局設定装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19940027

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19940027

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05/08/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 19940027

Country of ref document: EP

Kind code of ref document: A1