Blockchain Interoperability & Chain Abstraction: Deeply Intertwined, But Not The Same

Advanced8/23/2024, 7:20:51 AM
This article explores how interoperability technology serves as a foundational element for achieving seamless chain-agnostic experiences and how chain abstraction leverages interoperability solutions to enhance multi-chain interactions. Bungee, originally a bridge aggregator selecting the cheapest, fastest, and most liquid bridges based on user preferences, recognized the critical role of chain abstraction in addressing fragmentation and advancing the Web3 user experience. This led to the development of Socket 2.0, a modular and scalable coordination protocol for chain abstraction, allowing developers to build chain-agnostic applications. While interoperability and chain abstraction are distinct concepts, they are closely intertwined. As chain abstraction solidifies as the next evolutionary step in Web3, interoperability solutions will find new and creative ways to contribute, creating a positive flywheel effect.

Ever since the first smart contract networks appeared, the blockchain interoperability sector emerged with a clear goal: allowing users to freely navigate a multi-chain panorama, regardless of different blockchains’ standards, architecture, and economic structures.

Meanwhile, the race to build better blockchains and scale existing ones hasn’t stopped. This has led to a panorama where:

  • Blockchains are faster and cheaper than ever, launching and growing on an ongoing basis.
  • Modular scalability via L2s/L3s is fully integrated into the overall Web3 roadmap and culture—with the side effects of fragmentation.
  • Interoperability and cross-chain technologies aim to interconnect blockchains, but fail to independently address Web3’s larger user experience problem.
  • Chain abstraction emerges as the ultimate solution to turn a modular ecosystem into a borderless one, abstracting the complexities of interacting with multiple chains.

Blockchains’ evolution. Within the current, rapidly-expanding modular paradigm, some ecosystems end up inevitably siloed.

As Web3 experiences a paradigm shift, it’s worth considering: If chain abstraction solutions aim to create a borderless, unified ecosystem in which users can easily (often unknowingly) move across chains, how do they differ from interoperability and cross-chain solutions?

This article is here to answer just that while creating a comprehensive overview of the deep relation between both concepts and their evolution over time.

Demystifying blockchain interoperability and chain abstraction

With two terms commonly mistaken, such as blockchain interoperability and chain abstraction, it’s important to clarify and narrowly define both of them:

Interoperability

The term “interoperability” is broadly used in Web3 and, as mentioned in the introduction, often means different things. To present a definition that’s broad enough to contain all the different solutions classified under this term while clearly outlining its boundaries, we can use the following:

Interoperability solutions: Refers to different components and technologies facilitating the interaction of a chain with one or more others. These solutions can be either user- or developer-oriented, facilitating cross-chain usage either within dApps or as standalone products.

As such, blockchain interoperability solutions can also take the form of simple communication primitives or be constructed into somewhat complex products, with some of them becoming crucial to the current Web3 paradigm (like bridges). An incomplete list of these includes:

  • Cross-chain bridges, facilitating asset transfer among chains.
  • Atomic swap protocols, allowing users to exchange assets in one chain for assets in another.
  • Arbitrary Message Bridges (AMBs), which allow blockchains to exchange messages. AMBs are leveraged by developers to facilitate interoperability within dApps and other products or infrastructure.

Dedicated interoperability protocols based on DEXs (e.g. ThorChain).

Chain abstraction

As a quick recap from our previous articles, ChA is an organic response by the ecosystem to the ongoing problem of Web3’s fragmentation. It’s defined as “a user experience exempt from the manual processes required to interact with multiple chains” and, to be fully implemented requires multiple layers of technologies to be present across the technology stack. This is showcased below:

The three layers of chain abstraction, along with the problems each of them solves.

💡

For deeper insights into chain abstraction, you can visit our Learn Chain Abstraction page.

Relationship between interoperability and chain abstraction solutions

We’ve written extensively about how interoperability technologies are one of the foundational elements making the experience of chain abstraction possible.

Interoperability solutions are, to a great extent, the cornerstone upon which ChA is founded. Without the groundwork laid by bridges, messaging protocols, and other solutions, it’d be impossible to think about simplified multi-chain flows. As such, we can state that the vertical we today know as “chain abstraction” is, in part, a result of putting interoperability solutions to the service of an improved multi-chain experience.

This is also why we consider blockchain interoperability (along with account abstraction and intents) one of the three foundational technologies to improving Web3’s user experience and the main driver of the ChA revolution:

Alongside account abstraction and intents, interoperability solutions seek to abstract Web3’s complexities, leading to a frictionless future.

Leveraging blockchain interoperability solutions to enable ChA

Here, it’s worthwhile exploring how interoperability is used to construct ChA solutions. For this, we can revisit our integration depth framework.

This framework is based upon the idea that any component that—to any degree—attains the experience of “removing manual processes required for multi-chain interaction” can be deemed a chain abstraction solution. As such, interoperability technologies, like cross-chain messaging solutions, remain part of the chain abstraction stack but are primarily implemented within “deeper” integrations, which leverage them to enable chain abstraction across more than one area of the user experience.

Interoperability solutions exist at the base of the ChA stack, facilitating the creation of deeper implementations.

Blockchain Interoperability: Evolving towards chain abstraction implementations

To arrive at the main takeaway from this article, let’s now consider two key points:

  • As highlighted before, chain abstraction puts interoperability solutions to the service of an improved multi-chain experience.
  • As interoperability solutions become increasingly established and used within the industry, we can witness their providers’ attempts to present composable, complex solutions for developers and end-users—in other words, a quest to provide deeper ChA solutions.

The latter can be seen, for example, in the case of Stargate, a product by LayerZero. LayerZero’s first live product was a low-level communication primitive to be used to construct cross-chain dApps. After releasing this protocol, the team behind LZ decided to put these primitives into action to create a fully composable cross-chain bridging solution, a first of its kind. Given its full composability, this bridge can be deemed as an intermediate point between a foundational and orchestration solution, solving more and more complex problems required for the ChA experience.

The StarGate bridge, by utilizing interoperability solutions to achieve deeper ChA properties, solved blockchains’ bridging trilemma.

Another example of this is Socket. Originally a cross-chain Liquidity Layer (SocketLL) and Data Layer (SocketDL) used for blockchain interoperability and bridging, Socket eventually combined its product offering into Bungee. Bungee is, in essence, a bridge aggregator that chooses the cheapest/fastest/most liquid bridge available as per the preferences of the user. Later, realizing that chain abstraction was indispensable for tackling fragmentation and for Web3 UX to evolve, they began building Socket 2.0, a modular and extensible orchestration chain abstraction protocol for developers to build chain-agnostic applications.

Shifting tides

The above examples showcase what we expect to be a growing trend in Web3: the progressive settling of interoperability solutions at the core of the multi-chain experience, alongside the birth of creative applications aiming to implement ChA within a given area.

This also falls in line with the goals of interoperability solutions themselves as, once their base use cases are established, there are two paths of expansion for them:

  1. Capturing a larger share of the ecosystem (e.g. by integrating more chains/protocols).
  2. Reaching deeper levels of chain abstraction integrations.

Resultingly, as chain abstraction accelerates and interoperability solutions become a staple in the Web3 experience, we can only expect the latter to continue evolving, actively seeking to produce ChA infrastructure.

Conclusion

While interoperability and chain abstraction solutions are not the same, these two concepts are very closely intertwined. By zooming out, we can see that they represent different stages in the evolution of multi-chain interactions, moving in the same direction as the industry too evolves and grows.

As ChA solidifies itself as the next evolutionary step of Web3, interoperability solutions will only find new, creative ways of contributing to it, creating a positive flywheel effect.

In the end, this can only lead to a truly borderless, frictionless Web3 ecosystem.

Disclaimer:

  1. This article is reprinted from [blog], Forward the Original Title‘Blockchain Interoperability & Chain Abstraction: Deeply Intertwined, But Not The Same’, All copyrights belong to the original author [Carlos Maximiliano Cano]. If there are objections to this reprint, please contact the Gate Learn team, and they will handle it promptly.

  2. Liability Disclaimer: The views and opinions expressed in this article are solely those of the author and do not constitute any investment advice.

  3. Translations of the article into other languages are done by the Gate Learn team. Unless mentioned, copying, distributing, or plagiarizing the translated articles is prohibited.

