-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* addeed new page * Update learn-hyperbridge.md (#5507) * Update learn-hyperbridge.md * Update docs/learn/learn-hyperbridge.md Co-authored-by: Filippo <[email protected]> * Update docs/learn/learn-hyperbridge.md Co-authored-by: Filippo <[email protected]> * Update docs/learn/learn-hyperbridge.md Co-authored-by: Filippo <[email protected]> * Add links * Add links for barrentenberg (verified) --------- Co-authored-by: Filippo <[email protected]> --------- Co-authored-by: Tin Chung <[email protected]>
- Loading branch information
1 parent
9e30628
commit 40d296d
Showing
2 changed files
with
84 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,83 @@ | ||
| --- | ||
| id: learn-hyperbridge | ||
| title: Hyperbridge | ||
| sidebar_label: Hyperbridge | ||
| description: Polkadot's Bridge to Ethereum. | ||
| keywords: [bridge, polkadot, ethereum] | ||
| slug: ../learn-hyperbridge | ||
| --- | ||
|
|
||
| import RPC from "./../../components/RPC-Connection"; | ||
|
|
||
| :::info Learn about Parachain and Bridges | ||
|
|
||
| To fully follow the material on this page, it is recommended to be familiar with the concepts of [Parachain](./learn-parachains) and [Bridges](./learn-bridges.md). | ||
|
|
||
| ::: | ||
|
|
||
| Interoperability is the core vision of the {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} technology. Through years of blockchain development, much effort has been put into making a secure interoperability solution between blockchains. | ||
|
|
||
| Hyperbridge (short for hyper-scalable bridge) is innovated as a cross-chain solution built as an interoperability coprocessor. Hyperbridge is crafted to scale cryptographically secure, consensus, and state-proof-based interoperability across all blockchains. | ||
|
|
||
| ## Coprocessor Model | ||
|
|
||
| Ensuring secure cross-chain communication involves the meticulous verification of various aspects, including: [Consensus Mechanisms](https://wiki.polkadot.network/docs/learn-consensus), [Consensus Faults](https://research.polytope.technology/consensus-proofs), [State Proofs](https://research.polytope.technology/state-machine-proofs) and [State Transitions](https://wiki.polkadot.network/docs/learn-parachains#state-transitions). | ||
|
|
||
| > What is a coprocessor? | ||
| > | ||
| > **Coprocessor**, in the context of hardware, can be referred to a microprocessor designed to supplement the capabilities of the primary processor. For example, GPU is a coprocessor of the CPU to be optimized for graphical and simultaneous computation. | ||
| Due to the complexity and expensiveness of the onchain verification process, in coprocessor model, the computation is performed off-chain and the outcomes of the execution, along with cryptographic proofs validating their accuracy, are subsequently presented on-chain. | ||
|
|
||
| Expanding more about the coprocessor model, it has been applied in other solutions of offloading cryptographic computation as well, particularly, [**Zero-knowledge (ZK) coprocessor**](https://orochi.network/blog/Exploring-ZK-Coprocessor-What-Comes-Next) or [SNARK circuit](https://www.di.ens.fr/~nitulesc/files/Survey-SNARKs.pdf). | ||
|
|
||
| ### Parachain as Coprocessors | ||
|
|
||
| By leveraging the cost-effective consensus proofs facilitated by [BEEFY](https://spec.polkadot.network/sect-finality#sect-grandpa-beefy), Hyperbridge affirms the legitimacy of all parachain state transitions safeguarded by the network. | ||
|
|
||
| This capability enables the distribution of the validation workload for consensus, state proofs, and state transition re-execution across various designated [Parachain Cores](https://github.com/polkadot-fellows/RFCs/blob/6f29561a4747bbfd95307ce75cd949dfff359e39/text/0001-agile-coretime.md). Hence, Polkadot is utilized by the Hyperbridge as a verifiable computation layer to provide the ["Full Node Security"](https://blog.polytope.technology/introducing-hyperbridge-interoperability-coprocessor#full-node-level-security) in cross-chain bridges. | ||
|
|
||
| Hence, an additional layer of security is provided, allowing Hyperbridge to detect and prevent [Byzantine](https://en.wikipedia.org/wiki/Byzantine_fault) behaviors across connected chains. | ||
|
|
||
| ### Interoperable State Machine Protocol (ISMP) | ||
|
|
||
| [Interoperable State Machine Protocol (ISMP)](https://blog.polytope.technology/introducing-hyperbridge-interoperability-coprocessor) provides a familiar HTTP-like API for developers who want to make cross-chain requests to trigger certain logic on the counterparty chain. It allows making POST requests to send arbitrary data to connected chains, as well as GET requests to read the storage (verified through state proofs) of applications on connected chains. | ||
|
|
||
| In addition to facilitating cross-chain message passing among connected chains, ISMP also serves as a synchronisation primitive across Hyperbridge's internal state machines. This enables its parachain cores to communicate with each other and delegate tasks. | ||
|
|
||
| ### Underlying technologies | ||
|
|
||
| Underlying technologies of the Hyperbridge is integrated with: | ||
|
|
||
| - [PLONK verifier](https://eprint.iacr.org/2019/953.pdf): The PLONK Verifier within Hyperbridge can be likened to a sophisticated security apparatus. It operates akin to an expert detective, meticulously ensuring the legitimacy of every transaction without compromising private details. Continuously enhancing its capabilities, particularly with advancements like UltraPLONK, this integral component plays a pivotal role in maintaining the utmost integrity and confidentiality of cross-chain communications. | ||
| - [BEEFY consensus](https://spec.polkadot.network/sect-finality#sect-grandpa-beefy): The BEEFY (Bridge Efficiency Enabling Finality Yielder) protocol functions as a complementary system to GRANDPA, specifically designed to facilitate efficient bridging between the Polkadot network's relay chain and external, isolated blockchains like Ethereum. Notably, BEEFY addresses the challenge of interoperability with blockchains that were not initially constructed to integrate seamlessly with the Polkadot interchain framework. | ||
| - [The Barretenberg backend](https://github.com/AztecProtocol/barretenberg): Within the realm of Hyperbridge, Barretenberg functions as a powerhouse engine, adeptly managing intricate mathematical computations. Serving as the backend infrastructure, it guarantees the swift, secure, and reliable execution of all cryptographic operations within the Hyperbridge ecosystem. | ||
|
|
||
| ## Terminology | ||
|
|
||
| ### State Proofs | ||
|
|
||
| State proofs are a critical primitive of the blockchain stack that enable things like trustless bridges, off-chain light clients that can access on-chain data in a permissionless and secure manner as well as modular blockchains architectures where the execution layer can be decoupled from the consensus layer. | ||
|
|
||
| ### Consensus Proofs | ||
|
|
||
| Consensus Proofs in a blockchain system denote the mechanism by which participants, often nodes or validators, collectively agree on the validity of new transactions or blocks. The nature of consensus proofs varies across different blockchain architectures, such as Proof-of-Work, Proof-of-Stake, or other consensus algorithms. | ||
|
|
||
| The ultimate goal is to ensure a widespread and verifiable agreement among network participants, enhancing the security and reliability of the distributed ledger. | ||
|
|
||
| For example, Consensus Proofs in a proof of stake system is given as the signatures over the latest block header in the chain from a supermajority (two-thirds plus one) subset of the full authority set. | ||
|
|
||
| ## Learn More | ||
|
|
||
| The information provided here is subject to change; keep up to date using the following resources: | ||
|
|
||
| - [Introducing Hyperbridge: An Interoperability Coprocessor](https://blog.polytope.technology/introducing-hyperbridge-interoperability-coprocessor) - Article by Seun Lanlege, Polytope Lab founder. | ||
| - [Digital Services as State Machines](https://polkadot-blockchain-academy.github.io/pba-book/blockchain-contracts/services-as-state-machines/page.html) - Lecture about state machine from Polkadot Blockchain Academy | ||
| - [Polkadot Wiki - Bridges](https://wiki.polkadot.network/docs/learn-bridges) - Learn about bridges in Polkadot | ||
| - [Polkadot Wiki - Parachain](https://wiki.polkadot.network/docs/learn-parachains) - Learn about parachain in Polkadot | ||
| - [Hyperbridge Source Code](https://github.com/polytope-labs/hyperbridge) - Public codebase repository of hyperbridge. | ||
| - [Interoperable State Machine Protocol (ISMP) Book](https://ismp.polytope.technology/) - Guidebook of the ISMP | ||
| - [The Puzzle of Blockchain Interoperability](https://twitter.com/stakenode_dev/status/1744653040764817675) | ||
| - [RFC-1: Agile Coretime](https://github.com/polkadot-fellows/RFCs/blob/6f29561a4747bbfd95307ce75cd949dfff359e39/text/0001-agile-coretime.md) - Agile periodic-sale-based model for assigning Coretime on the Polkadot Ubiquitous Computer. | ||
| - [ISMP, The Endgame for Parachain Interoperability | Sub0 2023](https://www.youtube.com/watch?v=MCOAwooWecs) | ||
| - [Research Summary: PlonK: Permutations over Lagrange-bases for Oecumenical Noninteractive arguments of Knowledge](https://www.smartcontractresearch.org/t/research-summary-plonk-permutations-over-lagrange-bases-for-oecumenical-noninteractive-arguments-of-knowledge/382) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters