Conceptio › Archive › Google Patents

Google Patentsopen access

Universally trusted bridges for heterogenous blockchain networks — Paypal, Inc. (US11888991B2)

Paypal, Inc. · Google Patents

Google Patents · Patents · License: Open Access

patent, google patents, intellectual property, US11888991B2, Paypal, Inc., Michael Jim Tien Chan, en, 2024

ABSTRACT

Abstract

Different communication and software protocols may be used by different blockchain networks. Cross-chain communication is provided via a software bridge configured to enable specific operations. An event request may be sent from a first blockchain network to a second blockchain network. The event request may be processed using a first protocol of the first network to provide a first output. An offer of equivalent processing provided by the second network may be verified by: processing the event request using a second protocol of the second network to provide a second output, and confirming that the second output matches the offer of equivalent processing. A processing equivalence of the event request may be established between the first network and the second network based on the first output of the event request processed using the first protocol and the second output of the event request processed using the second protocol.

Description

TECHNICAL FIELD

The present disclosure generally relates to blockchain technology, and hardware and software related thereto. More specifically, the present disclosure relates to systems and methods for implementing blockchain bridges that allow exchanges between different types of blockchains in a variety of blockchain network environments, according to various embodiments.

BACKGROUND

Blockchains may have different formats that present interoperability problems. One type of blockchain may use different types of operations (e.g. encryption, transaction commitment, etc.) than another type of blockchain. This means that various blockchains cannot readily exchange information with each other, and thus, enabling a cross-chain transaction presents various difficulties.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide further understanding and are incorporated in and constitute a part of this specification, illustrate disclosed embodiments and, together with the description, serve to explain the principles of the disclosed embodiments. In the drawings:

FIG. 1 illustrates an example computing architecture for facilitating one or more blockchain based transactions.

FIG. 2 illustrates an example blockchain network.

FIG. 3 illustrates an example blockchain.

FIG. 4 is a diagram of an example transaction message.

FIG. 5 shows an example transaction broadcast the blockchain network.

FIG. 6 A is a flow diagram showing steps of an example method for performing a blockchain based transaction.

FIG. 6 B is a flow diagram showing steps of an example method for performing a blockchain based transaction.

FIG. 7 A shows an example of a privately broadcasted blockchain.

FIG. 7 B shows an example of blockchain misuse.

FIG. 8 illustrates an example of a blockchain enabled in-store purchase system.

FIG. 9 illustrates an example of communications for an IoT blockchain enabled device system.

FIG. 10 illustrates an example system.

FIG. 11 illustrates an example computing device.

FIG. 12 is a flow diagram showing steps of an example method for generating a blockchain bridge for heterogeneous blockchain networks for use in data exchange between the heterogenous blockchain networks.

FIG. 13 illustrates an example of a two-way polling service bridge established between a first blockchain network and a second blockchain network.

FIG. 14 illustrates examples of two-way polling service bridges established between blockchain networks.

FIG. 15 illustrates example events that trigger atomic blockchains for microservices.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference is made to the accompanying drawings identified above and which form a part hereof, and in which is shown by way of illustration of various embodiments in which aspects described herein may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope described herein. Various aspects are capable of other embodiments and of being practiced or being carried out in various different ways.

Blockchain bridges enable interoperability between different blockchain networks, such as Bitcoin, Ethereum, etc., and between parent blockchains and child blockchains (e.g., sidechains), which may operate under different protocols, consensus rules, cryptographic suites, etc. Interoperability between blockchain networks may include the transfer/exchange of tokens, data, and smart contract instructions between the blockchain networks. For example, blockchain bridges may allow users to deploy digital assets hosted on one blockchain network to decentralized applications (dApps) on another blockchain network, conduct fast, low-cost transactions of tokens hosted on otherwise less scalable blockchains, execute dApps across more than one blockchain network, and so forth.

However, to perform a cross-chain transaction, two or more blockchain networks involved in the transaction need to reach an agreement with regard to how the transaction will be processed on their respective blockchain networks. While third-party bridge solutions and single-side bridge solutions exist, these solutions are black/gray box as their internal mechanisms are proprietary for their developer, and often cause at least one side of a cross-chain transaction to have questions or concerns regarding the trustworthiness of the particular bridge. Currently, there is no trusted bridge for two or more blockchain networks with disparate network protocols or for when two states with regulatory oversight on the blockchain networks cannot trust each other. Thus, there is a need in the art for blockchain bridges that are co-built as a membrane of trust where participating networks may build and co-sign an offer-and-agreed upon premise for mapping respective network protocols to a single equivalent that can be used as a platform to conduct cross-chain transactions that may be represented on each of the participating networks.

In its broadest sense, blockchain refers to a framework that supports a trusted ledger that is stored, maintained, and updated in a distributed manner in a peer-to-peer network. For example, in a cryptocurrency application, such as Bitcoin or Ethereum, Ripple, Dash, Litecoin, Dogecoin, zCash, Tether, Bitcoin Cash, Cardano, Stellar, EOS, NEO, NEM, Bitshares, Decred, Augur, Komodo, PIVX, Waves, Steem, Monero, Golem, Stratis, Bytecoin, Ardor, or in digital currency exchanges, such as Coinbase, Kraken, CEX.IO, Shapeshift, Poloniex, Bitstamp, Coinmama, Bisq, LocalBitcoins, Gemini and others, the distributed ledger represents each transaction where units of the cryptocurrency are transferred between entities. For example, using a digital currency exchange, a user may buy any value of digital currency or exchange any holdings in digital currencies into worldwide currency or other digital currencies. Each transaction can be verified by the distributed ledger and only verified transactions are added to the ledger. The ledger, along with many aspects of blockchain, may be referred to as âdecentralizedâ in that a central authority is typically not present. Because of this, the accuracy and integrity of the ledger cannot be attacked at a single, central location. Modifying the ledger at all, or a majority of, locations where it is stored is made difficult so as to protect the integrity of the ledger. This is due in large part because individuals associated with the nodes that make up the peer-to-peer network have a vested interest in the accuracy of the ledger.

Though maintaining cryptocurrency transactions in the distributed ledger may be the most recognizable use of blockchain technology today, the ledger may be used in a variety of different fields. Indeed, blockchain technology is applicable to any application where data of any type may be accessed where the accuracy of the data is assured. For example, a supply chain may be maintained in a blockchain ledger, where the transfer of each component from party to party, and location to location, may be recorded in the ledger for later retrieval. Doing so allows for easier identification of a source for a defective part and where other such defective parts have been delivered. Similarly, food items may be tracked in like manner from farm to grocery store to purchaser.

Implementations of the present disclosure will now be described in detail with reference to the accompanying Figures.

It is to be understood that the phraseology and terminology used herein are for the purpose of description and should not be regarded as limiting. Rather, the phrases and terms used herein are to be given their broadest interpretation and meaning. The use of âincludingâ and âcomprisingâ and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items and equivalents thereof.

Computing Architecture

As discussed above, the distributed ledger in a blockchain framework is stored, maintained, and updated in a peer-to-peer network. In one example the distributed ledger maintains a number of blockchain transactions. FIG. 1 shows an example system 100 for facilitating a blockchain transaction. The system 100 includes a first client device 120 , a second client device 125 , a first server 150 , and an Internet of Things (IoT) device 155 interconnected via a network 140 . The first client device 120 , the second client device 125 , the first server 150 may be a computing device 605 described in more detail with reference to FIG. 6 . The IoT device 155 may comprise any of a variety of devices including vehicles, home appliances, embedded electronics, software, sensors, actuators, thermostats, light bulbs, door locks, refrigerators, RFID implants, RFID tags, pacemakers, wearable devices, smart home devices, cameras, trackers, pumps, POS devices, and stationary and mobile communication devices along with connectivity hardware configured to connect and exchange data. The network 140 may be any of a variety of available networks, such as the Internet, and represents a worldwide collection of networks and gateways to support communications between devices connected to the network 140 . The system 100 may also comprise one or more distributed or peer-to-peer (P2P) networks, such as a first, second, and third blockchain network 130 a - c (generally referred to as blockchain networks 130 ). As shown in FIG. 1 , the network 140 may comprise the first and second blockchain networks

130 a and 130 b . The third blockchain network 130 c may be associated with a private blockchain as described below with reference to FIG. 2 , and is thus, shown separately from the first and second blockchain networks 130 a and 103 b . Each blockchain network 130 may comprise a plurality of interconnected devices (or nodes) as described in more detail with reference to FIG. 2 . As discussed above, a ledger, or blockchain, is a distributed database for maintaining a growing list of records comprising any type of information. A blockchain, as described in more detail with reference to FIG. 3 , may be stored at least at multiple nodes (or devices) of the one or more blockchain networks 130 .

In one example, a blockchain based transaction may generally involve a transfer of data or value between entities, such as the first user 110 of the first client device 120 and the second user 115 of the second client device 125 in FIG. 1 . The server 150 may include one or more applications, for example, a transaction application configured to facilitate the transaction between the entities by utilizing a blockchain associated with one of the blockchain networks 130 . As an example, the first user 110 may request or initiate a transaction with the second user 115 via a user application executing on the first client device 120 . The transaction may be related to a transfer of value or data from the first user 110 to the second user 115 . The <figure-callout

TECHNICAL FIELD

BACKGROUND

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example computing architecture for facilitating one or more blockchain based transactions.

FIG. 2 illustrates an example blockchain network.

FIG. 3 illustrates an example blockchain.

FIG. 4 is a diagram of an example transaction message.

FIG. 5 shows an example transaction broadcast the blockchain network.

FIG. 6 A is a flow diagram showing steps of an example method for performing a blockchain based transaction.

FIG. 6 B is a flow diagram showing steps of an example method for performing a blockchain based transaction.

FIG. 7 A shows an example of a privately broadcasted blockchain.

FIG. 7 B shows an example of blockchain misuse.

FIG. 8 illustrates an example of a blockchain enabled in-store purchase system.

FIG. 9 illustrates an example of communications for an IoT blockchain enabled device system.

FIG. 10 illustrates an example system.

FIG. 11 illustrates an example computing device.

FIG. 13 illustrates an example of a two-way polling service bridge established between a first blockchain network and a second blockchain network.

FIG. 14 illustrates examples of two-way polling service bridges established between blockchain networks.

FIG. 15 illustrates example events that trigger atomic blockchains for microservices.

DETAILED DESCRIPTION

Implementations of the present disclosure will now be described in detail with reference to the accompanying Figures.

Computing Architecture

Blockchain Network

FIG. 2 shows an example blockchain network 200 comprising a plurality of interconnected nodes or devices 205 a - h (generally referred to as nodes 205 ). Each of the nodes 205 may comprise a computing device 605 described in more detail with reference to FIG. 6 . Although FIG. 2 shows a single device 205 , each of the nodes 205 may comprise a plurality of devices (e.g., a pool). The blockchain network 200 may be associated with a blockchain 220 . Some or all of the nodes 205 may replicate and save an identical copy of the blockchain 220 . For example, FIG. 3 shows that the nodes 205 b - e and 205 g - h store copies of the blockchain 220 . The nodes 205 b - e and 205 g - h may independently update their respective copies of the blockchain 220 as discussed below.

Blockchain Node Types

Blockchain nodes, for example, the nodes 205 , may be full nodes or lightweight nodes. Full nodes, such as the nodes 205 b - e and 205 g - h , may act as a server in the blockchain network 200 by storing a copy of the entire blockchain 220 and ensuring that transactions posted to the blockchain 220 are valid. The full nodes 205 b - e and 205 g - h may publish new blocks on the blockchain 220 . Lightweight nodes, such as the nodes

205 a and 205 f , may have fewer computing resources than full nodes. For example, IoT devices often act as lightweight nodes. The lightweight nodes may communicate with other nodes 205 , provide the full nodes 205 b - e and 205 g - h with information, and query the status of a block of the blockchain 220 stored by the full nodes 205 b - e and 205 g - h . In this example, however, as shown in FIG. 2 , the lightweight nodes

205 a and 205 f may not store a copy of the blockchain 220 and thus, may not publish new blocks on the blockchain 220 .

Blockchain Network Types

The blockchain network 200 and its associated blockchain 220 may be public (permissionless), federated or consortium, or private. If the blockchain network 200 is public, then any entity may read and write to the associated blockchain 220 . However, the blockchain network 200 and its associated blockchain 220 may be federated or consortium if controlled by a single entity or organization. Further, any of the nodes 205 with access to the Internet may be restricted from participating in the verification of transactions on the blockchain 220 . The blockchain network 200 and its associated blockchain 220 may be private (permissioned) if access to the blockchain network 200 and the blockchain 220 is restricted to specific authorized entities, for example organizations or groups of individuals. Moreover, read permissions for the blockchain 220 may be public or restricted while write permissions may be restricted to a controlling or authorized entity.

Blockchain

As discussed above, a blockchain 220 may be associated with a blockchain network 200 . FIG. 3 shows an example blockchain 300 . The blockchain 300 may comprise a plurality of

blocks

305 a , 305 b , and 305 c (generally referred to as blocks 305 ). The blockchain 300 comprises a first block (not shown), sometimes referred to as the genesis block. Each of the blocks 305 may comprise a record of one or a plurality of submitted and validated transactions. The blocks 305 of the blockchain 300 may be linked together and cryptographically secured. In some cases, the post-quantum cryptographic algorithms that dynamically vary over time may be utilized to mitigate ability of quantum computing to break present cryptographic schemes. Examples of the various types of data fields stored in a blockchain block are provided below. A copy of the blockchain 300 may be stored locally, in the cloud, on grid, for example by the nodes 205 b - e and 205 g - h , as a file or in a database.

Blocks

Each of the blocks 305 may comprise one or more data fields. The organization of the blocks 305 within the blockchain 300 and the corresponding data fields may be implementation specific. As an example, the blocks 305 may comprise a respective header

320 a , 320 b , and 320 c (generally referred to as headers 320 ) and block

data

375 a , 375 b , and 375 c (generally referred to as block data 375 ). The headers 320 may comprise metadata associated with their respective blocks 305 . For example, the headers 320 may comprise a

respective block number

325 a , 325 b , and 325 c . As shown in FIG. 3 , the block number 325 a of the block 305 a is Nâ1, the block number 325 b of the block 305 b is N, and the block number 325 c of the block 305 c is N+1. The headers 320 of the blocks 305 may include a data field comprising a block size (not shown).

The blocks 305 may be linked together and cryptographically secured. For example, the header 320 b of the block N (block 305 b ) includes a data field (previous block hash 330 b ) comprising a hash representation of the previous block Nâ1's header 320 a . The hashing algorithm utilized for generating the hash representation may be, for example, a secure hashing algorithm 256 (SHA-256) which results in an output of a fixed length. In this example, the hashing algorithm is a one-way hash function, where it is computationally difficult to determine the input to the hash function based on the output of the hash function. Additionally, the header 320 c of the block N+1 (block 305 c ) includes a data field ( previous block hash 330 c ) comprising a hash representation of block N's (block 305 b ) header 320 b.

The headers 320 of the blocks 305 may also include data fields comprising a hash representation of the block data, such as the block data hash 370 a - c . The block data hash 370 a - c may be generated, for example, by a Merkle tree and by storing the hash or by using a hash that is based on all of the block data. The headers 320 of the blocks 305 may comprise a

respective nonce

360 a , 360 b , and 360 c . In some implementations, the value of the nonce 360 a - c is an arbitrary string that is concatenated with (or appended to) the hash of the block. The headers 320 may comprise other data, such as a difficulty target.

The blocks 305 may comprise a

respective block data

375 a , 375 b , and 375 c (generally referred to as block data 375 ). The block data 375 may comprise a record of validated transactions that have also been integrated into the blockchain 200 via a consensus model (described below). As discussed above, the block data 375 may include a variety of different types of data in addition to validated transactions. Block data 375 may include any data, such as text, audio, video, image, or file, that may be represented digitally and stored electronically.

Blockchain Transaction

In one example, a blockchain based transaction may generally involve a transfer of data or value or an interaction between entities and described in more detail below. Referring back to FIG. 1 , the server 150 may include one or more applications, for example, a transaction application configured to facilitate a blockchain transaction between entities. The entities may include users, devices, etc. The first user 110 may request or initiate a transaction with the second user 115 via a user application executing on the first client device 120 . The transaction may be related to a transfer of value or data from the first user 110 to the second user 115 . The value or data may represent money, a contract, property, records, rights, status, supply, demand, alarm, trigger, or any other asset that may be represented in digital form. The transaction may represent an interaction between the first user 110 and the second user 115 .

FIG. 4 is a diagram of a flow 400 that generates a transaction 465 by the transaction application. The transaction 465 may include a public key 415 , a blockchain address 430 associated with the first user 110 , a digital signature 455 , and transaction output information 460 . The transaction application may derive a public key 415 from a private key 405 of the first user 110 by applying a cryptographic hash function 410 to the private key 405 . The cryptographic hash function 410 may be based on AES, SHA-2, SHA-3, RSA, ECDSA, ECDH (elliptic curve cryptography), or DSA (finite field cryptography), although other cryptographic models may be utilized. More information about cryptographic algorithms may be found in Federal Information Processing Standards Publication (FIPS PUB 180-3), Secure Hash Standard. The transaction application may derive an address or identifier for the first user 110 , such as the blockchain address 430 , by applying a hash function 420 to the public key 415 . Briefly, a hash function is a function that may be used for mapping arbitrary size data to fixed size data. The value may also be referred to as a digest, a hash value, a hash code, or a hash. In order to indicate that the first user 110 is the originator of the transaction 465 , the transaction application may generate the digital signature 455 for the transaction data 435 using the private key 405 of the first user 110 . The transaction data 435 may include information about the assets to be transferred and a reference to the sources of the assets, such as previous transactions in which the assets were transferred to the first user 110 or an identification of events that originated the assets. Generating the digital signature 455 may include applying a hash function 440 to the transaction data 435 resulting in hashed transaction data 445 . The hashed transaction data 445 and the transaction data 435 may be encrypted (via an encryption function 450 ) using the private key 405 of the first user 110 resulting in the digital signature 455 . The transaction output information 460 may include asset information 450 and an address or identifier for the second user 450 , such as the blockchain address 450 . The transaction 465 may be sent from the first client device 125 to the server 150 .

