Skip to content

Commit 94e9e34

Browse files
authored
Merge pull request #11309 from Olanetsoft/patch-1
update general message passing bridges example
2 parents b76d5d0 + 0d98acf commit 94e9e34

File tree

1 file changed

+1
-1
lines changed
  • public/content/developers/docs/bridges

1 file changed

+1
-1
lines changed

public/content/developers/docs/bridges/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Bridges can usually be classified into one of the following buckets:
4242

4343
- **Native bridges –** These bridges are typically built to bootstrap liquidity on a particular blockchain, making it easier for users to move funds to the ecosystem. For example, the [Arbitrum Bridge](https://bridge.arbitrum.io/) is built to make it convenient for users to bridge from Ethereum Mainnet to Arbitrum. Other such bridges include Polygon PoS Bridge, [Optimism Gateway](https://app.optimism.io/bridge), etc.
4444
- **Validator or oracle based bridges –** These bridges rely on an external validator set or oracles to validate cross-chain transfers. Examples: Multichain and Across.
45-
- **Generalized message passing bridges –** These bridges can transfer assets, along with messages and arbitrary data across chains. Examples: Nomad and LayerZero.
45+
- **Generalized message passing bridges –** These bridges can transfer assets, along with messages and arbitrary data across chains. Examples: Axelar, LayerZero, and Nomad.
4646
- **Liquidity networks –** These bridges primarily focus on transferring assets from one chain to another via atomic swaps. Generally, they don’t support cross-chain message passing. Examples: Connext and Hop.
4747

4848
## Trade-offs to consider {#trade-offs}

0 commit comments

Comments
 (0)