Update 2_crossChainInteroperability.md

This commit is contained in:
Madhav Goyal 2023-06-22 10:36:17 +05:30 committed by GitHub
parent aad9eee488
commit d7673a6e3b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 9 deletions

View File

@ -4,27 +4,27 @@ Because blockchains are siloed by nature, individual cryptocurrencies being boun
Centralized exchanges play an important role in cryptocurrency, but they are not a complete solution for blockchain interoperability for two primary reasons: (1) they're centralized, which is counterproductive to creating a decentralized platform, and (2) they deal only with tokens.
To solve the centralization problems with CEXs, decentralized exchanges (DEXs) were created. A DEX operates inside a smart contract runtime and can be as decentralized as the blockchain it runs on. Unfortunately, a DEX is only able to utilize the tokens on its native blockchain. In order to obtain a token which is not native to that chain, the DEX must be used in combination with a **bridge**.
To solve the centralization problems with CEXs, decentralized exchanges (DEXs) were created. A DEX operates inside a smart contract runtime and can be as decentralized as the blockchain it runs on. Unfortunately, a DEX is only able to utilize the tokens on its native blockchain. In order to obtain a token that is not native to that chain, the DEX must be used in combination with a **bridge**.
**Bridges** are complex and will be discussed at length in a later section. For now, we can categorize bridges as applications which 'lock' assets on one chain in exchange for **wrapped assets** on another chain. The wrapped assets can then be exchanged for the original 'backing' asset.
**Bridges** are complex and will be discussed at length in a later section. For now, we can categorize bridges as applications that 'lock' assets on one chain in exchange for **wrapped assets** on another chain. The wrapped assets can then be exchanged for the original 'backing' asset.
There are some other essential things you should know about bridges before going further:
- Bridges are capable of being decentralized in theory, but every Bridge has its own trust and security assumptions as its impossibl to make a truelly trustless bridge.
- Bridges are currently the one of the ways to hold a token on a chain other than its 'native' chain. If you're holding ETH on a chain other than Ethereum, it is, by definition, a wrapped token that represents the value of ETH on some other chain and uses vaults/ smart contracts to derive the value.
- Bridges are all mutually incompatible with each other. Using multiple bridges just makes 'double wrapped' tokens.
- If tokens have become double wrapped after traversing multiple bridges or blockchains, there can be a complex unwrapping process to get back to the original token but its improtant to make sure the check the wrapped asset contracts to make sure the mint-burn mechanism works.
- Bridges are capable of being decentralized in theory, but every Bridge has its own trust and security assumptions as its impossible to make a truly trustless bridge.
- Bridges are currently one of the ways to hold a token on a chain other than its 'native' chain. If you're holding ETH on a chain other than Ethereum, it is, by definition, a wrapped token that represents the value of ETH on some other chain and uses vaults/ smart contracts to derive the value.
- Bridges are all mutually incompatible with each other. Using multiple bridges just makes 'double-wrapped' tokens.
- If tokens have become double wrapped after traversing multiple bridges or blockchains, there can be a complex unwrapping process to get back to the original token but it's important to make sure check the wrapped asset contracts to make sure the mint-burn mechanism works.
This explains how the ecosystem arrived at its current state -- CEXs are a solution to siloed blockchains, DEXs are a simple response to CEXs, and DEXs have created a demand for bridges. Each solution in this timeline is an ad-hoc patch to the previous problem, and the current landscape of fractured liquidity, double wrapped tokens, isolated user bases and wallet incompatibilities is the result.
This explains how the ecosystem arrived at its current state -- CEXs are a solution to siloed blockchains, DEXs are a simple response to CEXs, and DEXs have created a demand for bridges. Each solution in this timeline is an ad-hoc patch to the previous problem, and the current landscape of fractured liquidity, double-wrapped tokens, isolated user bases, and wallet incompatibilities is the result.
Adding to this complexity are blockchains moving toward being general-purpose computing platforms. As such, interoperability will require data structures that are more complex than tokens and operations that are more sophisticated than transfers.
More ad-hoc solutions would only be short-term fixes for long-term problems, so it's critical to design new primitives and core infrastructure that will allow the next generation of decentralized applications to move beyond these lingering limitations.
This is why Wormhole exists. Wormhole proposes a new way of developing applications which leverages the strengths of each blockchain while mitigating the problems of the current ecosystem improving the user experince by abstracting their interactions from the chaint to the dapp.
This is why Wormhole exists. Wormhole proposes a new way of developing applications that leverages the strengths of each blockchain while mitigating the problems of the current ecosystem improving the user experience by abstracting their interactions from the chain to the dapp.
---
Rethinking the next generation of decentralized applications means dethroning the token as the fundamental atomic unit of blockchains but focusing on cross chain interoperability.
Rethinking the next generation of decentralized applications means dethroning the token as the fundamental atomic unit of blockchains but focusing on cross-chain interoperability.
We'll expand on this change in the next section.