From faba02e2deb6aca05ec3e591eae393e625f7992c Mon Sep 17 00:00:00 2001 From: Sarah Schwartz <58856580+sarahschwartz@users.noreply.github.com> Date: Thu, 8 Aug 2024 13:06:52 -0600 Subject: [PATCH] docs: use allowlist --- .../tutorials/custom-zk-chain/20.customizing-your-chain.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/tutorials/custom-zk-chain/20.customizing-your-chain.md b/content/tutorials/custom-zk-chain/20.customizing-your-chain.md index 548c219d..24ced865 100644 --- a/content/tutorials/custom-zk-chain/20.customizing-your-chain.md +++ b/content/tutorials/custom-zk-chain/20.customizing-your-chain.md @@ -7,11 +7,11 @@ description: Create a ZK chain with a custom ERC20 base token. One way you can customize your ZK chain is by changing the base token used for gas from ETH to an ERC20 token. Let's try customizing a new chain by using a custom ERC20 base token. -With the initial release of ZK stack, base tokens must be whitelisted for use as a base token for a chain. -The whitelisted addresses are stored and checked in the `BridgeHub` contract on the L1. +With the initial release of ZK stack, custom ERC20 base tokens must be added to an allowlist for use as a base token for a chain. +The allowed addresses are stored and checked in the `BridgeHub` contract on the L1. In the future it will be possible to add a new token in a permissionless process. -For now, you have the ability to whitelist tokens in your local ecosystem. +For now, you have the ability to add any tokens to the allowlist in your local ecosystem. The overall flow for setting up a local chain with a custom ERC20 base token looks like this: