WO2020119297A1 - Procédé et appareil de traitement d'événements sur la base d'une chaîne de blocs et dispositif électronique - Google Patents

Procédé et appareil de traitement d'événements sur la base d'une chaîne de blocs et dispositif électronique Download PDF

Info

Publication number
WO2020119297A1
WO2020119297A1 PCT/CN2019/113934 CN2019113934W WO2020119297A1 WO 2020119297 A1 WO2020119297 A1 WO 2020119297A1 CN 2019113934 W CN2019113934 W CN 2019113934W WO 2020119297 A1 WO2020119297 A1 WO 2020119297A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
blockchain
transactions
participant
event
Prior art date
Application number
PCT/CN2019/113934
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 WO2020119297A1 publication Critical patent/WO2020119297A1/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/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Definitions

  • One or more embodiments of this specification relate to the field of blockchain technology, and in particular, to a blockchain-based event processing method and device, and electronic equipment.
  • the participants of the event can generate a corresponding blockchain transaction for the event and submit the blockchain transaction to the blockchain so that the blockchain transaction can be executed by the blockchain node.
  • the blockchain transaction can be executed by the blockchain node.
  • one or more embodiments of this specification provide a blockchain-based event processing method and device, and electronic equipment
  • a blockchain-based event processing method which is applied to participants, and the method includes:
  • a blockchain-based event processing method is proposed, which is applied to blockchain nodes.
  • the method includes:
  • Receive a set transaction submitted by the participant to the blockchain the set transaction includes a number of candidate sub-transactions selected from the waiting queue maintained by the participant, the candidate sub-transaction corresponds to the participation of the participant event;
  • the aggregate transaction is executed to separately process the candidate sub-transactions in the aggregate transaction.
  • a blockchain-based event processing device which is applied to participants and includes:
  • An adding unit adding a corresponding alternative sub-transaction to the waiting queue maintained by the participant according to the events that the participant participates in;
  • the generating unit generates a corresponding set transaction based on several candidate sub-transactions selected from the waiting queue;
  • the submission unit submits the aggregate transaction to the blockchain, so that the alternative sub-transactions in the aggregate transaction are processed separately.
  • a blockchain-based event processing device which is applied to a blockchain node.
  • the device includes:
  • the receiving unit receives a set transaction submitted by the participant to the blockchain, and the set transaction includes several candidate sub-transactions selected from the waiting queue maintained by the participant, the candidate sub-transactions correspond to the participation Events in which the party is involved;
  • the execution unit executes the collective transaction to separately process the candidate sub-transactions in the collective transaction.
  • an electronic device including:
  • Memory for storing processor executable instructions
  • the processor implements the method described in the first aspect by running the executable instruction.
  • an electronic device including:
  • Memory for storing processor executable instructions
  • the processor executes the executable instruction to implement the method described in the second aspect above.
  • FIG. 1 is a flowchart of a blockchain-based event processing method provided by an exemplary embodiment.
  • FIG. 2 is a flowchart of another blockchain-based event processing method provided by an exemplary embodiment.
  • FIG. 3 is a schematic diagram of a scenario of cross-border remittance provided by an exemplary embodiment.
  • FIG. 4 is a schematic diagram of interaction in a cross-border remittance process according to an exemplary embodiment.
  • FIG. 5 is a schematic diagram of a blockchain transaction content based on a ciphertext value provided by an exemplary embodiment.
  • FIG. 6 is a schematic diagram of a block chain transaction content based on plain text values provided by an exemplary embodiment.
  • FIG. 7 is a schematic diagram of a statistical trigger situation provided by an exemplary embodiment.
  • FIG. 8 is a schematic structural diagram of an apparatus provided by an exemplary embodiment.
  • FIG. 9 is a block diagram of an event processing device based on a blockchain provided by an exemplary embodiment.
  • FIG. 10 is a schematic structural diagram of another device provided by an exemplary embodiment.
  • FIG. 11 is a block diagram of another blockchain-based event processing apparatus provided by an exemplary embodiment.
  • the steps of the corresponding method are not necessarily performed in the order shown and described in this specification.
  • the method may include more or fewer steps than described in this specification.
  • the single step described in this specification may be decomposed into multiple steps for description in other embodiments; and the multiple steps described in this specification may also be combined into a single step in other embodiments. description.
  • FIG. 1 is a flowchart of a blockchain-based event processing method provided by an exemplary embodiment. As shown in Fig. 1, this method is applied to participants and may include the following steps:
  • Step 102 Add a corresponding candidate sub-transaction to the waiting queue maintained by the participant according to the event in which the participant participates.
  • each participant corresponds to a participant.
  • the participant may be an individual, an enterprise, an organization, etc. This specification does not limit this.
  • the participating object has a corresponding digital identity, so that the electronic device carrying the digital identity is equivalent to being configured as a participant corresponding to the participating object.
  • the events in this specification may include any type and cover any scenario, such as voting, signing agreements, traffic distribution, transfers, cross-border remittance, etc.
  • This specification does not limit this.
  • the descriptive information may include information such as voting reasons and voting options
  • the trigger information submitted in the blockchain of each participating direction may include the selection result of the voting options, thereby triggering the completion of the voting operation.
  • the candidate sub-transaction contains description information of the event, and the description information is used to describe the situation of the related event, so that when the candidate sub-transaction is processed, the corresponding event can be implemented according to the description information.
  • the description information can characterize the execution logic of related events, the involved parties, the way to change the state parameters of the parties (such as increasing or decreasing the value of the state parameters), the amount of change, etc. Limit it.
  • the relevant content of the event can be communicated in advance by any participant in any way, and then any of the participants can draft the description information of the event, so that other participants of the event can respond to the View and confirm the content of the description information; of course, any one of the participants can also determine other participants of the event and other content in the description information without prior communication.
  • This manual does not limit this .
  • the description information of the event may be generated by any participant of the event and added as an alternative sub-transaction in the waiting queue maintained by the any participant. And, the any participant also shares the generated description information to other participants, so that the other participants can confirm the description information.
  • any participant can send the description information to other participants of the event through an off-chain channel.
  • Sending the description information to other participants in the event through the off-chain channel can achieve the efficient transmission of the description information.
  • the off-chain channel may be an encrypted channel or other form of secure channel established between the parties to the event to avoid information leakage.
  • any participant can submit a transaction to the blockchain and include the above description information in the transaction, so that the transaction can be sent to all the blockchain after consensus Blockchain node; and each participant of the event can be configured as a blockchain node in the blockchain, or each participant can have a corresponding blockchain node in the blockchain, so that each participant The party can obtain the above transaction and the description information it contains through the blockchain ledger maintained by itself or the corresponding blockchain node (the blockchain ledger contains the entire transaction data of the blockchain), so that the above description information is Synchronize to other parties in the event.
  • Step 104 Generate a corresponding set transaction based on several candidate sub-transactions selected from the waiting queue.
  • the set transaction may include multiple alternative sub-transactions, each of which corresponds to an event in which the above-mentioned parties participate, so that the set transaction is included after being submitted to the blockchain.
  • Multiple alternative sub-transactions can be processed in the blockchain, so that multiple events corresponding to these alternative sub-transactions are implemented. It can be seen that by including multiple alternative sub-transactions in the set transaction, these alternative sub-transactions are submitted to the blockchain in batches, which can reduce the number of transactions submitted to the blockchain without generating for each alternative sub-transaction A blockchain transaction helps reduce resource consumption and improve processing efficiency.
  • the candidate sub-transactions in the waiting queue may be selected to: Generate the corresponding aggregate transaction.
  • the alternative sub-transactions that already exist in the waiting queue may be selected periodically according to a preset duration to generate a corresponding set transaction; of course, the capacity of each set transaction may have a maximum limit, such that There is a corresponding maximum value for the number of candidate sub-transactions selected in the same period, and the excess can be postponed to the next period for selection.
  • alternative sub-transactions can also be selected through other preset rules, which are not limited in this specification.
  • the candidate sub-transactions in the waiting queue can be arranged in order according to the time of addition, and each candidate sub-transaction can be selected in sequence from front to back each time, so that the previously generated candidate sub-transactions can be selected preferentially .
  • the participants can also implement the order-independent selection operation on the alternative sub-transactions in the waiting queue according to the actual needs, such as the urgency of the event, the priority of the event, etc.; or, the waiting queue itself can follow the above-mentioned emergency Sort by degree, priority, etc., so that it can still be regarded as one by one.
  • the participants may add numbers to each merged transaction in the order of generation, so that each merged transaction is processed sequentially in the blockchain according to the size of the corresponding number.
  • the blockchain transaction needs to read the number included in the merger exchange; if the number is continuous with the number of the previously processed merger transaction, for example, the latest processed merger transaction number is 99, If the number of the merged transaction currently received is 100, the merged transaction with the number of 100 can be processed; if the numbers are not continuous, for example, the number of the latest merged transaction processed is 99, the current received merged transaction If the number is 101, the blockchain node needs to wait and give priority to the merge transaction with the number 100 before it can process the merge transaction with the number 101.
  • the state parameters of the participant may change, and the execution of subsequent transactions depends on the value of the state parameters after the execution of the previous transaction, so it is necessary to ensure that each merged transaction is The size is processed sequentially so that each merged transaction can be executed correctly.
  • Step 106 Submit the aggregate transaction to the blockchain, so that the alternative sub-transactions in the aggregate transaction are processed separately.
  • the candidate sub-transaction corresponding to the event includes multi-party trigger information for the event from all parties involved in the event; wherein, when the multi-party trigger information passes verification, the event The corresponding alternative sub-transaction is triggered to execute in the blockchain.
  • Multi-party trigger information represents the approval of all participants in the event for the description information and hopes to trigger the execution of the event.
  • the other participants can confirm the content of the description information, generate a signature on the description information through their own identity key, and return the signature to any participant
  • the multi-party trigger information can contain the description information and the signatures generated by each participant of the event; each signature belongs to the confirmation information provided by the corresponding participant, and if the cipher text value is used, the confirmation information will also contain the password Proof information for text values, which will be described in detail below.
  • the blockchain node can process the alternative sub-transactions submitted by any participant after the trigger information of multiple parties is verified.
  • the candidate sub-transaction corresponding to the event includes the single-party trigger information of the participant on the event; wherein, when all participants of the event submit to the blockchain When the unilateral trigger information of the event is all verified, the alternative sub-transaction corresponding to the event is triggered to execute in the blockchain.
  • the unilateral trigger information indicates that the corresponding participant confirms the description information of the event, hoping to trigger the execution of the event; and each participant of the event needs to submit the unilateral trigger information to the blockchain separately, so that the blockchain node is based on all participants Unilateral trigger information submitted separately to determine whether the event indicated by the corresponding alternative sub-exchange should be executed.
  • the above unilateral trigger information is submitted to the blockchain for verification by the blockchain nodes.
  • the unilateral trigger information can contain description information and the signature generated by the corresponding participant on the description information; the signature belongs to the confirmation information provided by the corresponding participant, and if the cipher text value is used, the confirmation information also contains the certification information, which will be described in detail below.
  • the description information of the event may include the amount of change
  • the event may be used to cause the state parameters correspondingly recorded on the blockchain by each participant to change according to the amount of change, such as increasing the amount of change. Value, decrease value, etc.
  • the corresponding state parameters may also be different according to the type of event or the difference in the scene.
  • the state parameter in the scenario of transfer or cross-border remittance can be the account balance of the participant
  • the state parameter in the scenario of traffic distribution can be the participant. This manual does not limit the amount of remaining flow.
  • the value of the state parameter corresponding to each participant and the amount of change may be a plain text value.
  • the blockchain nodes in the blockchain maintain a blockchain ledger, which records the full amount of transaction data, so that the blockchain node can learn the value of the state parameters corresponding to each participant; further, Any one of the parties can submit a transaction to the blockchain, the transaction contains the above trigger information, so that the transaction can be based on the value of the state parameter corresponding to the any of the parties after the consensus, the above changes Execution, so that the state parameter corresponding to any one of the participants can be changed based on the amount of change.
  • the value of the state parameter corresponding to each participant and the amount of change are ciphertext values calculated based on a homomorphic encryption algorithm or a homomorphic commitment algorithm, respectively.
  • a homomorphic encryption algorithm any type of homomorphic encryption algorithm can be used, as long as the homomorphic encryption algorithm can satisfy the addition homomorphism, so that even in the ciphertext state, the value of the state parameter can still be increased or decreased
  • the amount of change; for this homomorphic encryption algorithm is an additive homomorphic encryption algorithm or a fully homomorphic encryption algorithm, this specification does not limit this.
  • a random number can be determined for the unencrypted data, and the corresponding commitment data can be calculated based on the random number and the unencrypted data.
  • the commitment data can be Used as the ciphertext value above.
  • the participant when the value and change of the state parameter are ciphertext values, the participant needs to provide relevant proof information so that the blockchain node can determine the legal validity of the transaction when performing the relevant transaction. For example, the participant needs to give a proof of the amount of change to show that the amount of change is in the correct numerical range, such as [0,2 64 ).
  • the event is used to make the value of the state parameter corresponding to a certain party decrease according to the change, that is, the purpose of the transaction is to make the value of the state parameter of the certain party reduce the change
  • the certain A participant needs to provide proof of the value and change of the state parameter to indicate that the value of the state parameter is not less than the value decrease (the value decrease is equivalent to the above change).
  • the Range Proof technology in related technologies can be used to generate the above-mentioned certification information, which is not limited in this specification.
  • the amount of change in the description information may be a ciphertext value.
  • the plaintext value of the change is t1
  • the corresponding ciphertext commitment T1 can be generated according to the plaintext value t1 and the random number r1
  • the description information can include the T1, t1, and r1, so that the event
  • the other participants can verify the correspondence between the ciphertext commitment T1 and the plaintext value t1 and random number r1.
  • the description information can encrypt and protect the plain text value t1 and the random number r1.
  • the identity public key corresponding to the digital identity of the participant X can be used to encrypt
  • the encrypted Enc_X(t1) and Enc_X(r1) are added to the description information, so only the participant X can decrypt Enc_X(t1) and Enc_X(r1) through their own identity private keys to obtain the above plaintext values t1 and The random number r1 significantly improves data security.
  • any other encryption method in the related art such as a digital envelope, can also be used, which is not limited in this specification.
  • the description information may respectively include encrypted data corresponding to each other party.
  • the plaintext value t1 and random number r1 can be encrypted according to participant X's identity public key to obtain Enc_X(t1), Enc_X(r1), and according to the participant Y's identity public key encrypts the plaintext value t1 and the random number r1 to obtain Enc_Y(t1), Enc_Y(r1), and adds Enc_X(t1), Enc_X(r1), Enc_Y(t1) and Enc_Y(r1) to
  • any one of the participants only needs to prepare one piece of description information and send it to each other participant separately, without preparing different description information for each other participant.
  • the description information sent to participant X includes Enc_X(t1) and Enc_X(r1), and is sent to participant Y
  • the description information contains Enc_Y(t1) and Enc_Y(r1), which is not limited in this manual.
  • the set transaction may include first proof information, and the first proof information is used to prove that the change amount is in a correct numerical range.
  • first proof information is used to prove that the change amount is in a correct numerical range.
  • any participant can also generate the first certification information, so that no matter whether it is generating multi-party trigger information or single-party trigger information, no other participation policy needs to take the value of the change And generate other certification information.
  • each participant can also generate the corresponding change amount (the change amount corresponding to each participant may be different; for example, in a cross-border remittance scenario, the value of the change amount may be different based on different currency types).
  • One proof information, this manual does not limit this.
  • Second proof information which is used to prove that the value of the state parameter corresponding to a certain participant is not less than the value reduction.
  • each participant of the event can generate corresponding second certification information and provide it to any of the above, when it is determined that its own state parameter will decrease according to the change amount.
  • Participants the multi-party trigger information is formed by any one of the parties; alternatively, the second certification information can be generated by the one of the parties in a unified manner, without the need for each participant to generate separately.
  • the participant that generates the unilateral trigger information can generate second certification information for itself.
  • the participant when a participant generates second certification information for itself, the participant first updates the value of its corresponding state parameter according to other events in which it participates, and then according to the updated state of the value
  • the parameter generates second proof information.
  • the value and change of the state parameter are ciphertext values, and the event is used to cause the state parameter corresponding to the participant to decrease in value according to the change, the participant needs to be based on the previously processed transaction To determine the value of the corresponding state parameter to generate the correct second proof information to ensure that the relevant event can be successfully executed.
  • the blockchain node After receiving the aggregate transaction submitted by each participant, the blockchain node extracts the alternative sub-transactions included in the aggregate transaction and confirms the trigger information (multi-party trigger information or unilateral trigger information) included in the alternative sub-transaction And verification.
  • the multi-party trigger information contains the confirmation information corresponding to all the participants of the event, or all the participants in the event have submitted the corresponding single-party trigger information (each single-party trigger information contains the corresponding participant's confirmation information)
  • the event can be marked as a success status; similarly, the event that failed verification can be marked as a failure status, and all the events will not be received within the valid time period.
  • the event of the confirmation information corresponding to the participant is marked as a timeout state, etc., and then the state of each event is submitted to the blockchain.
  • the participant can query the transaction records on the blockchain ledger to determine the status of each event in which it participates, for example, for a transaction that fails or times out,
  • the value of the status parameter needs to be restored accordingly (for example, if the participant is a remittance party, the corresponding account balance needs to be rolled back), and the status parameter needs to be updated for a successful transaction (for example, the participant is the payee At the time, you need to collect the corresponding transfer amount and add it to the account balance), and then take the updated value of the status parameter to generate the second proof information of the relevant event (ensure that the second proof information is based on the latest status parameter Value), and then generate and submit the above set of transactions.
  • the participants of the event include: a sender and a receiver
  • the amount of change includes: a transfer amount
  • the status parameter includes: account balance; in other words, It is equivalent to the transfer operation from the remittance to the beneficiary, so that the account balance of the remitter reduces the corresponding transfer amount, and the account balance of the beneficiary increases the corresponding transfer amount.
  • the description information may include the sender's account address, the recipient's account address, the transfer amount (commitment value), the transfer amount in plain text (encrypted state), random number (encrypted state), etc., to indicate the account from the sender The address transfers the transfer amount to the payee's account address.
  • the participants of the event include: a remittance party, a relay party, and a beneficiary party
  • the variation includes: the remittance party and the middle party
  • the status parameters include: account balance; in other words, Equivalent to transferring the first type of assets (such as Hong Kong dollars) between the sender and the relay, the amount of the asset is the first transfer amount, and transferring the second type of assets (such as the US dollar) between the relay and the receiver ).
  • the asset amount is the second transfer amount, and according to the exchange rate between the first type and the second type of assets, the asset value corresponding to the first transfer amount and the second transfer amount is basically the same.
  • the account balance is reduced by the first transfer amount (the first type of asset)
  • the payee's account balance is increased by the second transfer amount (the second type of asset)
  • the relay party's account balance is increased by the first transfer amount ( The first type of assets) and reduced the second transfer amount (the second type of assets), which means that the asset value has not changed.
  • the participants of the event include: a remittance party, n relay parties, and a payee
  • the variation includes: the remittance party and the first Transfer amount based on the first type of asset between 1 relay party, transfer amount based on the i type asset between the i-1th relay party and the ith relay party, the nth relay party and all Describe the transfer amount based on the n+1th type of assets between the payees.
  • the transfer of the first type of assets (such as Hong Kong dollars) between the remittance party and relay party 1
  • the amount of assets is the first Transfer amount
  • transfer the second type of assets such as Euros
  • the amount of the asset is the second transfer amount
  • the assets (such as US dollars) and the amount of assets are the third transfer amount
  • the first transfer is based on the exchange rate 1 between the first type and second type assets, and the exchange rate 2 between the second type and third type assets
  • Amount, the second transfer amount and the asset value corresponding to the third transfer amount are basically the same
  • the account balance of the sender is reduced by the first transfer amount (the first type of asset)
  • the account balance of the payee is increased by Three transfers (the third type of assets)
  • the account balance of relay 1 increases the first transfer (the first type of assets) and reduces the second transfer (the second type of assets)
  • the asset value The above is equivalent to no change, and the account balance of relay 2 has
  • the alternative sub-transactions included in the set transaction are also set with a state value before change and a state value after change, so that the backup
  • the state parameter of the participant changes from the pre-change state value to the post-change state value via the state change amount; wherein, the state change amount, the pre-change state
  • the value and the changed state value are ciphertext values calculated based on a homomorphic encryption algorithm or a homomorphic commitment algorithm, respectively.
  • FIG. 2 is a flowchart of another blockchain-based event processing method provided by an exemplary embodiment. As shown in Figure 2, this method is applied to blockchain nodes and can include the following steps:
  • Step 202 Receive a set transaction submitted by a participant to the blockchain, where the set transaction includes several candidate sub-transactions selected from a waiting queue maintained by the participant, and the candidate sub-transaction corresponds to the participation Events that the party is involved in.
  • each participant corresponds to a participant.
  • the participant may be an individual, an enterprise, an organization, etc. This specification does not limit this.
  • the participating object has a corresponding digital identity, so that the electronic device carrying the digital identity is equivalent to being configured as a participant corresponding to the participating object.
  • the events in this specification may include any type and cover any scenario, such as voting, signing agreements, traffic distribution, transfers, cross-border remittance, etc.
  • This specification does not limit this.
  • the descriptive information may include information such as voting reasons and voting options
  • the trigger information submitted in the blockchain of each participating direction may include the selection result of the voting options, thereby triggering the completion of the voting operation.
  • the candidate sub-transaction contains description information of the event, and the description information is used to describe the situation of the related event, so that when the candidate sub-transaction is processed, the corresponding event can be implemented according to the description information.
  • the description information can characterize the execution logic of related events, the involved parties, the way to change the state parameters of the parties (such as increasing or decreasing the value of the state parameters), the amount of change, etc. Limit it.
  • the relevant content of the event can be communicated in advance by any participant in any way, and then any of the participants can draft the description information of the event, so that other participants of the event can respond to the View and confirm the content of the description information; of course, any one of the participants can also determine other participants of the event and other content in the description information without prior communication.
  • This manual does not limit this .
  • the description information of the event may be generated by any participant of the event and added as an alternative sub-transaction in the waiting queue maintained by the any participant. And, the any participant also shares the generated description information to other participants, so that the other participants can confirm the description information.
  • any participant can send the description information to other participants of the event through an off-chain channel.
  • Sending the description information to other participants in the event through the off-chain channel can achieve the efficient transmission of the description information.
  • the off-chain channel may be an encrypted channel or other form of secure channel established between the parties to the event to avoid information leakage.
  • any participant can submit a transaction to the blockchain and include the above description information in the transaction, so that the transaction can be sent to all the blockchain after consensus Blockchain node; and each participant of the event can be configured as a blockchain node in the blockchain, or each participant can have a corresponding blockchain node in the blockchain, so that each participant The party can obtain the above transaction and the description information it contains through the blockchain ledger maintained by itself or the corresponding blockchain node (the blockchain ledger contains the entire transaction data of the blockchain), so that the above description information is Synchronize to other parties in the event.
  • the set transaction may include multiple alternative sub-transactions, each of which corresponds to an event in which the above-mentioned parties participate, so that the set transaction is included after being submitted to the blockchain.
  • Multiple alternative sub-transactions can be processed in the blockchain, so that multiple events corresponding to these alternative sub-transactions are implemented. It can be seen that by including multiple alternative sub-transactions in the set transaction, these alternative sub-transactions are submitted to the blockchain in batches, which can reduce the number of transactions submitted to the blockchain without generating for each alternative sub-transaction A blockchain transaction helps reduce resource consumption and improve processing efficiency.
  • the candidate sub-transactions in the waiting queue may be selected to: Generate the corresponding aggregate transaction.
  • the alternative sub-transactions that already exist in the waiting queue may be selected periodically according to a preset duration to generate a corresponding set transaction; of course, the capacity of each set transaction may have a maximum limit, such that There is a corresponding maximum value for the number of candidate sub-transactions selected in the same period, and the excess can be postponed to the next period for selection.
  • alternative sub-transactions can also be selected through other preset rules, which are not limited in this specification.
  • the candidate sub-transactions in the waiting queue can be arranged in order according to the time of addition, and each candidate sub-transaction can be selected in sequence from front to back each time, so that the previously generated candidate sub-transactions can be selected preferentially .
  • the participants can also implement the order-independent selection operation on the alternative sub-transactions in the waiting queue according to the actual needs, such as the urgency of the event, the priority of the event, etc.; or, the waiting queue itself can follow the above-mentioned emergency Sort by degree, priority, etc., so that it can still be regarded as one by one.
  • the participants may add numbers to each merged transaction in the order of generation, so that each merged transaction is processed sequentially in the blockchain according to the size of the corresponding number.
  • the blockchain transaction needs to read the number included in the merger exchange; if the number is continuous with the number of the previously processed merger transaction, for example, the latest processed merger transaction number is 99, If the number of the merged transaction currently received is 100, the merged transaction with the number of 100 can be processed; if the numbers are not continuous, for example, the number of the latest merged transaction processed is 99, the current received merged transaction If the number is 101, the blockchain node needs to wait and give priority to the merge transaction with the number 100 before it can process the merge transaction with the number 101.
  • the state parameters of the participant may change, and the execution of subsequent transactions depends on the value of the state parameters after the execution of the previous transaction, so it is necessary to ensure that each merged transaction is The size is processed sequentially so that each merged transaction can be executed correctly.
  • step 204 the aggregate transaction is executed to separately process the candidate sub-transactions in the aggregate transaction.
  • the candidate sub-transaction corresponding to the event includes multi-party trigger information for the event from all parties involved in the event; wherein, when the multi-party trigger information passes verification, the event The corresponding alternative sub-transaction is triggered to execute in the blockchain.
  • Multi-party trigger information represents the approval of all participants in the event for the description information and hopes to trigger the execution of the event.
  • the other participants can confirm the content of the description information, generate a signature on the description information through their own identity key, and return the signature to any participant
  • the multi-party trigger information can contain the description information and the signatures generated by each participant of the event; each signature belongs to the confirmation information provided by the corresponding participant, and if the cipher text value is used, the confirmation information will also contain the password Proof information for text values, which will be described in detail below.
  • the blockchain node can process the alternative sub-transactions submitted by any participant after the trigger information of multiple parties is verified.
  • the candidate sub-transaction corresponding to the event includes the single-party trigger information of the participant on the event; wherein, when all participants of the event submit to the blockchain When the unilateral trigger information of the event is all verified, the alternative sub-transaction corresponding to the event is triggered to execute in the blockchain.
  • the unilateral trigger information indicates that the corresponding participant confirms the description information of the event, hoping to trigger the execution of the event; and each participant of the event needs to submit the unilateral trigger information to the blockchain separately, so that the blockchain node is based on all participants Unilateral trigger information submitted separately to determine whether the event indicated by the corresponding alternative sub-exchange should be executed.
  • the above unilateral trigger information is submitted to the blockchain for verification by the blockchain nodes.
  • the unilateral trigger information can contain description information and the signature generated by the corresponding participant on the description information; the signature belongs to the confirmation information provided by the corresponding participant, and if the cipher text value is used, the confirmation information also contains the certification information, which will be described in detail below.
  • the description information of the event may include the amount of change
  • the event may be used to cause the state parameters correspondingly recorded on the blockchain by each participant to change according to the amount of change, such as increasing the amount of change. Value, decrease value, etc.
  • the corresponding state parameters may also be different according to the type of event or the difference in the scene.
  • the state parameter in the scenario of transfer or cross-border remittance can be the account balance of the participant
  • the state parameter in the scenario of traffic distribution can be the participant. This manual does not limit the amount of remaining flow.
  • the value of the state parameter corresponding to each participant and the amount of change may be a plain text value.
  • the blockchain nodes in the blockchain maintain a blockchain ledger, which records the full amount of transaction data, so that the blockchain node can learn the value of the state parameters corresponding to each participant; further, Any one of the parties can submit a transaction to the blockchain, the transaction contains the above trigger information, so that the transaction can be based on the value of the state parameter corresponding to the any of the parties after the consensus, the above changes Execution, so that the state parameter corresponding to any one of the participants can be changed based on the amount of change.
  • the value of the state parameter corresponding to each participant and the amount of change are ciphertext values calculated based on a homomorphic encryption algorithm or a homomorphic commitment algorithm, respectively.
  • a homomorphic encryption algorithm any type of homomorphic encryption algorithm can be used, as long as the homomorphic encryption algorithm can satisfy the addition homomorphism, so that even in the ciphertext state, the value of the state parameter can still be increased or decreased
  • the amount of change; for this homomorphic encryption algorithm is an additive homomorphic encryption algorithm or a fully homomorphic encryption algorithm, this specification does not limit this.
  • a random number can be determined for the unencrypted data, and the corresponding commitment data can be calculated based on the random number and the unencrypted data.
  • the commitment data can be Used as the ciphertext value above.
  • the participant when the value of the state parameter and the amount of change are ciphertext values, the participant needs to provide relevant proof information so that the blockchain node can determine the legal validity of the transaction when performing the relevant transaction. For example, the participant needs to give a proof of the amount of change to show that the amount of change is in the correct numerical range, such as [0,2 64 ).
  • the event is used to make the value of the state parameter corresponding to a certain party decrease according to the change, that is, the purpose of the transaction is to make the value of the state parameter of the certain party reduce the change
  • the certain A participant needs to provide proof of the value and change of the state parameter to indicate that the value of the state parameter is not less than the value decrease (the value decrease is equivalent to the above change).
  • the Range Proof technology in related technologies can be used to generate the above-mentioned certification information, which is not limited in this specification.
  • the amount of change in the description information may be a ciphertext value.
  • the plaintext value of the change is t1
  • the corresponding ciphertext commitment T1 can be generated according to the plaintext value t1 and the random number r1
  • the description information can include the T1, t1, and r1, so that the event
  • the other participants can verify the correspondence between the ciphertext commitment T1 and the plaintext value t1 and random number r1.
  • the description information can encrypt and protect the plain text value t1 and the random number r1.
  • the identity public key corresponding to the digital identity of the participant X can be used to encrypt
  • the encrypted Enc_X(t1) and Enc_X(r1) are added to the description information, so only the participant X can decrypt Enc_X(t1) and Enc_X(r1) through their own identity private key to obtain the above plaintext values t1 and The random number r1 significantly improves data security.
  • any other encryption method in the related art such as a digital envelope, can also be used, which is not limited in this specification.
  • the description information may respectively include encrypted data corresponding to each other party.
  • the plaintext value t1 and random number r1 can be encrypted according to participant X's identity public key to obtain Enc_X(t1), Enc_X(r1), and according to the participant
  • the identity public key of Y encrypts the plaintext value t1 and the random number r1 to obtain Enc_Y(t1), Enc_Y(r1), and adds Enc_X(t1), Enc_X(r1), Enc_Y(t1) and Enc_Y(r1) to
  • any one of the participants only needs to prepare one piece of description information and send it to each other participant separately, without preparing different description information for each other participant.
  • the description information sent to participant X includes Enc_X(t1) and Enc_X(r1), and is sent to participant Y
  • the description information contains Enc_Y(t1) and Enc_Y(r1), which is not limited in this manual.
  • the set transaction may include first proof information, and the first proof information is used to prove that the change amount is in a correct numerical range.
  • first proof information is used to prove that the change amount is in a correct numerical range.
  • any participant can also generate the first certification information, so that no matter whether it is generating multi-party trigger information or single-party trigger information, no other participation policy needs to take the value of the change And generate other certification information.
  • each participant can also generate the corresponding change amount (the change amount corresponding to each participant may be different; for example, in a cross-border remittance scenario, the value of the change amount may be different based on different currency types).
  • One proof information, this manual does not limit this.
  • Second proof information which is used to prove that the value of the state parameter corresponding to a certain participant is not less than the value reduction.
  • each participant of the event can generate corresponding second certification information and provide it to any of the above, when it is determined that its own state parameter will decrease according to the change amount.
  • Participants the multi-party trigger information is formed by any one of the parties; alternatively, the second certification information can be generated by the one of the parties in a unified manner, without the need for each participant to generate separately.
  • the participant that generates the unilateral trigger information can generate second certification information for itself.
  • the participant when a participant generates second certification information for itself, the participant first updates the value of its corresponding state parameter according to other events in which it participates, and then according to the updated state of the value
  • the parameter generates second proof information.
  • the value and change of the state parameter are ciphertext values, and the event is used to cause the state parameter corresponding to the participant to decrease in value according to the change, the participant needs to be based on the previously processed transaction To determine the value of the corresponding state parameter to generate the correct second proof information to ensure that the relevant event can be successfully executed.
  • the blockchain node After receiving the aggregate transaction submitted by each participant, the blockchain node extracts the alternative sub-transactions included in the aggregate transaction and confirms the trigger information (multi-party trigger information or unilateral trigger information) included in the alternative sub-transaction And verification.
  • the multi-party trigger information contains the confirmation information corresponding to all the participants of the event, or all the participants in the event have submitted the corresponding single-party trigger information (each single-party trigger information contains the corresponding participant's confirmation information)
  • the event can be marked as a success status; similarly, the event that failed verification can be marked as a failure status, and all the events will not be received within the valid time period.
  • the event of the confirmation information corresponding to the participant is marked as a timeout state, etc., and then the state of each event is submitted to the blockchain.
  • the participant can query the transaction records on the blockchain ledger to determine the status of each event in which it participates, for example, for a transaction that fails or times out,
  • the value of the status parameter needs to be restored accordingly (for example, if the participant is a remittance party, the corresponding account balance needs to be rolled back), and the status parameter needs to be updated for a successful transaction (for example, the participant is the payee At the time, you need to collect the corresponding transfer amount and add it to the account balance), and then take the updated value of the status parameter to generate the second proof information of the relevant event (ensure that the second proof information is based on the latest status parameter Value), and then generate and submit the above set of transactions.
  • the participants of the event include: a sender and a receiver
  • the amount of change includes: a transfer amount
  • the status parameter includes: account balance; in other words, It is equivalent to the transfer operation from the remittance to the beneficiary, so that the account balance of the remitter reduces the corresponding transfer amount, and the account balance of the beneficiary increases the corresponding transfer amount.
  • the description information may include the sender's account address, the recipient's account address, the transfer amount (commitment value), the transfer amount in plain text (encrypted state), random number (encrypted state), etc., to indicate the account from the sender The address transfers the transfer amount to the payee's account address.
  • the participants of the event include: a remittance party, a relay party, and a beneficiary party
  • the variation includes: the remittance party and the middle party
  • the status parameters include: account balance; in other words, Equivalent to transferring the first type of assets (such as Hong Kong dollars) between the sender and the relay, the amount of the asset is the first transfer amount, and transferring the second type of assets (such as the US dollar) between the relay and the receiver ).
  • the asset amount is the second transfer amount, and according to the exchange rate between the first type and the second type of assets, the asset value corresponding to the first transfer amount and the second transfer amount is basically the same.
  • the account balance is reduced by the first transfer amount (the first type of asset)
  • the payee's account balance is increased by the second transfer amount (the second type of asset)
  • the relay party's account balance is increased by the first transfer amount ( The first type of assets) and reduced the second transfer amount (the second type of assets), which means that the asset value has not changed.
  • the participants of the event include: a remittance party, n relay parties, and a payee
  • the variation includes: the remittance party and the first Transfer amount based on the first type of asset between 1 relay party, transfer amount based on the i type asset between the i-1th relay party and the ith relay party, the nth relay party and all Describe the transfer amount based on the n+1th type of assets between the payees.
  • the transfer of the first type of assets (such as Hong Kong dollars) between the remittance party and relay party 1
  • the amount of assets is the first Transfer amount
  • transfer the second type of assets such as Euros
  • the amount of the asset is the second transfer amount
  • the assets (such as US dollars) and the amount of assets are the third transfer amount
  • the first transfer is based on the exchange rate 1 between the first type and second type assets, and the exchange rate 2 between the second type and third type assets
  • Amount, the second transfer amount and the asset value corresponding to the third transfer amount are basically the same
  • the account balance of the sender is reduced by the first transfer amount (the first type of asset)
  • the account balance of the payee is increased by Three transfers (the third type of assets)
  • the account balance of relay 1 increases the first transfer (the first type of assets) and reduces the second transfer (the second type of assets)
  • the asset value The above is equivalent to no change, and the account balance of relay 2 has
  • the alternative sub-transactions included in the set transaction are also set with a state value before change and a state value after change, so that the backup
  • the state parameter of the participant changes from the pre-change state value to the post-change state value via the state change amount; wherein, the state change amount, the pre-change state
  • the value and the changed state value are ciphertext values calculated based on a homomorphic encryption algorithm or a homomorphic commitment algorithm, respectively.
  • each institution can separately merge several remittance transactions (equivalent to the above-mentioned alternative sub-transactions) in which it participates into a blockchain transaction (equivalent to the above-mentioned collective transaction), and through the The blockchain submits the blockchain transaction to realize the batch submission and processing of several remittance transactions.
  • the following will first describe the process of generating and processing a single remittance transaction, and then expand to the batch processing of multiple remittance transactions.
  • FIG. 3 is a schematic diagram of a scenario of cross-border remittance provided by an exemplary embodiment.
  • the user 1 transfers the blockchain to the user 2; among them, the "user" in this specification can be represented as a logged-in user account, and the user account can actually belong to an individual or organization.
  • the manual does not limit this.
  • user 1 opens a customer funds account at institution 1 in country A 1
  • user 2 opens a customer fund account 2 at institution 4 in country B
  • this specification can not directly implement cross-border remittances between institution 1 and institution 4.
  • the cross-border remittance operation is implemented on the blockchain.
  • Institution 1, institution 2, institution 3 and institution 4 have corresponding equipment 1, equipment 2, equipment 3 and equipment 4, respectively, and by running the client program of the blockchain on equipment 1 to 4, equipment 1 to 4 are Configured as a corresponding blockchain node; accordingly, institutions 1 to 4 can implement operations related to the blockchain through devices 1 to 4. For example, institutions 1 to 4 can submit corresponding blockchain transactions to the blockchain through devices 1 to 4; for another example, devices 1 to 4 respectively maintain full transaction data on the blockchain, that is, blockchain ledger, Institutions 1 to 4 can query and maintain the balance data of each blockchain account accordingly.
  • the blockchain account Y1 corresponding to institution 1 holds 1000 HKD
  • the blockchain account Y2 corresponding to institution 2 holds 2500 HKD and 4,200 Euros
  • the Blockchain account Y3 corresponding to Institution 3 holds 3,000 Euros and $2,000
  • the Blockchain account Y4 corresponding to Institution 4 holds $1,500.
  • the balance data of the blockchain accounts Y1 to Y4 are often not maintained in the form of plain text, but the corresponding cipher text data is used.
  • the blockchain account Y1 can be recorded as (currency_1, PC(a, r_a), Enc_A(a), Enc_A(r_a)) in the blockchain ledger, where: currency_1 means the currency type is Hong Kong dollar, a It means that the amount of Hong Kong dollar is 1000, r_a is the random number corresponding to a, PC(a, r_a) is the commitment value in the form of ciphertext calculated by Pedersen commitment mechanism for a and r_a, Enc_A(a), Enc_A(r_a) respectively Take values for the ciphertext of a and r_a (for example, you can use the identity public key of organization 1 for encryption, or you can use any other form of encryption algorithm).
  • the blockchain account Y2 can be recorded as (currency_1, PC(b1, r_b1), Enc_B(b1), Enc_B(r_b1)), (currency_2, PC(b2, r_b2), Enc_B(b2), Enc_B(r_b2)) ,
  • b1 means the amount of HKD is 2500
  • r_b1 is the random number corresponding to b1
  • currency_2 means the currency type is Euro
  • b2 means the amount of Euro is 4200
  • r_b2 is the random number corresponding to b2.
  • Blockchain account Y3 can be recorded as (currency_2, PC(c1, r_c1), Enc_C(c1), Enc_C(r_c1)), (currency_3, PC(c2, r_c2), Enc_C(c2), Enc_C(r_c2)) , Where: c1 indicates that the Hong Kong dollar is 3000, r_c1 is the random number corresponding to c1, currency_3 indicates the currency type is USD, c2 indicates the amount of USD is 2000, and r_c2 is the random number corresponding to c2.
  • the blockchain account Y4 can be recorded as (currency_3, PC(d, r_d), Enc_D(d), Enc_D(r_d)), where d represents the amount of USD 1500 and r_d is the random number corresponding to d.
  • FIG. 4 is a schematic diagram of interaction in a cross-border remittance process according to an exemplary embodiment.
  • the interactive process of cross-border remittance can include the following steps:
  • step 401 the device 1 drafts a remittance transaction tx_i.
  • user 1 wishes to send 500 HKD to user 2.
  • This user 1 can provide the 500 HKD through customer funds account 1 at institution 1, and user 2 can use customer funds account 2 at institution 4 Charge the US dollar calculated at a certain exchange rate.
  • the institution 1 may deduct 500 Hong Kong dollars from the customer funds account 1 corresponding to the user 1; and, the institution 1 needs to determine the remittance route between itself and the institution 4, for example, the remittance route in FIG. 4 is “ Institution 1 ⁇ Institution 2 ⁇ Institution 3 ⁇ Institution 4”, so that Institution 1 can transfer 500 HKD to Institution 2, Institution 2 can transfer 56 Euros (equivalent to 500 HKD) to Institution 3, Institution 3 can transfer to Institution 4 64 US dollars (equivalent to 56 euros, 500 Hong Kong dollars), and finally the institution 4 transfers 64 US dollars to the customer funds account 2 corresponding to user 2 to complete the remittance operation.
  • Institution 1 deducts 500 Hong Kong dollars from customer funds account 1
  • Institution 4 transfers US$64 to customer funds account 2 is an off-chain operation
  • institutions 1 to 4 realize the on-chain funds transfer through the blockchain.
  • substitution 1 ⁇ institution 2 ⁇ institution 3 ⁇ institution 4 there are two relay parties between organization 1 and organization 4 as organization 3 and organization 4; while in other implementations
  • the number of relay parties may be one, three, or more than three, and this specification does not limit this.
  • the remittance transaction tx_i drafted by the device 1 may include the following remittance transaction details: the transaction id is tx_i, the address Z1 of the blockchain account Y1, and the blockchain account Y2 Address Z2, blockchain account Y3 address Z3, blockchain account Y4 address Z4, cipher text information related to the transaction amount ⁇ (currency_1, PC(t1, r_t1), Enc_B(t1), Enc_B(r_t1) ,Enc_C(t1),Enc_C(r_t1),Enc_D(t1),Enc_D(r_t1)),(currency_2,PC(t2,r_t2),Enc_B(t2),Enc_B(r_t2),Enc_C(t2),Enc_C(r_t2 ),Enc_D(t2),Enc_D(r_D(r_D(r_t2),Enc_D(r_t2),Enc_D
  • the addresses Z1 to Z4 are used to indicate the participants of this remittance event, so that the subsequent transfer and remittance will be made from the blockchain accounts Y1 to Y4 corresponding to the addresses Z1 to Z4.
  • t1 means from address Z1 to address The transfer amount of Z2 (such as the above 500 Hong Kong dollars), r_t1 is the random number corresponding to the amount t1, PC(t1, r_t1) is the commitment value calculated based on the amount t1 and the random number r_t1, Enc_B(t1) indicates the institution 2
  • the ciphertext value of the amount t1 encrypted by the identity public key of the ID Enc_C(t1) means the ciphertext value of the amount t1 encrypted by the identity public key of the institution 3
  • Enc_D(t1) means the identity public key of the institution 4
  • rate1 and rate2 are the exchange rate of currency_1 and currency_2, and the exchange rate of currency_2 and currency_3 respectively. time is the trading moment. And, there may be some other data required for the transaction, which can be referred to the scheme in the related art, which will not be listed here one by one.
  • RP_t1, RP_t2, and RP_t3 are the interval proofs corresponding to the transaction amounts t1, t2, and t3, respectively, to prove that the transaction amounts t1, t2, and t3 are in the correct numerical range, for example, 1 ⁇ t1 ⁇ 2 64 , 1 ⁇ t2 ⁇ 2 64 , 1 ⁇ t3 ⁇ 2 64 .
  • the device 1 can generate the above-mentioned interval proof through the zero-knowledge proof technique in the related art, which is not limited in this specification.
  • the above cipher text information related to the transaction amount can be replaced with plain text information related to the transaction amount, such as ⁇ (currency_1,t1),(currency_2,t2 ),(currency_3,t3),rate1,rate2,time,... ⁇ , and does not need to include the above-mentioned interval proofs RP_t1, RP_t2, RP_t3, etc.
  • step 402a to 402c device 1 synchronizes the details of the remittance transaction to device 2, device 3, and device 4, respectively.
  • the device 1 may sign the details of the remittance transaction through the identity private key of the organization 1, and then send them to the device 2 to the device 4 through an off-chain (or referred to as off-chain) channel to achieve data synchronization.
  • an off-chain or referred to as off-chain
  • device 1 to device 4 respectively run a client program of the blockchain, so that device 1 to device 4 are respectively configured as blockchain nodes in the blockchain; or, device 1 to device 4 are There are corresponding blockchain nodes in the blockchain, and this specification does not limit this.
  • each blockchain node in the blockchain maintains a unified blockchain ledger, and the blockchain ledger records a full amount of blockchain data. Therefore, device 1 can generate a transaction that contains the remittance transaction details of the above remittance transaction tx_i, and submit the transaction to the blockchain; accordingly, when the transaction passes consensus, it can be sent to the district
  • Each blockchain node in the blockchain is used by each blockchain node to update its maintained blockchain ledger.
  • device 1, device 2, device 3, and device 4 can be informed of the above transaction submitted by device 1 through the blockchain ledger maintained by their corresponding blockchain nodes, so as to obtain the above remittance transaction tx_i included in the transaction Details of the remittance transaction.
  • the device 1 may also synchronize the remittance transaction data to the device 2 to the device 4 in other ways, which is not limited in this specification.
  • step 403a the device 1 adds the remittance transaction tx_i corresponding to the remittance transaction details to its own local queue 1.
  • the device 1 when the device 1 sends the remittance transaction details through the off-chain channel, the device 1 can directly add the remittance transaction tx_i to the local queue 1; of course, the device 1 can wait for the device 2 to the device 4 to confirm the details of the remittance transaction and After the corresponding confirmation response is returned, the remittance transaction tx_i is added to the local queue 1 to ensure that devices 2 to 4 all participate in the remittance transaction tx_i.
  • the device 1 when the device 1 synchronizes the details of the remittance transaction to the device 2 to the device 4 through the blockchain, the device 1 will also receive the details of the remittance transaction synchronized on the blockchain.
  • Remittance transaction details are verified (for verification process, please refer to step 403b), and after verification, add the remittance transaction tx_i to the local queue 1, or confirm that the remittance transaction details correspond to the remittance transaction tx_i, the remittance transaction tx_i is determined by the device 1
  • the verification process of the details of the remittance transaction is omitted, and it is directly added to the local queue 1.
  • step 403b after verifying the details of the received remittance transaction, the device 2 adds it to its own local queue 2.
  • the device 2 after receiving the details of the remittance transaction, the device 2 needs to implement a verification operation, including: the device 2 uses its own private key to identify the Enc_B(t1), Enc_B(r_t1), and Enc_B(t2) contained in the details of the remittance transaction.
  • the device 2 may add the corresponding remittance transaction tx_i to the local queue 2 maintained by itself, and return a confirmation response to the device 1 to indicate that the corresponding remittance transaction is accepted.
  • Steps 403c-403d after verifying the details of the received remittance transaction, the device 3-4 adds it to its own local queue 3-4.
  • the operations performed by the device 3 and the device 4 are similar to those of the device 2, and are not repeated here.
  • the remittance transaction tx_i has been added to the local queues 1 to 4 maintained by devices 1 to 4 respectively.
  • the processing method similar to the above remittance transaction tx_i can also be adopted.
  • the remittance transaction is added to the local queue for the transaction aggregation and batch processing in the following steps.
  • step 404a the device 1 aggregates the transaction TX_a according to the remittance transaction in the local queue 1, and submits it to the blockchain after signing.
  • the institution 1 can also participate in other remittance transactions. For example, when a user needs to remit money to another user through the institution 1, the device 1 can use a method similar to the above steps , Draft the corresponding remittance transaction, send the details of the remittance transaction to other institutions for verification, and add the corresponding remittance transaction tx_i to the local queue 1.
  • institution 1 can also act as a relay party for some remittance transactions (similar to the role of institution 2-3 in the above-mentioned embodiment) or a payee (similar to the role of institution 4 in the above-mentioned embodiment), making the institution 1
  • the device 1 can receive the remittance transaction details sent by the remittance party (similar to the role of the institution 1 in the above embodiment) of these remittance transactions, and add the corresponding remittance transaction to the local queue 1 after the verification is passed.
  • the local queue 1 maintained by the device 1 contains many remittance transactions in which the institution 1 participates.
  • the device 1 can select one or more remittance transactions from the local queue 1 each time according to the predefined transaction selection rules, and aggregate the selected remittance transactions to generate a blockchain transaction.
  • FIG. 5 is a schematic diagram of a blockchain transaction content based on a ciphertext value provided by an exemplary embodiment.
  • device 1 selects 4 remittance transactions and aggregates them into a blockchain transaction, for example, remittance transactions tx_11, tx_12, tx_13, and tx_14 are aggregated into blockchain transactions TX_1, and remittance transactions tx_21, tx_22 , Tx_23, tx_24 are aggregated into blockchain transactions TX_2, remittance transactions tx_31, tx_32, tx_33, tx_34 are aggregated into blockchain transactions TX_3.
  • Each blockchain transaction generated by the device 1 includes the sequence number seq set by the device 1 and information related to each remittance transaction.
  • the sequence number seq is related to the generation order of each blockchain transaction.
  • the seq value of the blockchain transaction TX_1 is 99
  • the seq value of the blockchain transaction TX_2 is 100
  • the seq value of the blockchain transaction TX_3 is 101
  • the blockchain transaction TX_1 is earlier than the blockchain transaction TX_2 Generation
  • blockchain transaction TX_2 is generated earlier than blockchain transaction TX_3.
  • the blockchain node will process each blockchain transaction in the order of seq from small to large, such as first processing the blockchain transaction TX_1, Then process the blockchain transaction TX_2, and then process the blockchain transaction TX_3.
  • the information related to each remittance transaction may include: the initial state balance of the blockchain transaction, the end state balance of the blockchain transaction, the initial state balance of each remittance transaction, the transaction amount of each remittance transaction, each remittance The balance of the transaction's end status (that is, the temporary status), the proof information of each remittance transaction, etc.
  • the initial balance of the blockchain transaction TX_1 is PC (100)
  • the final balance of the blockchain transaction TX_1 is PC (80)
  • the initial balance of the remittance transaction tx_11 is PC (100)
  • the transaction amount of the remittance transaction tx_11 For the PC (10) to be remitted, the end status balance of the remittance transaction tx_11 is PC (110), and the proof information of the remittance transaction tx_11 includes the interval proof that the PC (10) and PC (110) belong to the correct numerical range,
  • the related content of tx_12 to tx_14 please refer to FIG. 5, and no more examples will be given here.
  • institution 1 when institution 1 acts as a remittance or relay party in several remittance transactions included in this blockchain transaction, institution 1 will subtract the corresponding account transfer from its corresponding blockchain account Y1 account balance Amount (the remittance party only transfers out the funds; the relay party can receive the transferred funds and need to transfer out the funds, which is described here for the operation of the transferred funds), and continue to participate in the subsequent remittance transactions based on the updated remittance amount.
  • institution 1 After the blockchain transaction is submitted to the blockchain, if institution 1 as a remittance or relay party successfully executes a remittance transaction, institution 1 does not need to adjust the blockchain account Y1; if institution 1 acts as a remittance party or If a remittance transaction of the successor is not successfully executed, the institution 1 needs to adjust the balance of the account of the blockchain account Y1.
  • the above-mentioned blockchain transaction includes institution 1 as the payee or the relay party (the payee only transfers funds; the relay party can receive the transferred funds and need to transfer the funds, here is for the transferred funds
  • the institution 1 needs to add the corresponding funds to the blockchain account Y1 to realize the collection. If the remittance transaction is not successfully executed, the institution 1 does not need to adjust the blockchain account Y1.
  • the blockchain node when the blockchain node receives and processes the blockchain transaction submitted by the device 1, it can mark the status of each remittance transaction according to whether the remittance transaction included in the blockchain exchange can be successfully executed, such as the transaction is successful Status, failure status, timeout status, etc.
  • Blockchain transaction TX_1's initial state balance is PC(100)
  • device 1 aggregates and generates blockchain transaction TX_1
  • it does not directly set the value of the balance of the blockchain account Y1
  • the institution 1 acts as a relay or payee
  • the increase in the amount of money generated when the remittance transaction is marked as successful (receipt)
  • the increase in the amount of money when the remittance transaction of institution 1 as the sender or relay is marked as failed or overtime (for the deducted transfer amount) Rollback) etc.
  • the device 1 further calculates the corresponding value based on the value of the balance of the blockchain account Y1 (the transfer amount of the previously submitted remittance transaction has been deducted, the unreceived payment) and the actual amount change value of the above remittance transaction that may cause the amount change
  • the initial state balance of is PC (100); similarly, the device 1 should generate corresponding interval proofs for each remittance transaction included in the blockchain transaction TX_1 based on the initial state balance PC (100).
  • FIG. 6 is a schematic diagram of a block chain transaction content based on plain text values provided by an exemplary embodiment.
  • device 1 selects 4 remittance transactions and aggregates them into a blockchain transaction, for example, remittance transactions tx_11, tx_12, tx_13, and tx_14 are aggregated into blockchain transactions TX_1, and remittance transactions tx_21, tx_22 , Tx_23, tx_24 are aggregated into blockchain transactions TX_2, remittance transactions tx_31, tx_32, tx_33, tx_34 are aggregated into blockchain transactions TX_3.
  • Each blockchain transaction generated by the device 1 includes the sequence number seq set by the device 1 and information related to each remittance transaction.
  • the sequence number seq has the same function as the embodiment shown in FIG. 5 and will not be repeated here.
  • the information related to each remittance transaction can include: the initial state balance of the blockchain transaction, the end state balance of the blockchain transaction, and the transaction amount of each remittance transaction; and because of the use of plain text data, no longer need a picture
  • the device 2-3 aggregates and generates transactions TX_b and TX_c according to the remittance transactions in the local queue 2-3, and submits them to the blockchain after signing.
  • the device 2 may select one or more remittance transactions from the local queue 2 to aggregate and generate corresponding blockchain transactions. It is assumed that the device 2 includes the above-mentioned remittance transaction tx_i in a certain selected remittance transaction, and accordingly generates a corresponding blockchain transaction TX_b.
  • the device 3 may select one or more remittance transactions from the local queue 3 to aggregate and generate corresponding blockchain transactions. It is assumed that the device 3 includes the above-mentioned remittance transaction tx_i in a certain selected remittance transaction, and accordingly generates a corresponding blockchain transaction TX_c.
  • step 404d the device 4 aggregates and generates the transaction TX_d according to the remittance transaction in the local queue 4, and submits it to the blockchain after signing.
  • the device 4 may select one or more remittance transactions from the local queue 4 to aggregate and generate corresponding blockchain transactions. It is assumed that the device 4 includes the above-mentioned remittance transaction tx_i in a certain selected remittance transaction, and accordingly generates a corresponding blockchain transaction TX_d.
  • device 1 to device 4 can choose to generate the corresponding blockchain transaction according to the actual situation, and it does not necessarily process the remittance transaction tx_i immediately; in other words, device 1 to device 4 are actually asynchronous to the block
  • the chain submits the remittance transaction tx_i (included in the corresponding blockchain transaction), so that the execution of the remittance transaction tx_i is allocated to be triggered by the device 1 to the device 4 respectively, prompting the device 1 to the device 4 to participate in a large number of remittance transactions
  • blockchain transactions can be generated in batches for participating remittance transactions, thereby reducing the number of blockchain transactions generated and submitted, which helps reduce processing burden and improve processing efficiency.
  • Step 405 The blockchain node processes the received blockchain transaction to verify each remittance transaction included in the blockchain transaction.
  • Step 406 mark the remittance transaction tx_i.
  • each institution since each institution will continuously submit blockchain transactions to the blockchain, the remittance transactions included in the previously submitted blockchain exchange will affect the inclusion of blockchain transactions included in the subsequent submission. Remittance transactions, therefore, after receiving the blockchain transaction submitted by each institution, the blockchain node needs to read the sequence number seq contained in the received blockchain transaction, and process the Blockchain transactions of corresponding institutions.
  • a blockchain node when a blockchain node receives the TX_a blockchain transaction submitted by device 1, it reads the sequence number seq contained in it as 100; and if the sequence number of the latest blockchain transaction that the blockchain node has processed seq is 98, then the blockchain node needs to wait for the blockchain transaction with the sequence number seq of 99 submitted by the device 1, and only after the blockchain transaction with the sequence number 99 is processed, the sequence number is 100. Blockchain transactions are processed.
  • the blockchain nodes can separately extract the remittance transactions included in each blockchain transaction and implement separate measures for each remittance transaction verification.
  • the verification operation may include: verifying the signature is correct; verifying that the calculation of the actual amount change value of the above "remittance transaction that may cause the amount change" in the remittance transaction is correct, the interval is proved to be correct; the transfer amount and transfer in of the fund transfer Whether the amount is consistent, etc., will not repeat them one by one here.
  • FIG. 7 is a schematic diagram of a statistical trigger situation provided by an exemplary embodiment. As shown in FIG. 7, based on the native functions of the blockchain or the extended functions provided by smart contracts, blockchain nodes can separately record the blockchain transactions submitted by institutions 1 to 4, such as the blockchain submitted by institution 1.
  • the chain node can extract the remittance transactions included in each blockchain transaction and make statistics for the participants of each remittance transaction (the details of the remittance transaction include the information of the remittance, relay, and recipient): when received When the remittance transaction is included in the blockchain transaction submitted by the corresponding participant, and the remittance transaction passes the above-mentioned separate verification, the participant may be marked as "OK".
  • the blockchain node can be marked as shown in Figure 6 " Y1:OK”; similarly, if the blockchain nodes are also marked as "Y2:OK”, “Y3:OK”, “Y4:OK”, etc. for institutions 2 to 4, respectively, then the blockchain nodes can determine the The remittance transaction tx_i has been confirmed by all participants, and the remittance transaction tx_i can be marked as a successful status.
  • the blockchain node can only add the tag “Y2:” to the remittance transaction tx_#: “OK”, and need to continue to wait for the blockchain transaction submitted by device 1, device 3 and device 4.
  • the blockchain node will send the remittance transaction tx_i Marked as a timeout status, so that it cannot be successfully executed. If any of the participants in Institution 1 to Institution 4 mentioned a blockchain transaction containing the remittance transaction tx_i, but failed to pass the separate verification due to errors in the amount accumulation details or the interval certification error, then the blockchain node The remittance transaction tx_i will be marked as failed, so that it cannot be successfully executed.
  • Institution 1 to Institution 4 can refer to these statuses to generate the corresponding amount accumulation when they subsequently generate blockchain transactions Details, generating interval proofs with sufficient balance, etc. are similar to the processes described in steps 404a to 404d above, and will not be repeated here.
  • Institution 1 collected 500 HKD from user 1 outside the chain, and transferred 500 HKD to institution 2, and institution 2 received 500 HKD from institution 1, and transferred 56 to institution 3, and the institution 3 Collecting 56 euros transferred into institution 2 and transferring 64 dollars to institution 4, agency 4 charging 64 dollars transferred into institution 3 and transferring 64 dollars to user 1 outside the chain, which is equivalent to the balance of expenditures of institutions 1 to 4.
  • User 1 completes the remittance operation of 500 HKD to user 2.
  • the data changes on the blockchain ledger are:
  • the blockchain account Y1 corresponding to institution 1 is updated to (currency_1, PC(a-t1, r_a-r_t1), Enc_A(a-t1), Enc_A(r_a-r_t1 )), a reduction of 500 Hong Kong dollars;
  • the blockchain account Y2 corresponding to Institution 2 is updated to: (currency_1, PC(b1+t1, r_b1+r_t1), Enc_B(b1+t1), Enc_B(r_b1+r_t1)), ( currency_2,PC(b2-t2,r_b2-r_t2),Enc_B(b2-t2),Enc_B(r_b2-r_t2)), increased by 500 Hong Kong dollars, reduced by 56 Euros;
  • the corresponding blockchain account Y3 of Institution 3 is updated to: (currency_2,PC(c1+t2,r_c1+r_t2),Enc_C(c1+
  • FIG. 8 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to FIG. 8.
  • the device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810. Of course, it may include hardware required for other services.
  • the processor 802 reads the corresponding computer program from the non-volatile memory 810 into the memory 808 and then runs it to form a blockchain-based event processing device at a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as a logic device or a combination of software and hardware, etc., that is to say, the execution body of the following processing flow is not limited to each
  • the logic unit may also be a hardware or logic device.
  • the blockchain-based event processing device is applied to the participants, and may include:
  • the adding unit 901 adds corresponding candidate sub-transactions to the waiting queue maintained by the participant according to the events participated by the participant;
  • the generating unit 902 generates corresponding set transactions according to several candidate sub-transactions selected from the waiting queue;
  • the submission unit 903 submits the aggregate transaction to the blockchain, so that the alternative sub-transactions in the aggregate transaction are processed separately.
  • the generating unit 902 is specifically configured to:
  • the candidate sub-transactions already in the waiting queue are selected to generate a corresponding set transaction
  • the candidate sub-transactions that already exist in the waiting queue are periodically selected according to a preset duration to generate corresponding aggregate transactions.
  • Optional also includes:
  • the adding unit 904 adds corresponding numbers to each set transaction according to the generation order, so that each set transaction is sequentially processed according to the corresponding number size in the blockchain.
  • the candidate sub-transactions included in the set transaction are set with corresponding state changes, so that after the candidate sub-transactions are processed, the state parameter of the participant occurs based on the state change The corresponding value changes.
  • the state change amount is a plain text value.
  • the alternative sub-transactions included in the set transaction are also set with a pre-change state value and a post-change state value, so that after the alternative sub-transaction is processed, the state parameter of the participant is determined by the The state value before change changes to the state value after change through the state change amount;
  • the state change amount, the state value before the change, and the state value after the change are ciphertext values calculated based on a homomorphic encryption algorithm or a homomorphic commitment algorithm, respectively.
  • the set transaction also includes: first proof information, and the first proof information is used to prove that the increase in state value is at the correct value Interval
  • the set transaction also includes: second proof information, the second proof information is used to prove the state value reduction amount, the The changed state values corresponding to the selected candidate sub-transactions are all in the correct value range.
  • the adjacent alternative sub-transactions satisfy: the post-change state value corresponding to the previous alternative sub-transaction and the pre-change change corresponding to the latter alternative sub-transaction
  • the status value is the same.
  • the candidate sub-transaction corresponding to the event includes unilateral trigger information of the participant on the event; wherein, when all participants of the event submit to the blockchain for the When the unilateral trigger information of the event is all verified, the alternative sub-transaction corresponding to the event is triggered to execute in the blockchain.
  • the candidate sub-transaction corresponding to the event includes multi-party trigger information for the event from all parties involved in the event; wherein, when the multi-party trigger information passes verification, the event corresponding to the event Alternative sub-transactions are triggered to execute in the blockchain.
  • FIG. 10 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to FIG. 10.
  • the device includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, and a non-volatile memory 1010. Of course, it may include hardware required for other services.
  • the processor 1002 reads the corresponding computer program from the non-volatile memory 1010 into the memory 1008 and then runs it to form a blockchain-based event processing device at a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as a logic device or a combination of software and hardware, etc., that is to say, the execution body of the following processing flow is not limited to each
  • the logic unit may also be a hardware or logic device.
  • the blockchain-based event processing device is applied to a blockchain node, and may include:
  • the receiving unit 1101 receives a collective transaction submitted by a participant to the blockchain, and the collective transaction includes several alternative sub-transactions selected from a waiting queue maintained by the participant, and the alternative sub-transactions correspond to the Events involved by the participants;
  • the execution unit 1102 executes the collective transaction to separately process the candidate sub-transactions in the collective transaction.
  • Optional also includes:
  • the extracting unit 1103 extracts the serial number included in the aggregate transaction, and the serial number is added by the participant in the order of generation;
  • the processing unit 1104 sequentially processes each set transaction submitted by the participant according to the corresponding number size.
  • the candidate sub-transactions included in the set transaction are set with corresponding state changes, so that after the candidate sub-transactions are processed, the state parameter of the participant occurs based on the state change The corresponding value changes.
  • the state change amount is a plain text value.
  • the alternative sub-transactions included in the set transaction are also set with a pre-change state value and a post-change state value, so that after the alternative sub-transaction is processed, the state parameter of the participant is determined by the The state value before change changes to the state value after change through the state change amount;
  • the state change amount, the state value before the change, and the state value after the change are ciphertext values calculated based on a homomorphic encryption algorithm or a homomorphic commitment algorithm, respectively.
  • the set transaction also includes: first proof information, and the first proof information is used to prove that the increase in state value is at the correct value Interval
  • the set transaction also includes: second proof information, the second proof information is used to prove the state value reduction amount, the The changed state values corresponding to the selected candidate sub-transactions are all in the correct value range.
  • the adjacent alternative sub-transactions satisfy: the post-change state value corresponding to the previous alternative sub-transaction and the pre-change change corresponding to the latter alternative sub-transaction
  • the status value is the same.
  • the candidate sub-transaction corresponding to the event includes unilateral trigger information of the participant on the event; wherein, when all participants of the event submit to the blockchain for the When the unilateral trigger information of the event is all verified, the alternative sub-transaction corresponding to the event is triggered to execute in the blockchain.
  • the candidate sub-transaction corresponding to the event includes multi-party trigger information for the event from all parties involved in the event; wherein, when the multi-party trigger information passes verification, the event corresponding to the event Alternative sub-transactions are triggered to execute in the blockchain.
  • the system, device, module or unit explained in the above embodiments may be specifically implemented by a computer chip or entity, or implemented by a product with a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or any combination of these devices.
  • This specification proposes a computer-readable medium on which computer instructions are stored.
  • the technical solution of this specification is implemented, such as the blockchain-based event processing method of any of the above embodiments, here I will not repeat them one by one.
  • the computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory, random access memory (RAM) and/or non-volatile memory in computer-readable media, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
  • RAM random access memory
  • ROM read only memory
  • flash RAM flash random access memory
  • Computer-readable media including permanent and non-permanent, removable and non-removable media, can store information by any method or technology.
  • the information may be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices.
  • computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
  • first, second, third, etc. may use the terms first, second, third, etc. to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination”.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Cette invention concerne un procédé et un appareil de traitement de données financières sur la base d'une de blocs, ainsi qu'un dispositif électronique. Lorsqu'il est appliqué à un participant, le procédé comprend les étapes consistant à : ajouter, en fonction d'un événement auquel participe le participant, une sous-transaction alternative correspondante à une file d'attente maintenue par le participant (102) ; générer une transaction collectée correspondante sur la base de plusieurs sous-transactions alternatives sélectionnées à partir de la file d'attente (104) ; et soumettre la transaction collectée à une chaîne de blocs de telle sorte que les sous-transactions alternatives dans la transaction collectée soient respectivement traitées (106).
PCT/CN2019/113934 2018-12-14 2019-10-29 Procédé et appareil de traitement d'événements sur la base d'une chaîne de blocs et dispositif électronique WO2020119297A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811530103.3 2018-12-14
CN201811530103.3A CN110009316A (zh) 2018-12-14 2018-12-14 基于区块链的事件处理方法及装置、电子设备

Publications (1)

Publication Number Publication Date
WO2020119297A1 true WO2020119297A1 (fr) 2020-06-18

Family

ID=67165136

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/113934 WO2020119297A1 (fr) 2018-12-14 2019-10-29 Procédé et appareil de traitement d'événements sur la base d'une chaîne de blocs et dispositif électronique

Country Status (3)

Country Link
CN (1) CN110009316A (fr)
TW (1) TWI705691B (fr)
WO (1) WO2020119297A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110009316A (zh) * 2018-12-14 2019-07-12 阿里巴巴集团控股有限公司 基于区块链的事件处理方法及装置、电子设备
MY192336A (en) 2019-07-23 2022-08-17 Advanced New Technologies Co Ltd Managing transactions on blockchain networks
CN113435885A (zh) * 2019-08-30 2021-09-24 创新先进技术有限公司 在区块链中并发执行交易的方法和装置
CN111310237B (zh) * 2020-01-22 2024-04-26 腾讯科技（深圳）有限公司 一种基于区块链的业务处理方法、装置以及设备
CN116260707B (zh) * 2023-05-15 2023-10-10 安徽中科晶格技术有限公司 基于共识的区块链节点灾备方法、装置、设备及存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170193464A1 (en) * 2015-12-18 2017-07-06 Justin SHER Protocol utilizing bitcoin blockchain for maintaining independently proposed and approved set contents
CN107273455A (zh) * 2017-05-31 2017-10-20 深圳前海微众银行股份有限公司 区块链数据访问方法和装置
CN107704269A (zh) * 2017-10-16 2018-02-16 中国银行股份有限公司 一种基于区块链生成区块的方法以及系统
CN108520412A (zh) * 2018-04-18 2018-09-11 北京天德科技有限公司 一种面向区块链的清结算交易分账算法的设计方法
CN108776897A (zh) * 2018-06-05 2018-11-09 腾讯科技（深圳）有限公司 数据处理方法、装置、服务器及计算机可读存储介质
CN108876384A (zh) * 2018-09-19 2018-11-23 联动优势科技有限公司 一种交易数据的处理方法及装置
CN110009316A (zh) * 2018-12-14 2019-07-12 阿里巴巴集团控股有限公司 基于区块链的事件处理方法及装置、电子设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11941588B2 (en) * 2015-11-06 2024-03-26 Cable Television Laboratories, Inc. Systems and methods for blockchain virtualization and scalability
KR101950912B1 (ko) * 2016-08-01 2019-02-21 서강대학교산학협력단 블록체인 기반 트랜잭션 검증 시스템 및 그 방법
CN106982205B (zh) * 2017-03-01 2020-05-19 中钞信用卡产业发展有限公司杭州区块链技术研究院 基于区块链的数字资产处理方法和装置
CN108241979B (zh) * 2017-12-20 2021-03-16 深圳壹账通智能科技有限公司 基于区块链的多账本转账方法、电子装置及可读存储介质
CN108320228A (zh) * 2018-03-07 2018-07-24 物数（上海）信息科技有限公司 跨区块链资产交易方法、平台、设备及存储介质
CN108600161A (zh) * 2018-03-12 2018-09-28 成都零光量子科技有限公司 一种公平高效的区块链共识方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170193464A1 (en) * 2015-12-18 2017-07-06 Justin SHER Protocol utilizing bitcoin blockchain for maintaining independently proposed and approved set contents
CN107273455A (zh) * 2017-05-31 2017-10-20 深圳前海微众银行股份有限公司 区块链数据访问方法和装置
CN107704269A (zh) * 2017-10-16 2018-02-16 中国银行股份有限公司 一种基于区块链生成区块的方法以及系统
CN108520412A (zh) * 2018-04-18 2018-09-11 北京天德科技有限公司 一种面向区块链的清结算交易分账算法的设计方法
CN108776897A (zh) * 2018-06-05 2018-11-09 腾讯科技（深圳）有限公司 数据处理方法、装置、服务器及计算机可读存储介质
CN108876384A (zh) * 2018-09-19 2018-11-23 联动优势科技有限公司 一种交易数据的处理方法及装置
CN110009316A (zh) * 2018-12-14 2019-07-12 阿里巴巴集团控股有限公司 基于区块链的事件处理方法及装置、电子设备

Also Published As

Publication number Publication date
TW202023236A (zh) 2020-06-16
TWI705691B (zh) 2020-09-21
CN110009316A (zh) 2019-07-12

Similar Documents

Publication Publication Date Title
TWI724460B (zh) 基於區塊鏈的事件處理方法及裝置、電子設備
US10861016B2 (en) Event processing method, apparatus and electronic device based on blockchain technology
WO2020119298A1 (fr) Procédé et appareil de traitement d'événements basés sur une chaîne de blocs et dispositif électronique
WO2020119297A1 (fr) Procédé et appareil de traitement d'événements sur la base d'une chaîne de blocs et dispositif électronique
EP3745637B1 (fr) Système et procédé pour la protection d'informations
CN109242485B (zh) 区块链交易方法及装置、电子设备
EP3748901B1 (fr) Système et procédé de protection d'informations
CN109359971B (zh) 区块链交易方法及装置、电子设备
CN112651740A (zh) 区块链交易方法及装置、电子设备
CN113568946A (zh) 用于管理多个区块链网络中的交易的方法、系统和装置
CN113595734B (zh) 用于管理多个区块链网络中的交易的方法、系统和装置
CN111784341B (zh) 区块链交易方法及装置、电子设备、存储介质
CN113595733A (zh) 用于管理多个区块链网络中的交易的方法、系统和装置
CN110009323A (zh) 区块链交易方法及装置、电子设备、存储介质
WO2000022787A2 (fr) Procede, systeme et produit de programme informatique pour des services de courrier electronique renforces

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: 19896225

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: 19896225

Country of ref document: EP

Kind code of ref document: A1