Skip to content

Commit 931b390

Browse files
author
jarrodwatts
committed
bridging basics
1 parent 9fe5fe3 commit 931b390

File tree

3 files changed

+12
-5
lines changed

3 files changed

+12
-5
lines changed

docs/cdk/concepts/agglayer.md

Whitespace-only changes.

docs/cdk/concepts/bridging.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,17 @@
11
# Bridging
22

3-
[Bridges](https://ethereum.org/en/developers/docs/bridges/) are a fundamental component of L2s. They allow users to bridge funds from the L1 (Ethereum) seamlessly, to pay for gas fees or interact with dApps on the L2, and optionally bridge funds back to the L1.
3+
[Bridges](https://ethereum.org/en/developers/docs/bridges/) are a fundamental component of L2s. A core feature of chains built with the CDK is **interoperability**, which allows developers to access funds from Ethereum as well as other L2s when building dApps on your chain.
44

5-
CDK chains come with a built-in bridge service and customizable UI that enables users to move assets (both native and ERC20 tokens) between L1 and L2.
5+
## L1 <-> L2 Bridge
6+
7+
CDK chains come with a built-in bridge service and customizable UI that enables users to move assets (both native and ERC20 tokens) between L1 and L2 or between different L2s.
68

79
A key benefit to building ZK-powered L2s with the CDK is that there are no challenge periods unlike [optimistic rollups](./zk-vs-optimistic.md#optimistic-rollups), meaning users can move funds from the L2 to the L1 immediately after the [aggregation](./transaction-lifecycle.md#aggregated) process is complete (i.e. a ZK proof is posted & verified).
810

9-
![Bridge UI for CDK](../../img/cdk/bridge-ui.png)
11+
## Unified Bridge
12+
13+
By default, chains launched using the CDK are opt-in to the AggLayer, enabling cross-chain transactions via the unified bridge. The unified bridge enables cross-chain L2 to L2 transactions to other chains that have opted-in to the [AggLayer](https://polygon.technology/blog/aggregated-blockchains-a-new-thesis).
14+
15+
This allows developers to build unique cross-chain experiences by integrating a `bridgeAndCall` function into their smart contracts, enabling users to call smart contract functions on other L2 chains without requiring users to bridge or hold tokens on the target chain.
16+
17+
Learn more on the [zkEVM unified bridge documentation](https://docs.polygon.technology/zkEVM/architecture/protocol/unified-LxLy/ulxly-rollupmanager/).

mkdocs.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,7 @@ nav:
6363
- Transaction Lifecycle: cdk/concepts/transaction-lifecycle.md
6464
- Transaction Finality: cdk/concepts/transaction-finality.md
6565
- Gas Fees: cdk/concepts/gas-fees.md
66-
- Bridging: cdk/concepts/bridging.md
67-
- AggLayer & Interoperability: cdk/concepts/agglayer.md
66+
- Bridging & Interoperability: cdk/concepts/bridging.md
6867
- Admin Upgradeability: cdk/concepts/admin-upgradeability.md
6968
- Architecture:
7069
- CDK rollup: cdk/architecture/cdk-zkevm.md

0 commit comments

Comments
 (0)