From f334fb2eb45ae2dd69e61040126f5887e7e58b35 Mon Sep 17 00:00:00 2001 From: Ahmed Castro Date: Tue, 12 Sep 2023 15:57:18 -0600 Subject: [PATCH 1/2] Update bridge-erc20-through-the-custom-gateway.mdx Fixed wrong address --- .../guides/bridge-erc20-through-the-custom-gateway.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx b/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx index 866bfe17..5d1d7558 100644 --- a/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx +++ b/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx @@ -40,10 +40,10 @@ Next, launch you'll launch a counterpart to this token on Scroll, which will rep For this to work: -- The token must implement the `IScrollStandardERC20`` interface in order to be compatible with the bridge. +- The token must implement the `IScrollStandardERC20` interface in order to be compatible with the bridge. - The contract should provide the gateway address and the counterpart token addresses (the L1 token we just launched) under the `gateway()` and `counterpart()` functions. It should also allow the L2 gateway to call the token `mint()` and `burn()` functions, which are called when a token is deposited and withdrawn. -The following is a complete example of a token compatible with the bridge. To the constructor, you will pass the official Scroll Custom Gateway address (`0x31C994F2017E71b82fd4D8118F140c81215bbb37`) and the address of the token launched on Sepolia. +The following is a complete example of a token compatible with the bridge. To the constructor, you will pass the official Scroll Custom Gateway address (`0x058dec71E53079F9ED053F3a0bBca877F6f3eAcf`) and the address of the token launched on Sepolia. ```solidity // SPDX-License-Identifier: MIT From 6b2374dda67e00e510e199ca671f205aa6f533b9 Mon Sep 17 00:00:00 2001 From: Ahmed Castro Date: Tue, 12 Sep 2023 16:03:35 -0600 Subject: [PATCH 2/2] Update bridge-erc20-through-the-custom-gateway.mdx --- .../guides/bridge-erc20-through-the-custom-gateway.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx b/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx index 5d1d7558..70a9b35f 100644 --- a/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx +++ b/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx @@ -36,7 +36,7 @@ contract L1Token is ERC20 { ## Step 2: Launch the counterpart token on Scroll Sepolia testnet -Next, launch you'll launch a counterpart to this token on Scroll, which will represent the original token on Sepolia. This token can implement custom logic to match that of the L1 token or even add additional features beyond those of the L1 token. +Next, you'll launch a counterpart to this token on Scroll, which will represent the original token on Sepolia. This token can implement custom logic to match that of the L1 token or even add additional features beyond those of the L1 token. For this to work: