Testnet v0.3.2

This network update brings about the following changes:

• Reduces the amount of data published to L1 Ethereum using EigenLayer

• Lower transactions fees on L2

For more details on how the aforementioned features were included to the codebase, follow the links below to navigate to the Mantle GitHub repo.

GitHub Links

1. Changelog: https://github.com/mantlenetworkio/mantle/releases

2. Pull request with upgrades: https://github.com/mantlenetworkio/networks/pull/7

Instructions for Node Operators

This update includes changes that will effect take once you sync your node using the updated Docker image. Follow the steps below to proceed.

1. Modify the DTL configuration in docker-compose.yaml

• Update the image. You can do this by either adding DOCKER_TAG_DATA_TRANSPORT_LAYER = 0.3.2 in goerli/env/dtl.env, or updating image to mantlenetworkio/data-transport-layer: 0.3.2

• Add the following attributes: DATA_TRANSPORT_LAYER__EIGEN_UPGRADE_ENABLE: true and DATA_TRANSPORT_LAYER__SYNC_TO_DA: false

• Add a new element as shown below.

volume:
  volumes:
    - ./data/db:/db

2. Modify the verifer or replica setting in docker-compose.yaml

• Set image version to image: mantlenetworkio/l2geth: 0.3.2

• Add the following attribute: ROLLUP_EIGEN_DA_BLOCK: "8280000"

3. Check node height

If your current node height happens to be higher than 8280000, which is the block height for this update, you'll need to download the backup data from the previous day and extract it, and then use it to replace your node's chaindata. For instance, if you're performing this action on 2023-05-25, you download the data from 2023-05-24 using the following link:

https://s3.ap-southeast-1.amazonaws.com/static.testnet.mantle.xyz/20230524-testnet-chaindata.tar

Make sure to update the date in the URL based on your current date before starting the download. Also, the data directory depends on your local configuration. It should be of the form ./data/verifier/chaindata

4. Sync node

Run the following command and wait for your node to complete the sync.

docker-compose up --force-recreate -d

Deploying a New Node Instance

If you encounter issues updating your node version with the process described above, you'll need to use the previous day's snapshot and deploy a new node instance. Follow the steps below to do that.

1. Configure DTL

If you're going to run a new node instance, you can just use Mantle's public DTL service to sync chain data. Use the docker-compose.replica.yml file from this pull request.

2. Check node height

You'll still need to download the backup data from the previous day, extract it, and then use it to replace your node's chaindata. For instance, if you're performing this action on 2023-05-25, you download the data from 2023-05-24 using the following link:

https://s3.ap-southeast-1.amazonaws.com/static.testnet.mantle.xyz/20230524-testnet-chaindata.tar

Make sure to update the date in the URL based on your current date before starting the download. Also, the data directory depends on your local configuration. It should be of the form ./data/verifier/chaindata

3. Run node

You'll need to download the docker-compose.replica.yml file to spin your new node instance. Once you've download the file from here, run the following command to start your node and sync it.

docker-compose -f docker-compose.replica.yml up -d