Universally trusted bridges for heterogenous blockchain networks
US-2023073337-A1 · Mar 9, 2023 · US
US12088742B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12088742-B2 |
| Application number | US-202217664767-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 24, 2022 |
| Priority date | Sep 17, 2021 |
| Publication date | Sep 10, 2024 |
| Grant date | Sep 10, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present invention provides an anti-trapdoor-leakage on-chain data restoration system, at least comprising: a blockchain node, for broadcasting transaction data of a request-initiating person to blockchain nodes and proposer nodes in other groups, respectively; and a proposer node, for performing computation of a Chameleon-Hash function using a key set that is generated by a key-generating module provided in the proposer node, packaging the transaction data to generate a new block, and distributing the new block to all the blockchain nodes so that the blockchain nodes update their respective underlying ledgers according to the new blocks broadcasted by the proposer. The system of the present invention not only realizes such functions as restoration and editing of the transaction data, but also protects operational security and reliability of blockchains.
Opening claim text (preview).
What is claimed is: 1. An anti-trapdoor-leakage on-chain data restoration method, at least comprising: broadcasting transaction data of a request-initiating person to blockchain nodes and proposer nodes in other groups by a blockchain node, respectively; performing computation of a Chameleon-Hash function by a proposer node using a key set that is generated by a key-generating module provided in the proposer node; packaging the transaction data to generate a new block by the proposer node; distributing the new block to all the blockchain nodes by the proposer node; and making the blockchain nodes update their respective underlying ledgers according to the new blocks broadcasted by the proposer; further comprising: according to a type of the block, determining by the blockchain node whether a transaction initiated by a request-initiating person satisfies preset restoration conditions; based on a determination result, calling a relevant processing contract by the blockchain node; and according to the processing contract, restoring or synchronizing the data by the blockchain node, based on consensus reached through a multi-organization vote and insertion of the new block; further comprising: forming an index of a replacement block by using the tx_id of the cross-domain transaction; and sorting old transactions of a new organization with the same index and inserting it into the existing blockchain; wherein every said block in an underlying ledger that has been updated by the blockchain node has a block head including index records about a previous block and a next block with respect to that block, so as to enable the blockchain node to confirm data of the previous block and/or the next block with respect to that block through that block; wherein the proposer node modifies a hash of the previous block recorded in the old block confirmed according to the transaction data, through the computation of a Chameleon-Hash function; wherein after the computation of the Chameleon-Hash function, a hash of the previous block recorded in the old block remains unchanged, and the old block is marked as invalid but kept in the underlying ledger with its original capability of linking blockchains intact, after the blockchain node inserts the new block to the underlying ledger; further comprising: according to the called processing contract, searching for the relevant transaction so as to acquire a tx_id of the transaction; based on the acquired tx_id, searching for the relevant old block; and searching for the proposer node relevant to the old block and make the proposer node generate the new block. 2. The on-chain data restoration method of claim 1 , wherein a trapdoor key corresponding to the new block generated by the proposer node is different from a trapdoor key of the old block identified by the tx_id of the transaction. 3. The on-chain data restoration method of claim 2 , wherein the blockchain node or the client determines whether the transaction initiated by the request-initiating person satisfies the preset restoration conditions according to the block type; the corresponding processing contract is called based on the determination result; according to the processing contract, the consensus reached through a multi-organization vote is passed; and an instruction is generated based on the result of consensus reached through a multi-organization vote.
using cryptographic hash functions · CPC title
Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062) · CPC title
Revocation or update of secret information, e.g. encryption key update or rekeying · CPC title
using hash chains, e.g. blockchains or hash trees · CPC title
Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.