The specific type of cryptographic algorithm being utilized may vary dynamically based on various factors, such as a length of time, privacy concerns, etc. For example, the type of cryptographic algorithm being utilized may be changed yearly, weekly, daily, etc. The type of algorithms may also change based on varying levels of privacy. For example, an owner of content may implement a higher level of protection or privacy by utilizing a stronger algorithm.

Blockchain Addresses

A blockchain network may utilize blockchain addresses to indicate an entity using the blockchain or start and end points in the transaction. For example, a blockchain address for the first user 110 , shown in FIG. 4 as the blockchain address of sender 430 , may include an alphanumeric string of characters derived from the public key 415 of the first user 110 based on applying a cryptographic hash function 420 to the public key 415 . The methods used for deriving the addresses may vary and may be specific to the implementation of the blockchain network. In some examples, a blockchain address may be converted into a QR code representation, barcode, token, or other visual representations or graphical depictions to enable the address to be optically scanned by a mobile device, wearables, sensors, cameras, etc. In addition to an address or QR code, there are many ways of identifying individuals, objects, etc. represented in a blockchain. For example, an individual may be identified through biometric information such as a fingerprint, retinal scan, voice, facial id, temperature, heart rate, gestures/movements unique to a person etc., and through other types of identification information such as account numbers, home address, social security number, formal name, etc.

Broadcasting Transaction

The server 150 may receive transactions from users of the blockchain network 130 . The transactions may be submitted to the server 150 via desktop applications, smartphone applications, digital wallet applications, web services, or other software applications. The server 150 may send or broadcast the transactions to the blockchain network 130 . FIG. 5 shows an example transaction 502 broadcast by the server 150 to the blockchain network 130 . The transaction 502 may be broadcast to multiple nodes 205 of the blockchain network 130 . Typically, once the transaction 502 is broadcast or submitted to the blockchain network 130 , it may be received by one or more of the nodes 205 . Once the transaction 502 is received by the one or more nodes 205 of the blockchain network 130 , it may be propagated by the receiving nodes 205 to other nodes 205 of the blockchain network 130 .

A blockchain network may operate according to a set of rules. The rules may specify conditions under which a node may accept a transaction, a type of transaction that a node may accept, a type of compensation that a node receives for accepting and processing a transaction, etc. For example, a node may accept a transaction based on a transaction history, reputation, computational resources, relationships with service providers, etc. The rules may specify conditions for broadcasting a transaction to a node. For example, a transaction may be broadcast to one or more specific nodes based on criteria related to the node's geography, history, reputation, market conditions, docket/delay, technology platform. The rules may be dynamically modified or updated (e.g. turned on or off) to address issues such as latency, scalability and security conditions. A transaction may be broadcast to a subset of nodes as a form of compensation to entities associated with those nodes (e.g., through receipt of compensation for adding a block of one or more transactions to a blockchain).

Transaction ValidationâUser Authentication and Transaction Data Integrity

Not all the full nodes 205 may receive the broadcasted transaction 502 at the same time, due to issues such as latency. Additionally, not all of the full nodes 205 that receive the broadcasted transaction 502 may choose to validate the transaction 502 . A node 205 may choose to validate specific transactions, for example, based on transaction fees associated with the transaction 502 . The transaction 502 may include a blockchain address 505 for the sender, a public key 510 , a digital signature 515 , and transaction output information 520 . The node 205 may verify whether the transaction 502 is legal or conforms to a pre-defined set of rules. The node 205 may also validate the transaction 502 based on establishing user authenticity and transaction data integrity. User authenticity may be established by determining whether the sender indicated by the transaction 502 is in fact the actual originator of the transaction 502 . User authenticity may be proven via cryptography, for example, asymmetric-key cryptography using a pair of keys, such as a public key and a private key. Additional factors may be considered when establishing user authenticity, such as user reputation, market conditions, history, transaction speed, etc. Data integrity of the transaction 502 may be established by determining whether the data associated with the transaction 502 was modified in any way. Referring back to FIG. 4 , when the transaction application creates the transaction 465 , it may indicate that the first user 110 is the originator of the transaction 465 by including the digital signature 455 .

