Skip to content

Update 02-set-up-aep-fee-router.mdx #2474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

Update 02-set-up-aep-fee-router.mdx #2474

Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
ecca21d
Update 02-set-up-aep-fee-router.mdx
gmehta2 Jul 17, 2025
56fbd04
Merge branch 'master' into gmehta2-patch-10
pete-vielhaber Jul 21, 2025
8ca5792
Merge branch 'master' into gmehta2-patch-10
anegg0 Jul 22, 2025
dfffd90
Merge branch 'master' into gmehta2-patch-10
anegg0 Jul 22, 2025
c0fa84d
Merge branch 'master' into gmehta2-patch-10
anegg0 Jul 29, 2025
3ce1215
Merge branch 'master' into gmehta2-patch-10
anegg0 Aug 6, 2025
3c40c76
fix malformed admonition in AEP Fee Router guide
anegg0 Aug 6, 2025
cf74aec
Merge branch 'master' into gmehta2-patch-10
anegg0 Aug 6, 2025
c019d67
Merge branch 'master' into gmehta2-patch-10
anegg0 Aug 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions ...-your-chain/advanced-configurations/aep-fee-router/02-set-up-aep-fee-router.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,13 +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).

<VanillaAdmonition type="note" title="Note about custom gas tokens">
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.

</VanillaAdmonition>

Here are a few flows to help visualize the deployment:

<ImageZoom src="/img/arb-chain-aep-scenario-1.svg" alt="AEP scenario 1" className="img-800px" />
Expand All @@ -80,7 +73,7 @@ The Arbitrum chain (Orbit) SDK provides a [configurable script](https://github.c

<VanillaAdmonition type="info" title="Note for L3 chains with custom gas tokens">
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.

</VanillaAdmonition>
Expand Down