From c31eb87bb3442f01a4737862499f4b442dc25a09 Mon Sep 17 00:00:00 2001 From: yanziseeker <153156292+AdventureSeeker987@users.noreply.github.com> Date: Tue, 30 Apr 2024 23:15:38 +0800 Subject: [PATCH] fix broken link --- Languages/en/02_zkSync/readme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Languages/en/02_zkSync/readme.md b/Languages/en/02_zkSync/readme.md index 160f5d1..2fefa71 100644 --- a/Languages/en/02_zkSync/readme.md +++ b/Languages/en/02_zkSync/readme.md @@ -123,7 +123,7 @@ You can use [zkSync official cross-chain bridge](https://portal.zksync.io/bridge Deposits from Ethereum mainnet to zkSync take approximately 15 minutes, while withdrawals from zkSync to Ethereum can take up to 24 hours. -Developers can also use zkSync's cross-chain bridge contracts in L1 and L2 to build custom cross-chain bridges, [Document](https://docs.zksync.io/build/developer-reference/bridging-asset.html#withdrawals -to-l1). +Developers can also use zkSync's cross-chain bridge contracts in L1 and L2 to build custom cross-chain bridges, [Document](https://docs.zksync.io/build/developer-reference/bridging-asset.html#withdrawals-to-l1). ## 5. Block explorer @@ -168,7 +168,7 @@ Developers can use Solidity or Vyper to develop smart contracts on zkSync, and m - Use upgradable contracts: The zkSync Era is still in the early stages of development, and although the team has conducted extensive testing to ensure EVM compatibility, issues may still arise. Therefore, when deploying contracts, you should try to use upgradable proxy contracts to deal with possible problems. If you don’t understand proxy contracts/upgradeable contracts, you can refer to the WTF Solidity tutorial [Lecture 48](https://github.com/AmazingAng/WTF-Solidity/blob/main/48_TransparentProxy/readme.md) and [Lecture 49 ](https://github.com/AmazingAng/WTF-Solidity/blob/main/49_UUPS/readme.md). -- Do not rely on EVM's gas logic: zkSync has its own set of gas logic, which is different from L1. For example, it will consider the gas consumption when data is published in L1. For details, please refer to [Document](https://docs.zksync.io/zk -stack/concepts/fee-mechanism.html). +- Do not rely on EVM's gas logic: zkSync has its own set of gas logic, which is different from L1. For example, it will consider the gas consumption when data is published in L1. For details, please refer to [Document](https://docs.zksync.io/zk-stack/concepts/fee-mechanism.html). ## 9. Summary