The node 205 may decrypt the digital signature 515 using the public key 510 . A result of the decryption may include hashed transaction data 540 and transaction data 530 . The node 205 may generate hashed transaction data 550 based on applying a hash function 545 to the transaction data 530 . The node 205 may perform a comparison 565 between the first hashed transaction data 540 and the second hashed transaction data 550 . If the result 570 of the comparison 565 indicates a match, then the data integrity of the transaction 502 may be established and node 205 may indicate that the transaction 502 has been successfully validated. Otherwise, the data of the transaction 502 may have been modified in some manner and the node 205 may indicate that the transaction 502 has not been successfully validated.

Each full node 205 may build its own block and add validated transactions to that block. Thus, the blocks of different full nodes 205 may comprise different val

CLAIMS

Claims ( 18 )

The invention claimed is:

1. A computer system comprising:

a non-transitory memory; and

one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the computer system to perform operations comprising:

sending an event request from a first blockchain network to a second blockchain network;

processing the event request using a first protocol of the first blockchain network, wherein the processing the event request using the first protocol provides a first output;

verifying an offer of equivalent processing provided by the second blockchain network by:

processing the event request using a second protocol of the second blockchain network, wherein the processing the event request using the second protocol provides a second output, and

confirming that the second output matches the offer of equivalent processing; and

performing additional operations to establish, on the first blockchain network, a processing equivalence of the event request between the first blockchain network and the second blockchain network based on the first output of the event request processed using the first protocol and the second output of the event request processed using the second protocol, wherein the first protocol and the second protocol have disparate blockchain consensus algorithms.

2. The computer system of claim 1 , wherein the processing the event request using the second protocol is performed in a sandbox on the second blockchain network.

3. The computer system of claim 1 , wherein the operations further comprise:

providing a sandbox on the first blockchain network, wherein the sandbox on the first blockchain network is configured to allow a node of the second blockchain network to process the event request using the first protocol of the first blockchain network to verify the first output.

4. The computer system of claim 1 , wherein the additional operations to establish the processing equivalence of the event request comprises:

digitally signing the processing equivalence; and

receiving a digital signature corresponding to the second blockchain network for the processing equivalence.

5. The computer system of claim 4 , wherein the additional operations to establish the processing equivalence further comprise broadcasting the processing equivalence to a main-net of the first blockchain network.

6. The computer system of claim 1 , wherein the operations further comprise confirming that the processing equivalence has been established on the second blockchain network by polling nodes on the second blockchain network to determine the nodes have an updated blockchain that includes the processing equivalence.

7. The computer system of claim 1 , wherein the operations further comprise:

sending a notice, to the second blockchain network, indicating an establishment of the processing equivalence on the first blockchain network; and

receiving, from the second blockchain network, a notice indicating an establishment of the processing equivalence on the second blockchain network.

8. A method comprising:

receiving, by a computer system corresponding to a first blockchain network, an event request from a second blockchain network;

processing, by the computer system, the event request using a first protocol of the first blockchain network, wherein the processing the event request using the first protocol provides a first output;

verifying, by the computer system, an offer of equivalent processing provided by the second blockchain network by:

processing, by the computer system, the event request using a second protocol of the second blockchain network, wherein the processing the event request using the second protocol provides a second output, and

confirming, by the computer system, that the second output matches the offer of equivalent processing; and

performing, by the computer system, operations to establish, on the first blockchain network, a processing equivalence of the event request between the first blockchain network and the second blockchain network based on the first output of the event request processed using the first protocol and the second output of the event request processed using the second protocol, wherein the first protocol and the second protocol have disparate blockchain consensus algorithms, and wherein the first protocol and the second protocol have different cryptographic hash functions.

9. The method of claim 8 , wherein the event request comprises a cross-chain cryptocurrency transaction request.

10. The method of claim 8 , wherein the verifying the offer of equivalent processing provided by the second blockchain network is performed in a sandbox on the second blockchain network.

11. The method of claim 10 , wherein the sandbox comprises designated cluster nodes on the second blockchain network.

12. The method of claim 8 , wherein the establishing, on the first blockchain network, the processing equivalence of the event request includes generating a two-way polling service bridge between the first blockchain network and the second blockchain network.

13. The method of claim 12 , further comprising conducting, by the computer system, a transaction with the second blockchain network using the two-way polling service bridge.

14. The method of claim 8 , wherein the first blockchain network is permissioned and the second blockchain network is permissionless.

15. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising:

sending an event request from a first blockchain network to a second blockchain network;

processing the event request using a first cryptographic hash function of the first blockchain network, wherein the processing the event request using the first cryptographic hash function provides a first output;

receiving, from the second blockchain network, an offer of equivalent processing of the event request;

verifying the offer of equivalent processing of the event request by:

processing the event request using a second cryptographic hash function of the second blockchain network, wherein the processing the event request using the second cryptographic hash function provides a second output, and

confirming that the second output matches the offer of equivalent processing; and

