Skip to content

Commit f0daa52

Browse files
committed
Update ulxly-stb.md
Minor updates
1 parent a517f2e commit f0daa52

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/cdk/architecture/ulxly-stb.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The ability to manage bridge reserves is crucial to implement restaking for yiel
2929

3030
## Introducing "Stake the Bridge"
3131

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.
3333

3434
### Design and implementation
3535

@@ -39,7 +39,7 @@ On L2 (the CDK chain), there are three components needed to make this work:
3939

4040
- [`L2Token`](https://github.com/pyk/zkevm-stb/blob/main/src/L2Token.sol), which is a natively deployed ERC20 contract.
4141
- [`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.
4343

4444
!!! info
4545

@@ -89,8 +89,8 @@ With the STB contracts set up on L1 and L2 for a particular CDK chain, the bridg
8989

9090
The diagram above illustrates the following flow:
9191

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.
9494
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.
9595
4. The `Messenger` contract validates the message and then sends it to the STB `L2Escrow`.
9696
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
103103
- The STB flow involves locking tokens in the L1Escrow contract, which is followed by the minting of USDC.e on L2.
104104
- 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.
105105

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.
107107

108108
## Using the STB contracts
109109

0 commit comments

Comments
 (0)