6. 使用自定义ERC20通证作为Layer2的原生通证

前言

前几章介绍的部署方式都是将Layer1的原生通证跨链映射到Layer2，同时作为Layer2的原生通证，其实CDK还支持将Layer1的ERC20通证映射为Layer2的原生通证。

---

部署

我们仍然按照第四章的方式进行部署，只是部署前需要将kurtosis-cdk目录下params.yml配置文件的第157行zkevm_use_gas_token_contract参数的值改为true，这样部署时CDK会自动在Layer1部署一个ERC20通证，部署完成后控制台打印的服务详情如下：

========================================== User Services ==========================================
UUID           Name                             Ports                                                     Status
8ab8eb1a3bab   contracts-001                    <none>                                                    RUNNING
104d02483025   grafana-001                      dashboards: 3000/tcp -> http://127.0.0.1:32804            RUNNING
a7cda3c61642   panoptichain-001                 prometheus: 9090/tcp -> http://127.0.0.1:32802            RUNNING
1a9ee4f615bd   postgres-001                     postgres: 5432/tcp -> postgresql://127.0.0.1:32773        RUNNING
5c72f162de2f   prometheus-001                   http: 9090/tcp -> http://127.0.0.1:32803                  RUNNING
ea415ba34e8b   zkevm-agglayer-001               agglayer: 4444/tcp -> http://127.0.0.1:32799              RUNNING
                                                prometheus: 9091/tcp -> http://127.0.0.1:32798
e16471326940   zkevm-bridge-proxy-001           web-ui: 80/tcp -> http://127.0.0.1:32801                  RUNNING
1a2352d60d13   zkevm-bridge-service-001         grpc: 9090/tcp -> grpc://127.0.0.1:32796                  RUNNING
                                                rpc: 8080/tcp -> http://127.0.0.1:32797
418a9b0f93d4   zkevm-bridge-ui-001              web-ui: 80/tcp -> http://127.0.0.1:32800                  RUNNING
7aec6e656c43   zkevm-dac-001                    dac: 8484/tcp -> http://127.0.0.1:32795                   RUNNING
4a4060b41b31   zkevm-node-aggregator-001        aggregator: 50081/tcp -> grpc://127.0.0.1:32778           RUNNING
                                                pprof: 6060/tcp -