You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cdk/architecture/ulxly-stb.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The ability to manage bridge reserves is crucial to implement restaking for yiel
29
29
30
30
## Introducing "Stake the Bridge"
31
31
32
-
**Stake the Bridge**, or **STB**, is a feature that lets CDK chain operators maintain control over the assets that are deposited to their respective networks.
32
+
Stake the Bridge, or **STB**, is a feature that lets CDK chain operators maintain control over the assets that are deposited to their respective networks.
33
33
34
34
### Design and implementation
35
35
@@ -39,7 +39,7 @@ On L2 (the CDK chain), there are three components needed to make this work:
39
39
40
40
-[`L2Token`](https://github.com/pyk/zkevm-stb/blob/main/src/L2Token.sol), which is a natively deployed ERC20 contract.
41
41
-[`L2Escrow`](https://github.com/pyk/zkevm-stb/blob/main/src/L2Escrow.sol), a contract that manages the L2Token's supply.
42
-
-**[`L2TokenConverter`](https://github.com/pyk/zkevm-stb/blob/main/src/L2TokenConverter.sol), the contract that enables converting bridge-wrapped tokens to natively-minted tokens on L2.
42
+
-[`L2TokenConverter`](https://github.com/pyk/zkevm-stb/blob/main/src/L2TokenConverter.sol), the contract that enables converting bridge-wrapped tokens to natively-minted tokens on L2.
43
43
44
44
!!! info
45
45
@@ -89,8 +89,8 @@ With the STB contracts set up on L1 and L2 for a particular CDK chain, the bridg
89
89
90
90
The diagram above illustrates the following flow:
91
91
92
-
1. A user initiates a **USDC** deposit from L1 to L2.
93
-
2. Instead of being deposited directly to the unified bridge, the **USDC** is deposited into the STB `L1Escrow` contract.
92
+
1. A user initiates a USDC deposit from L1 to L2.
93
+
2. Instead of being deposited directly to the unified bridge, the USDC is deposited into the STB `L1Escrow` contract.
94
94
3. The STB `L1Escrow` locks the USDC and passes a message to the unified messenger containing the user’s address and amount of USDC being bridged.
95
95
4. The `Messenger` contract validates the message and then sends it to the STB `L2Escrow`.
96
96
5. The STB `L2Escrow` receives the message and mints USDC.e from the `L2Token` contract.
@@ -103,7 +103,7 @@ With the introduction of STB, there are now two ways to deposit tokens to an L2
103
103
- The STB flow involves locking tokens in the L1Escrow contract, which is followed by the minting of USDC.e on L2.
104
104
- On the other hand, if the tokens are deposited directly into the LxLy bridge contract, it results in the minting of LxLy USDC on L2.
105
105
106
-
The `L2TokenConverter` facilitates conversion between **USDC.e** and **LxLy USDC**. The way it works is by locking (Deposit function) either of the tokens in the converter contract, and then sending (Withdraw function) the equivalent amount of the other token to the user's wallet.
106
+
The `L2TokenConverter` facilitates conversion between USDC.e and LxLy USDC. The way it works is by locking (`Deposit` function) either of the tokens in the converter contract, and then sending (`Withdraw` function) the equivalent amount of the other token to the user's wallet.
0 commit comments