header-langage
简体中文
繁體中文
English
Tiếng Việt
Scan to Download the APP
Partnered With:

Blockchain Bridges: Building networks on top of encrypted networks

Read this article in 13 Minutes
Why is cross-chain bridging important? What might future cross-chain Bridges look like?
原文链接:《 Blockchain Bridges: Building Networks of Cryptonetworks 》
Source: 1kxNetwork Medium
原文作者: Dmitriy Berenzon
ETH Chinese station



After years of research and development, we have finally formed a multi-chain market structure. There are over 100 active public blockchains, many with their own unique applications, users, geographic distribution, security models, and design trade-offs. Regardless of what individual communities believe, the reality is that the universe tends to increase in entropy, and the number of these networks is likely to continue to increase in the future.


This type of market structure makes it imperative to achieve interoperability between different networks. Many developers have realized this, and last year saw a surge in the number of blockchain Bridges designed to bring together increasingly fragmented networks. As of this writing, there are over 40 different bridging projects.



  As of 8 September 2021; Demo drawing Demo drawing (incomplete)

In this article, I will:

· Explain why bridging is important


· Overview of various bridge designs and their advantages and disadvantages


· Overview of the current bridging landscape


· Describe what Bridges might look like in the future


Interoperability unlocks innovation possibilities.


As individual ecosystems grow, they develop their own unique advantages: greater security, greater throughput, cheaper transaction fees, better privacy, specific resource provisioning (storage, computing, bandwidth), regional developer and user communities, etc. Bridges are important because they give users access to new platforms and protocols; Enable protocols to interoperate with each other; Allowing developers to collaborate to build new products. More specifically, they have the following benefits:


Increase the productivity and availability of existing crypto assets.  


Bridging allows existing crypto assets to be moved to new platforms to do new things. Such as:


· Send DAI to Terra to purchase synthetic assets on Mirror or earn revenue on Anchor


· Send TopShot from Flow to Ethereum as collateral for NFTfi


· Loan DAI on Maker using DOT and ATOM as collateral


Extend product functionality of existing protocols.  


Bridging expands the design space that protocols can implement. Such as:


· Flow mining with Yearn Vaults on Solana and Avalanche


· NFT cross-chain shared order book on Ethereum and Flow on Rarible Protocol


Coop's proof of equity Index


Unlock new feature cases for users and developers  


Bridging gives users and developers more options. Such as:


· Arbitrage the price of SUSHI across DEX on Optimism, Arbitrum and Polygon


· Use Bitcoin to pay Arweave's storage fees


· Bid NFT on Tezos via PartyBid


The bridge 101 & have spent  


At an abstract level, a bridge can be defined as a system that transfers information between two or more blockchains. "Information" can refer to assets, contract calls, certificates, or states. Most bridge designs consist of the following components:


· Monitoring: There is usually an actor (or a "predictor", "verifier", "repeater") monitoring the state on the source chain.


· Messaging/relay: After an event is received by an actor, the information needs to be transferred from the source chain to the target chain.


· Consensus: In some models, consensus is required between participants monitoring the source chain in order to forward information to the target chain.


· Signature: Participants need to encrypt signatures of information sent to the target chain, either singly or as part of the Threshold signature scheme.


There are roughly four types of bridging schemes, each with its own advantages and disadvantages:


1. Asset-specific: The sole purpose of this bridge type is to provide access to a specific Asset in the external chain. These are typically 'wrapped' assets (assets that are fully collateralised by the underlying assets in custody or uncustody). Bitcoin is the most common asset that Bridges to other chains, with seven different Bridges on Ethereum alone. This bridge is the easiest to achieve, and you get a lot of liquidity out of it. But its functionality is limited and needs to be re-implemented on each target chain. Examples are wBTC and Wrapped Arweave.


2. Chain-specific: A bridge between two chains that typically supports locking and unlocking tokens on the source Chain and casting arbitrary encapsulated assets on the target Chain. Because of their limited complexity, these Bridges can often be brought to market more quickly, but they are also not easily scaled up to the broader ecosystem. The use case has Polygon's PoS bridge, which allows users to transfer assets from Ethereum to Polygon and vice versa, but only to those two chains.


3. Application-specific: an Application that provides access to two or more blockchains, but only for use within that Application. The inherent benefit of this application is that the code base is small; Instead of having a separate instance of the entire application on each blockchain, there are often more lightweight, modular "adapters" on each blockchain. A blockchain that implements an "adapter" has access to all other blockchains to which it is connected, so there are network effects. Their disadvantage is that it is difficult to extend this functionality to other applications (for example, from a lending application to a trading application). Specific use cases are Compound Chain and Thorchain, which build separate blockchains dedicated to cross-chain lending and transactions, respectively.


4. Generalized: A protocol designed to transfer information across multiple blockchains. Due to its low complexity, this design enjoys strong network effects -- a single integration of the project gives it access to the entire ecosystem within the bridge. The downside is that some designs often trade off security and decentralization to achieve this scalability effect. This can have complex and unintended consequences for ecosystems. One use case is IBC, which is used to send information between two heterogeneous chains (with final deterministic guarantee).



  As of September 14, 2021

In addition, according to the mechanism used to verify cross-chain transactions, there are roughly three types of bridge design:


Type 1: External Validators and federalism (External Validators & AMP; Federations)   


Such bridging schemes typically have a group of verifiers monitoring the "mailbox" address on the source chain and performing operations on the target chain based on consensus. Asset transfer typically works like this: assets are locked on a "mailbox" and an equal number of assets are cast on the target chain. These verifiers typically deposit separate tokens as collateral to keep the network secure.    



  Simplified diagrams of external validators and federated systems

Type 2: Light clients & AMP; Relays) 


参与者监测源链上的事件,并生成有关该链上记录的过去事件的加密打包证明。这些证明将和区块头一起被转发到目标链上的合约 (如「轻客户端」),然后验证某个事件是否被记录,并在验证后执行操作。这种设计机制需要一些参与者「中继」区块头和证明。虽然用户可以「自中继」交易,但确实存在中继将持续转发数据的活性假设。这是一种相对安全的桥接设计,因为它在无需信任中间实体的情况下保证了去信任的有效交付。但它也是资源密集型的,因为开发者必须在每条新目标链上构建一个新智能合约,来解析源链的状态证明;而验证流程本身则需要消耗大量 gas 费用。



  Abstract illustration of a light client/relay system

Type 3: Liquidity Networks


This is similar to a peer-to-peer network, where each node acts as a "router" holding a "library" of source and target chain assets. These networks typically leverage the security of the underlying blockchain; By using locking and disputing mechanisms, the router is guaranteed not to steal the user's money. Because of this, a mobile network like Connext may be a safer option for users who transfer a lot of value. In addition, this type of bridge may be best suited for cross-chain asset transfers because the assets provided by the router are native to the target chain, rather than derivative assets that cannot be completely replaced with each other.



Abstract diagram of a liquidity network


  According to the three bridge types above, the following chart can be obtained:    



  As of September 14, 2021

It is important to note that any given bridge above is a two-way communication channel. There may be separate models in each channel, so this classification does not accurately represent mixed models such as Gravity, Interlay, and tBTC. Because they both have light clients in one direction and verifier nodes in the other.


In addition, a bridge design can be roughly evaluated based on the following factors:


· Security: trust and active vacation facilities, tolerance for evil behavior, security and reflexivity of user funds.


· Speed: delay time for completion of the transaction and guarantee of final certainty. There is usually a trade-off between speed and safety.


· Connectivity: Target chain selection for users and developers, and different difficulty levels for integrating additional target chains.


· Capital efficiency: The economic mechanism that sets the transaction costs of transferring capital and assets needed to ensure system security.


· Statefulness: Ability to transfer specific assets, more complex states and/or perform cross-chain contract calls.


To sum up, the tradeoffs of these three design mechanisms can be evaluated from the following perspective:



In addition, security is a range, which can be roughly divided into the following categories:


· Trust-less: The security of a bridge is bound to the underlying blockchain it Bridges. Unless there is a consensus-level attack on the underlying blockchain, the user's money will not be lost or stolen. That is, it is not a complete lack of trust, because the economic, engineering, and cryptography components of all these systems have trust assumptions (i.e., there is no vulnerability in the code).


Insured: Attackers can steal users' money, but they may not be profitable for doing so. Because they need to post collateral to participate in the network, they are subject to forfeiture when they commit wrongdoing or misdeeds. If users lose their money, the agreement will compensate them by forfeiting the attacker's collateral.


· Bonded: &NBsp; Similar to the insurance model (i.e., the financial interests of the participants are closely related to their behavior), except that the user forfeits the collateral due to his or her error or malfeasance. The type of collateral is important for both insurance and mortgage mode; Endogenous collateral (agreed tokens as collateral) is riskier because if the bridge fails, the value of the token is also likely to collapse, further reducing the bridge's security guarantee.


· Trusted: Participants do not need to pledge assets, and users cannot retrieve assets in the event of system failure or malpractice, so security depends primarily on the reputation of the bridge operator.



  As of September 14, 2021

在未来的升级中,有几个项目将从「基于信任的」类别中移除。


Summarize the trade-offs of design mechanisms


"External verifier and federalism" is generally better for stateful and connectivity because they can trigger transactions, store data, and allow interaction with data on any number of target chains. However, this comes at the expense of security because, by definition, the user relies on the security of the bridge rather than the source or destination chain. While most external verifier mechanisms today are trust-based models, some require collateral assets, a subset of which is used to insure end users. Unfortunately, their insurance mechanisms are often reflexive. If the agreement token is used as collateral, it is assumed that the value of the token is sufficient to compensate the user for his loss. In addition, if the mortgaged asset is different from the insured asset, it depends on the price flow of the predictor, so the security of the bridge is degraded to that of the predictor. Without a trust model, these Bridges are also the least capital-efficient, since they increase economic throughput while also scaling up the size of the collateral.


