From dfaf02a387ca281536753928960a77bc993a781e Mon Sep 17 00:00:00 2001 From: Allan Date: Wed, 15 Oct 2025 09:47:29 -0500 Subject: [PATCH 1/3] clarify rollup CGT requirements --- .../common-configurations/02-use-a-custom-gas-token-rollup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx b/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx index bb00dccf3..c561cf2f2 100644 --- a/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx +++ b/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx @@ -19,7 +19,7 @@ When deploying an Arbitrum chain in [Rollup mode](/how-arbitrum-works/12-data-av Enabling a custom fee token for a Rollup chain requires additional configuration compared to an [AnyTrust chain](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/01-use-a-custom-gas-token-anytrust.mdx); it also introduces important exchange-rate considerations. This guide outlines specific implementation steps and operational considerations for chain owners or operators to consider when enabling a custom fee token for Rollups. ## Requirements of the custom gas token - +A key requirement for a custom gas token is that there is some representation on the parent chain. During chain deployment, the gas token is "natively bridged" and then properly configured as the native gas token on the Arbitrum chain. Additional requirements include: - Must be a standard `ERC-20` token - Transfers and approvals must occur directly via the token contract, not via proxies or hooks - Must not be rebasing or include transfer fees and From 829074d916dcc9cefdc244b0589f11f98875a81e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ga=C3=ABl=20Blanchemain?= Date: Wed, 15 Oct 2025 12:33:28 -0700 Subject: [PATCH 2/3] reformat --- .../common-configurations/02-use-a-custom-gas-token-rollup.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx b/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx index c561cf2f2..16797c365 100644 --- a/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx +++ b/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx @@ -19,7 +19,9 @@ When deploying an Arbitrum chain in [Rollup mode](/how-arbitrum-works/12-data-av Enabling a custom fee token for a Rollup chain requires additional configuration compared to an [AnyTrust chain](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/01-use-a-custom-gas-token-anytrust.mdx); it also introduces important exchange-rate considerations. This guide outlines specific implementation steps and operational considerations for chain owners or operators to consider when enabling a custom fee token for Rollups. ## Requirements of the custom gas token + A key requirement for a custom gas token is that there is some representation on the parent chain. During chain deployment, the gas token is "natively bridged" and then properly configured as the native gas token on the Arbitrum chain. Additional requirements include: + - Must be a standard `ERC-20` token - Transfers and approvals must occur directly via the token contract, not via proxies or hooks - Must not be rebasing or include transfer fees and From b854872b6cb6a207fcddea6f523ddcaaaa4d6ca4 Mon Sep 17 00:00:00 2001 From: Allan Date: Wed, 15 Oct 2025 14:36:15 -0500 Subject: [PATCH 3/3] Update docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Gaël Blanchemain --- .../common-configurations/02-use-a-custom-gas-token-rollup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx b/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx index 16797c365..662c06358 100644 --- a/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx +++ b/docs/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx @@ -20,7 +20,7 @@ Enabling a custom fee token for a Rollup chain requires additional configuration ## Requirements of the custom gas token -A key requirement for a custom gas token is that there is some representation on the parent chain. During chain deployment, the gas token is "natively bridged" and then properly configured as the native gas token on the Arbitrum chain. Additional requirements include: +A key requirement for a custom gas token is that it has a representation on the parent chain. During chain deployment, the gas token is "natively bridged" and then properly configured as the native gas token on the Arbitrum chain. Additional requirements include: - Must be a standard `ERC-20` token - Transfers and approvals must occur directly via the token contract, not via proxies or hooks