Blockchain Interoperability & Chain Abstraction: Deeply Intertwined, But Not The Same

Advanced8/23/2024, 7:20:51 AM
This article explores how interoperability technology serves as a foundational element for achieving seamless chain-agnostic experiences and how chain abstraction leverages interoperability solutions to enhance multi-chain interactions. Bungee, originally a bridge aggregator selecting the cheapest, fastest, and most liquid bridges based on user preferences, recognized the critical role of chain abstraction in addressing fragmentation and advancing the Web3 user experience. This led to the development of Socket 2.0, a modular and scalable coordination protocol for chain abstraction, allowing developers to build chain-agnostic applications. While interoperability and chain abstraction are distinct concepts, they are closely intertwined. As chain abstraction solidifies as the next evolutionary step in Web3, interoperability solutions will find new and creative ways to contribute, creating a positive flywheel effect.

Ever since the first smart contract networks appeared, the blockchain interoperability sector emerged with a clear goal: allowing users to freely navigate a multi-chain panorama, regardless of different blockchains’ standards, architecture, and economic structures.

Meanwhile, the race to build better blockchains and scale existing ones hasn’t stopped. This has led to a panorama where:

  • Blockchains are faster and cheaper than ever, launching and growing on an ongoing basis.
  • Modular scalability via L2s/L3s is fully integrated into the overall Web3 roadmap and culture—with the side effects of fragmentation.
  • Interoperability and cross-chain technologies aim to interconnect blockchains, but fail to independently address Web3’s larger user experience problem.
  • Chain abstraction emerges as the ultimate solution to turn a modular ecosystem into a borderless one, abstracting the complexities of interacting with multiple chains.

Blockchains’ evolution. Within the current, rapidly-expanding modular paradigm, some ecosystems end up inevitably siloed.

As Web3 experiences a paradigm shift, it’s worth considering: If chain abstraction solutions aim to create a borderless, unified ecosystem in which users can easily (often unknowingly) move across chains, how do they differ from interoperability and cross-chain solutions?

This article is here to answer just that while creating a comprehensive overview of the deep relation between both concepts and their evolution over time.

Demystifying blockchain interoperability and chain abstraction

With two terms commonly mistaken, such as blockchain interoperability and chain abstraction, it’s important to clarify and narrowly define both of them:

Interoperability

The term “interoperability” is broadly used in Web3 and, as mentioned in the introduction, often means different things. To present a definition that’s broad enough to contain all the different solutions classified under this term while clearly outlining its boundaries, we can use the following:

Interoperability solutions: Refers to different components and technologies facilitating the interaction of a chain with one or more others. These solutions can be either user- or developer-oriented, facilitating cross-chain usage either within dApps or as standalone products.

As such, blockchain interoperability solutions can also take the form of simple communication primitives or be constructed into somewhat complex products, with some of them becoming crucial to the current Web3 paradigm (like bridges). An incomplete list of these includes:

  • Cross-chain bridges, facilitating asset transfer among chains.
  • Atomic swap protocols, allowing users to exchange assets in one chain for assets in another.
  • Arbitrary Message Bridges (AMBs), which allow blockchains to exchange messages. AMBs are leveraged by developers to facilitate interoperability within dApps and other products or infrastructure.

Dedicated interoperability protocols based on DEXs (e.g. ThorChain).

Chain abstraction

As a quick recap from our previous articles, ChA is an organic response by the ecosystem to the ongoing problem of Web3’s fragmentation. It’s defined as “a user experience exempt from the manual processes required to interact with multiple chains” and, to be fully implemented requires multiple layers of technologies to be present across the technology stack. This is showcased below:

The three layers of chain abstraction, along with the problems each of them solves.

💡

For deeper insights into chain abstraction, you can visit our Learn Chain Abstraction page.

Relationship between interoperability and chain abstraction solutions

We’ve written extensively about how interoperability technologies are one of the foundational elements making the experience of chain abstraction possible.

Interoperability solutions are, to a great extent, the cornerstone upon which ChA is founded. Without the groundwork laid by bridges, messaging protocols, and other solutions, it’d be impossible to think about simplified multi-chain flows. As such, we can state that the vertical we today know as “chain abstraction” is, in part, a result of putting interoperability solutions to the service of an improved multi-chain experience.

This is also why we consider blockchain interoperability (along with account abstraction and intents) one of the three foundational technologies to improving Web3’s user experience and the main driver of the ChA revolution:

Alongside account abstraction and intents, interoperability solutions seek to abstract Web3’s complexities, leading to a frictionless future.

Leveraging blockchain interoperability solutions to enable ChA

Here, it’s worthwhile exploring how interoperability is used to construct ChA solutions. For this, we can revisit our integration depth framework.

This framework is based upon the idea that any component that—to any degree—attains the experience of “removing manual processes required for multi-chain interaction” can be deemed a chain abstraction solution. As such, interoperability technologies, like cross-chain messaging solutions, remain part of the chain abstraction stack but are primarily implemented within “deeper” integrations, which leverage them to enable chain abstraction across more than one area of the user experience.

Interoperability solutions exist at the base of the ChA stack, facilitating the creation of deeper implementations.

Blockchain Interoperability: Evolving towards chain abstraction implementations

To arrive at the main takeaway from this article, let’s now consider two key points:

  • As highlighted before, chain abstraction puts interoperability solutions to the service of an improved multi-chain experience.
  • As interoperability solutions become increasingly established and used within the industry, we can witness their providers’ attempts to present composable, complex solutions for developers and end-users—in other words, a quest to provide deeper ChA solutions.

The latter can be seen, for example, in the case of Stargate, a product by LayerZero. LayerZero’s first live product was a low-level communication primitive to be used to construct cross-chain dApps. After releasing this protocol, the team behind LZ decided to put these primitives into action to create a fully composable cross-chain bridging solution, a first of its kind. Given its full composability, this bridge can be deemed as an intermediate point between a foundational and orchestration solution, solving more and more complex problems required for the ChA experience.

The StarGate bridge, by utilizing interoperability solutions to achieve deeper ChA properties, solved blockchains’ bridging trilemma.

Another example of this is Socket. Originally a cross-chain Liquidity Layer (SocketLL) and Data Layer (SocketDL) used for blockchain interoperability and bridging, Socket eventually combined its product offering into Bungee. Bungee is, in essence, a bridge aggregator that chooses the cheapest/fastest/most liquid bridge available as per the preferences of the user. Later, realizing that chain abstraction was indispensable for tackling fragmentation and for Web3 UX to evolve, they began building Socket 2.0, a modular and extensible orchestration chain abstraction protocol for developers to build chain-agnostic applications.

Shifting tides

The above examples showcase what we expect to be a growing trend in Web3: the progressive settling of interoperability solutions at the core of the multi-chain experience, alongside the birth of creative applications aiming to implement ChA within a given area.

This also falls in line with the goals of interoperability solutions themselves as, once their base use cases are established, there are two paths of expansion for them:

  1. Capturing a larger share of the ecosystem (e.g. by integrating more chains/protocols).
  2. Reaching deeper levels of chain abstraction integrations.

Resultingly, as chain abstraction accelerates and interoperability solutions become a staple in the Web3 experience, we can only expect the latter to continue evolving, actively seeking to produce ChA infrastructure.

Conclusion

While interoperability and chain abstraction solutions are not the same, these two concepts are very closely intertwined. By zooming out, we can see that they represent different stages in the evolution of multi-chain interactions, moving in the same direction as the industry too evolves and grows.

As ChA solidifies itself as the next evolutionary step of Web3, interoperability solutions will only find new, creative ways of contributing to it, creating a positive flywheel effect.

In the end, this can only lead to a truly borderless, frictionless Web3 ecosystem.

Disclaimer:

  1. This article is reprinted from [blog], Forward the Original Title‘Blockchain Interoperability & Chain Abstraction: Deeply Intertwined, But Not The Same’, All copyrights belong to the original author [Carlos Maximiliano Cano]. If there are objections to this reprint, please contact the Gate Learn team, and they will handle it promptly.

  2. Liability Disclaimer: The views and opinions expressed in this article are solely those of the author and do not constitute any investment advice.

  3. Translations of the article into other languages are done by the Gate Learn team. Unless mentioned, copying, distributing, or plagiarizing the translated articles is prohibited.

Empieza ahora
¡Regístrate y recibe un bono de
$100
!