From ecca21dce987ef6982fefee5059f5997511dfcfc Mon Sep 17 00:00:00 2001 From: gmehta2 <39961155+gmehta2@users.noreply.github.com> Date: Thu, 17 Jul 2025 09:38:22 -0400 Subject: [PATCH 1/2] Update 02-set-up-aep-fee-router.mdx --- .../aep-fee-router/02-set-up-aep-fee-router.mdx | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx index b2a501b2ba..507d95edc2 100644 --- a/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx +++ b/arbitrum-docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx @@ -55,11 +55,6 @@ This includes: In the event that a `ChildToParentRouter` does not connect to the address controlled by the Arbitrum Foundation on Ethereum, an Arbitrum chain must deploy successive `ChildToParentRouter` contracts until a connection to such address is established. Additional `ChildToParentRouter` contracts configured to route ETH have been deployed in certain networks and can be leveraged by chains created on top of these networks. You can [see which networks have a router deployed](#canonical-contracts). - -Layer-3 chains with custom gas tokens with L2-based token contracts cannot send their custom gas tokens to Ethereum. A future version of the AEP Fee Router may allow Arbitrum chains with L2-based tokens to distribute fees using the routing system. - -In the absence of these, please send `ETH` through the AEP Fee Router to fulfill your AEP license obligations. - Here are a few flows to help visualize the deployment: @@ -80,7 +75,7 @@ The Arbitrum chain (Orbit) SDK provides a [configurable script](https://github.c The standard script deploys and sets up the AEP fee router contracts to route funds to the parent chain. -L2 chains are expected to route funds to the [multisig wallet owned by the Arbitrum Foundation](#canonical-contracts) living on Ethereum. +L2 chains are expected to route funds to the [multisig wallet owned by the Arbitrum Foundation](#canonical-contracts) on Ethereum. L3 chains (or further layers) might need to specify a different target address on the parent chain depending on the gas token of the chain. If the chain uses `ETH` as the gas token, and a [ChildToParentRouter](#canonical-contracts) contract is deployed in the parent chain, they can route their funds to that contract. If the chain uses a different gas token, please contact the Arbitrum Foundation to confirm the target address to withdraw the AEP fees to. From 3c40c76e56f7b5448c19f5eb19d89aedd8fc5b4a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ga=C3=ABl=20Blanchemain?= Date: Tue, 5 Aug 2025 18:45:32 -0700 Subject: [PATCH 2/2] fix malformed admonition in AEP Fee Router guide --- .../aep-fee-router/02-set-up-aep-fee-router.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx b/docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx index 507d95edc2..ca79deb0ab 100644 --- a/docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx +++ b/docs/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx @@ -55,8 +55,6 @@ This includes: In the event that a `ChildToParentRouter` does not connect to the address controlled by the Arbitrum Foundation on Ethereum, an Arbitrum chain must deploy successive `ChildToParentRouter` contracts until a connection to such address is established. Additional `ChildToParentRouter` contracts configured to route ETH have been deployed in certain networks and can be leveraged by chains created on top of these networks. You can [see which networks have a router deployed](#canonical-contracts). - - Here are a few flows to help visualize the deployment: