header-langage
简体中文
English
Scan to Download the APP
Partnered With:

The Impossible Triangle of Ethereum Ecosystem Interoperability

Read this article in 9 Minutes
What is the underlying logic of different cross-chain and cross-L2 bridges? What are the pros and cons of each?
Original Title: "The Interoperability Trilemma"

Original Author: Arjun Bhuptani, Connext Co-Founder

Original compilation: Perry Wang, Lianwen


Understanding the Ethereum domain The Impossible Triangle of Interoperability


A few days ago, Connext launched NXTP, the underlying protocol for completely trustless transmission and contract invocation between Ethereum-compatible domains, that is, linking different blockchains and the second layer/L2 project.


I hope that through this article, I will explain why achieving interoperability in the Ethereum ecosystem is very difficult, and explain why we believe that: NXTP represents the ecosystem The beginning of a real long-term solution.


The need for trustless interoperability


Multi-chain/L2 Ethereum has became a fact and will continue to exist. Both protocols and applications have changed their development strategies to migrate to multiple domains, and users now have to deal with moving between layers, or to other L1 systems/sidechains on a daily basis. Projects scrambled to enable this migration for DeFi, spawning dozens of new “bridges” and interoperability protocols.


Unsurprisingly, this has also led to some high-profile hacks and scams: Cross-chain transaction protocol THORChain was hacked; PolyNetwork was hacked.


Despite these examples, every "bridge" system bills itself as trustless, secure, and decentralized - even if it's not. This means that the big challenge for developers and users now is: "how do I determine which bridge mechanisms are truly cryptoeconomically secure"?


In other words, when transferring funds between chains, how can users distinguish between "bridge" types to determine who to trust?


What exactly does "trustless" mean in cryptoeconomics?


In the research community, when we talk about the secure and trustless properties of the cryptoeconomy, we are actually asking a very specific question: who is validating the system , what is the cost of destroying them?


If our goal is to build truly decentralized, uncensorable public goods, we must consider that our system may be vulnerable to very powerful adversaries Attacks such as: sovereign states, large corporations, or megalomaniac-type evil geniuses.


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability

If your threat model does not include ( Amazon founder) Bezos eventually turns to the evil side, then you will not succeed.


Maximizing security means maximizing the number and diversity of validators (validators, miners, etc.) in the system This usually means doing your best to have a system that is fully validated by the Ethereum validator set - this is the core idea behind L2 and Ethereum's scaling scheme.


Aside: Most people don't realize this, but scalability research is interoperability research. While it has been clear for years that we can scale by moving to multiple domains, the question has always been: how to enable trustless communication between these domains. That's why John Adler's seminal paper on optimistic rollups is titled "Trustless Two-Way Bridges With Sidechains By Halting".


What happens if we add a new validator between domains?


We apply what we learned above about cryptoeconomic security to the Bridge.


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability


Consider a scenario: Suppose you are in Arbitrum With funds on , you specifically chose to use this domain because it's a rollup, which means (under some reasonable assumptions) that your funds are fully secured by Ethereum's underlying validators. In other words, your funds are probably as safe in the crypto economy as they are in the blockchain ecosystem.


Now imagine that you decide to use the "bridge" to transfer your funds to Optimism cheaply and quickly. Optimism is also trustless, so you can put your funds there with confidence knowing they will share the same level of security (Ethereum's) as Arbitrum.


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability


However, the "bridge" you use The protocol uses its own set of external validators. While this may not seem like a big deal at first, your funds are now no longer secured by Ethereum, but by validators on the "bridge":


• If this is an asset-locking/minting "bridge", creating packaged assets means the "bridge" validators can now unilaterally collude to steal all your funds;
• If this is a liquidity pool "Bridge", "Bridge" validators can collude in a similar way to steal all pool funds from liquidity providers (LP).


While everyone has waited years for a secure, trustless L2, your situation is not the same as when using a trusted sidechain or trusted L1 architecture The situation is the same.


The key takeaway is that a cryptoeconomic system is only as secure as its weakest link, and when you use an insecure "bridge", your chain or L2 security is also meaningless. And, similar to L1 and L2 security, it all boils down to one question: who verifies the system?


Classification of Interoperability Protocols


We can classify all interoperable There are three types of sexual agreements.


The first type: native authentication.


Native verification protocol is: for the data passed between chains, it is completely verified by the verifier of the underlying chain itself. This is usually done by running a light client of one chain in the Ethereum Virtual Machine (VM) of the other chain, or vice versa.


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability


Examples include Cosmos IBC and NEAR RainbowBridge. Rollup entry/exit is also a special form of it!


Advantages:
• No trust required for the highest form of interoperability since the underlying validators are directly responsible for securing the "bridge";
• Implementation Fully generic messaging between domains.


Disadvantages:
• Relies on the domain's underlying trust and/or consensus mechanisms to function, so must be custom built for each type of domain.


The Ethereum ecosystem is highly heterogeneous: we have numerous domains, from zk/optimistic rollups, to sidechains, to the foundations that run various consensus algorithms Chain: ETH-PoW, Nakamoto-PoW, Tendermint-PoS, Snowball-PoS, PoA, and many more consensus mechanisms. Each of these domains requires a unique strategy for achieving a natively validated interoperability system.


Second type: external validation.


External Validation Protocols are protocols that use a set of external validators to relay data between chains. This usually takes the form of a secure multi-party computation (MPC) system, oracle network, or threshold signatures (all of which are really the same thing).


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability


Examples include THORChain, Anyswap, Biconomy, Synapse, PolyNetwork, EvoDeFi, and many, many others.


Advantages:
• Allows for fully generic messaging between domains;
• Can be easily extended to any area.


Disadvantages:
• Users and/or LPs fully trust funds/data with external validators. This means that the model is substantially less secure than the underlying domain in terms of cryptoeconomics (similar to the comparison between Arbitrum and Optimism mentioned above).


In some cases, projects will use additional staking or bonding mechanisms in an attempt to increase security for users. However, this is usually economically inefficient. In order for the system to be trustless, users must cover the highest possible losses with collateral, and these collateral must be provided by the validators themselves. Not only does this significantly increase the capital required by the system, but it defeats the entire purpose of minting assets or liquidity pools in the first place.


The third type: local authentication.


A local verification protocol is a protocol in which only the parties involved in a particular cross-domain interaction verify the information exchanged. Local verification protocols transform the complex n-party verification problem into a much simpler set of two-party interactions, where each party only verifies its counterparty. This model works as long as the economic interests of the two parties are adversarial — that is, two parties cannot collude to obtain funds from the entire chain.


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability


Examples include Connext, Hop, Celer and Other simple atomic swap systems.


Advantages:
• Locally validated systems are trustless - their security is backed by the underlying chain as rollups share some reasonable Guarantees (eg, the chain cannot be vetted for more than X days);
• They are also easily scalable to other domains.


Note: Not every locally authenticated system is trustless. Some projects sacrifice trustlessness to some extent to improve the user experience or add additional functionality.


For example, Hop adds some trust assumptions by requiring a fast arbitrary-messaging-bridge (AMB) in the system: the protocol unlocks Bonder's Liquidity instead of waiting the full 7 days when exiting a rollup. The protocol also needs to rely on externally authenticated "bridges" if no AMB exists for a given domain.


Disadvantages:
Locally verified systems cannot support generalized data passing between chains.


The meaning of the above is a bit subtle, and may boil down to permission: locally verified systems can implement cross-domain contract calls, but only if the called function has some form of logical owner of . For example, the Uniswap token swap function can be invoked trustlessly across chains, since anyone with a swappable token can invoke the function. However, this method cannot lock and mint NFTs across chains without trust—this is because the logical owner of the mint function on the target chain should be the lock contract on the source chain, and this is in the local verification system. cannot be reflected.


The Interoperability Dilemma


Now we get to the topic of this article and what should drive users and the mental model that developers use to make decisions around the choice of "bridge".


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability


Similar to the scalability impossible triangle, There is also an interoperability impossibility triangle in the Ethereum ecosystem. Interoperability protocols can only have two of the following three properties:
• Trustless: have the same security as the underlying domain;
• Scalability: Any domain can support;
• Information Versatility: Ability to handle arbitrary cross-domain data.


How do Connext  and NXTP fit into this?


We could not find an easy way to achieve the desired results for all three interoperability properties. However, we have realized that the interoperability impossible triangle problem can be solved in the same way that Ethereum solved the scalability impossible triangle problem.


Ethereum L1 optimizes security and decentralization at the expense of scalability. The rationale behind this is that these properties are perhaps the most important to the longevity and usefulness of the blockchain. However, Ethereum enhances scalability through L2/sharding as a layer on top of the existing secure and decentralized backbone.


At Connext, we firmly believe that the longest-lived, most usable and adoptable interoperable system in the Ethereum ecosystem will be the A system that is maximally trustless and scalable. For this reason, NXTP was designed as a locally authenticated system, specifically designed to be as secure as the underlying domain, while being usable on any domain.


What about the versatility of information? Similar to scaling solutions in the Ethereum ecosystem, we increase the commonality of information by plugging a natively validated protocol on top of NXTP (as the L2 of our interoperable network!). This way, users and developers get a consistent interface across any domain, and can "upgrade" their connections to generalize information where that functionality is available.


Understanding the Impossible Triangle of Ethereum Inter-Domain Interoperability


This is why we say NXTP is our The underlying protocol for an interoperable network. Our entire network will consist of a series of protocols, including NXTP, a generic cross-chain bridge specific to a pair of domains, and protocols to connect them into one seamless system.


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