performing additional operations to establish, on the first blockchain network, a processing equivalence of the event request between the first blockchain network and the second blockchain network, wherein the first cryptographic has function and the second cryptographic has function have disparate blockchain consensus algorithms.

16. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:

broadcasting the processing equivalence of the event request to a main-net of the first blockchain network.

17. The non-transitory machine-readable medium of claim 15 , wherein the establishing the processing equivalence of the transaction includes generating a two-way polling service bridge with the second blockchain network based on the processing equivalence, wherein the two-way polling service bridge is configured to allow the first blockchain network and the second blockchain network to conduct a transaction, wherein the transaction is one of a plurality of types of transactions, and wherein each type of transaction has a corresponding two-way polling service bridge between the first blockchain network and the second blockchain network generated therefor.

18. The non-transitory machine-readable medium of claim 17 , wherein the operations further comprise conducting the transaction with the second blockchain network using the two-way polling service bridge.

US17/412,132

2021-08-25

Universally trusted bridges for heterogenous blockchain networks

Active

2042-07-21

US11888991B2

( en )

Priority Applications (2)

Application Number

Priority Date

Filing Date

Title

US17/412,132

US11888991B2

( en )

2021-08-25

Universally trusted bridges for heterogenous blockchain networks

US18/401,113

US20240205019A1

( en )

2021-08-25

2023-12-29

Universally trusted bridges for heterogenous blockchain networks

Applications Claiming Priority (1)

Application Number

Priority Date

Filing Date

Title

US17/412,132

US11888991B2

( en )

2021-08-25

Universally trusted bridges for heterogenous blockchain networks

Related Child Applications (1)

Application Number

Title

Priority Date

Filing Date

US18/401,113

Continuation

US20240205019A1

( en )

2021-08-25

2023-12-29

Universally trusted bridges for heterogenous blockchain networks

Publications (2)

Publication Number

Publication Date

US20230073337A1

US20230073337A1 ( en )

2023-03-09

US11888991B2

true

US11888991B2 ( en )

2024-01-30

Family

ID=85385751

Family Applications (2)

Application Number

Title

Priority Date

Filing Date

US17/412,132

Active

2042-07-21

US11888991B2

( en )

2021-08-25

Universally trusted bridges for heterogenous blockchain networks

US18/401,113

Pending

US20240205019A1

( en )

2021-08-25

2023-12-29

Universally trusted bridges for heterogenous blockchain networks

Family Applications After (1)

Application Number

Title

Priority Date

Filing Date

US18/401,113

Pending

US20240205019A1

( en )

2021-08-25

2023-12-29

Universally trusted bridges for heterogenous blockchain networks

Country Status (1)

Country

Link

( 2 )

US11888991B2

( en )

Cited By (2)

* Cited by examiner, â Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20230353394A1

( en )

2021-11-15

2023-11-02

Tencent Technology (Shenzhen) Company Limited

Cross-blockchain transaction processing method and apparatus, computer device, computer storage medium, and computer program product

US20240205019A1

( en )

2021-08-25

2024-06-20

Paypal, Inc.

Universally trusted bridges for heterogenous blockchain networks

Families Citing this family (14)

* Cited by examiner, â Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

WO2021039453A1

( en )

2019-08-29

2021-03-04

Control method, server, and program

WO2022225468A1

( en )

2021-04-20

2022-10-27

Angel Time Co., Ltd.

Multi dimension blockchain

WO2022220862A1

( en )

2021-09-14

2022-10-20

Futurewei Technologies, Inc.

System and methods of verifiable smart contract as a service

CN115834590A

( en )

2021-09-15

2023-03-21

åä¸ºææ¯æéå¬å¸

Block chain system

CN113810185B

( en )

2021-09-17

2022-09-27

åä¸ç§æå¤§å¦

Anti-trapdoor leakage on-chain data restoration system and method

KR102610011B1

( en )

2021-10-21

2023-12-04

ê³ ë ¤ëíêµ ì°ííë ¥ë¨

Method for reducing smart contract fee of dapp, recording medium and compute server for performing the method

US12627514B2

( en )

2021-11-29

2026-05-12

Kishore Swaminathan

Event-locked messages with provable attestation

US20230206216A1

( en )

2021-12-23

2023-06-29

Pangee, Inc.

Blockchain bridge systems, methods, and storage media for trading non- fungible token

US12219076B2

( en )

2022-06-15

2025-02-04

Coinbase, Inc.

Systems and methods for mitigating network congestion on blockchain networks by supporting blockchain operations through off-chain interactions

US12556416B2

( en )

2023-10-27

2026-02-17

Jinan University

Method and system for atomic, consistent and accountable cross-chain rewriting

US12475442B2

( en )

2023-12-01

2025-11-18

Halliday International, Inc.

Blockchain interoperability system

US12572922B2

( en )

2023-12-08

2026-03-10

Ava Labs, Inc.

Cross-chain transaction signing

US20250371527A1

( en )

2024-05-31

2025-12-04

Bank Of America Corporation

Intelligent system and method to derive a normalized consent protocol for heterogeneous distributed ledger leveraging neuro-symbolic artificial intelligence (ai)

CN119558974B

( en )

2024-11-29

2025-08-26

ä¸å¤®è´¢ç»å¤§å¦

A blockchain asset cyclic cross-chain exchange method based on chameleon hashing

Citations (6)

* Cited by examiner, â Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20190238316A1

( en )

2018-01-31

2019-08-01

Salesforce.Com, Inc.

Systems, methods, and apparatuses for implementing intelligent consensus, smart consensus, and weighted consensus models for distributed ledger technologies in a cloud based computing environment

US20200065763A1

( en )

2018-08-22

2020-02-27

Equinix, Inc.

Smart contract interpreter

US20200402025A1

( en )

2019-06-21

2020-12-24

Skychain Co., Ltd.

Escrowing system for cross-blockchain third-party settlement and method thereof

US20210157875A1

( en )

2018-10-26

2021-05-27

Advanced New Technologies Co., Ltd.

Blockchain-based cross-chain data access method and apparatus

US20210272075A1

( en )

2020-02-28

2021-09-02

nChain Holdings Limited

Methods and devices for controlling a mining pool for multiple blockchain networks

US20220147999A1

( en )

2019-07-26

2022-05-12

Huawei Technologies Co., Ltd.

Cross-chain transaction method and apparatus

Family Cites Families (4)

* Cited by examiner, â Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

EP3522088B1

( en )

2018-02-05

2022-03-16

Nokia Technologies Oy

Securing blockchain access through a gateway

CN110035046B

( en )

2018-11-16

2020-02-21

é¿éå·´å·´éå¢æ§è¡æéå¬å¸

Interaction system across blockchains

KR20200132518A

( en )

2019-05-17

2020-11-25

ì¼ì±ìì¤ëìì¤ ì£¼ìíì¬

System for supporting transaction interoperation between blockchain networks and method thereof

US11888991B2

( en )

2021-08-25

2024-01-30

Paypal, Inc.

Universally trusted bridges for heterogenous blockchain networks

2021

2021-08-25

US17/412,132

patent/US11888991B2/en

active

Active

2023

2023-12-29

US18/401,113

patent/US20240205019A1/en

active

Pending

Patent Citations (6)

* Cited by examiner, â Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20190238316A1

( en )

2018-01-31

2019-08-01

Salesforce.Com, Inc.

Systems, methods, and apparatuses for implementing intelligent consensus, smart consensus, and weighted consensus models for distributed ledger technologies in a cloud based computing environment

US20200065763A1

( en )

2018-08-22

2020-02-27

Equinix, Inc.

Smart contract interpreter

US20210157875A1

( en )

2018-10-26

2021-05-27

Advanced New Technologies Co., Ltd.

Blockchain-based cross-chain data access method and apparatus

US20200402025A1

( en )

2019-06-21

2020-12-24

Skychain Co., Ltd.

Escrowing system for cross-blockchain third-party settlement and method thereof

US20220147999A1

( en )

2019-07-26

2022-05-12

Huawei Technologies Co., Ltd.

Cross-chain transaction method and apparatus

US20210272075A1

( en )

2020-02-28

2021-09-02

nChain Holdings Limited

Methods and devices for controlling a mining pool for multiple blockchain networks

Cited By (3)

* Cited by examiner, â Cited by third party

Publication number

Priority date

Publication date

Assignee

Title

US20240205019A1

( en )

2021-08-25

2024-06-20

Paypal, Inc.

Universally trusted bridges for heterogenous blockchain networks

US20230353394A1

( en )

2021-11-15

2023-11-02

Tencent Technology (Shenzhen) Company Limited

Cross-blockchain transaction processing method and apparatus, computer device, computer storage medium, and computer program product

US12425246B2

( en )

2021-11-15

2025-09-23

Tencent Technology (Shenzhen) Company Limited

Cross-blockchain transaction processing method and apparatus, computer device, computer storage medium, and computer program product

Also Published As

Publication number

Publication date

US20230073337A1

( en )

2023-03-09

US20240205019A1

( en )

2024-06-20

Universally trusted bridges for heterogenous blockchain networks — Paypal, Inc. (US11888991B2)

Related documents