"Light clients and relays" are also better in terms of state, since blockhead relays can transmit any type of data. Although there are activity assumptions due to the need for Repeaters to transmit information, they are also secure because no additional trust assumptions are required. At the same time, they are the most capital-efficient Bridges because no assets need to be locked up. However, these advantages come at the expense of connectivity. For each pair of chains connected, the developer must deploy a new light client smart contract on both the source and target chains, with a complexity between O(LogN) and O(N) (this is in the range because it is relatively easy to add chain support using the same consensus algorithm). There is also a significant speed deficit in optimistic models that rely on proof of fraud, which can increase the delay to 4 hours.


"Liquidity networks" are stronger in terms of security and speed because they are locally validated systems (i.e. do not require global consensus). They are also more capital efficient than external verifiers of mortgage/insurance schemes because capital efficiency is related to transaction flow/volume rather than safety. For example, assuming equal transaction flows in two chains, and given a built-in rebalancing mechanism, liquidity networks can facilitate arbitrarily large economic throughput.


The tradeoff is stateful, because while you can transfer call data, it has limited capabilities. For example, they can cross the chain and the data interaction, the receiving party shall have the right to according to the data provided by the interact (for example, using the information from the sender's signature calls smart contracts), but there is no "owners" to transfer data or transmission belongs to the general state of the data (such as casting represent tokens) didn't help.


Open questions.  


Building robust cross-chain Bridges is a challenge in distributed systems. Although many attempts have been made in this area, some problems remain to be solved:


· Final certainty and rollback (Finality & AMP; Rollbacks) : & have spent How do Bridges respond to block recombination and time thief attacks in chains with probabilistic finality? For example, what happens to users who send themselves from Boca to Ethereum if any of the chains undergo a state rollback?


· NFT Transfers & AMP; provenance) :  How do Bridges trace NFT across multiple chains? For example, if there is an NFT that has traded in multiple markets on Ethereum, Flow, and Solana, how are all those transactions and owners recorded?


· Stress Testing :& NBSP; How do various bridge designs respond in the case of chain congestion or protocol and network level attacks?


The future of blockchain Bridging  


While bridging unlocks more innovation possibilities for the blockchain ecosystem, it can also be a big risk if the team takes shortcuts in r&d. The Poly Network cross-chain attack shows us the scale of the potential economic losses of vulnerabilities and attacks, and I suspect there will be more large-scale attacks in the future. For bridge builders, though, networks are now highly fragmented and competitive. But teams should be highly disciplined and prioritize safety over speed of release.


While the ultimate ideal is to build a "isomorphic bridge" that is common to all things, the reality is that there is probably no single "optimal" bridge design. Different types of Bridges will be suitable for different specific applications (such as asset transfer, contract invocation, token minting, etc.).


In addition, the best Bridges should be the safest, connectable, fast, capital efficient, cost effective and resistant to censorship. These attributes need to be maximized if we want to realize the vision of the "blockchain Internet".


So far, we have not built an optimal bridge. There are several interesting development directions for all bridge types:


· Reduce the cost of header validation: The cost of header validation for light clients is very high, and if we can solve this problem, it will bring us closer to achieving full common and untrusted interoperability. An interesting design is to bridge to L2 to reduce these costs. For example, implement the Tendermint light client on zkSync.


· Move from a trust-based model to a mortgage model: While the capital efficiency of the mortgage verifier is much lower, the security of the "social contract" is not enough to secure billions of dollars of user funds. Furthermore, fancy threshold signatures do not reduce trust; This group of signers is still a trusted third party. In the absence of collateral, users are effectively handing over their assets to an external custodian.


· Change from mortgage mode to insurance mode: losing assets is the last thing users want to encounter. Although verifiers and Repeaters of mortgaged assets can prevent wrongdoing to some extent, the protocol should go further and compensate users directly with forfeiture funds.


· Expanding liquidity in liquidity networks: "Liquidity networks" are arguably the fastest bridging of asset transfers, and there are some interesting design trade-offs between trust and liquidity. For example, liquidity networks may use the mortgage verifier model to outsource capital supply, where routing can also be a threshold oversigner with mortgage liquidity.


· Bridge aggregation: While the use of Bridges may follow exponential laws for specific assets, aggregators like Li Finance can improve the experience for developers and end users.


Thank you very much. Feedback from Aidan Musnitzsky, Arjun Bhuptani, James Prestwich and Pranay Mohan.    


The original link




Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia

举报 Correction/Report
Choose Library
Add Library
Cancel
Finish
Add Library
Visible to myself only
Public
Save
Correction/Report
Submit