v4.2.0-mainnet

This release support Fusaka upgrade. Please upgrade before 2025-12-03, 21:49 UTC.

Upgrade steps:

1. Run cd dvf
2. Run git pull to update files, especially docker-compose-operator-mev.yml, which will update the version of geth, mev-boost and lighthouse
3. Change IMAGE_TAG to v4.2.0-mainnet in .env file
4. Upgrade geth: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d geth
5. Upgrade mev-boost: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d mev-boost
6. Upgrade lighthouse: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d lighthouse
7. Upgrade operator: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d operator

v4.1.1-mainnet

This release fix issues related to cluster node and operator stuck when ip changes.

Upgrade steps:

1. Run cd dvf
2. Change IMAGE_TAG to v4.1.1-mainnet in .env file
3. Upgrade the operator: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d operator

v4.1.0-mainnet

This release support cluster node and Pectra upgrade. Please upgrade before May 07 2025 10:05:11 UTC.

Upgrade steps:

1. Run cd dvf
2. Run git pull to update files, especially docker-compose-operator-mev.yml, which will update the version of geth, mev-boost and lighthouse
3. Change IMAGE_TAG to v4.1.0-mainnet in .env file
4. Upgrade geth: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d geth
5. Upgrade mev-boost: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d mev-boost
6. Upgrade lighthouse: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d lighthouse
7. Upgrade operator: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d operator

Changes:

1. Support cluster node and use DKG to generate validators.
2. Support Pectra upgrade.
3. Compress the data communicated between operators to improve communication efficiency.

v4.0.0-mainnet

This release contains breaking changes that are not compatible with v3.x.x. We will coordinate active operators in private mainnet to do this upgrade together at the same time to minimize the validator downtime.

Upgrade steps:

1. Run cd dvf
2. Run git pull to update files, especially docker-compose-operator-mev.yml
3. Change IMAGE_TAG to v4.0.0-mainnet in .env file
4. Add CLUSTER_CONTRACT_ADDRESS=f0455Aca6B61109098562610e89C7ca22c12Bb43 in .env file
5. Change WS_URL to RPC_URL and use the http endpoint instead of the websocket endpoint of the EL client.
6. Recreate the operator: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d operator

Changes:

1. Improved the communication protocol between operators by using grpc.
2. Refactored the internal logic of the operator to reduce memory usage.
3. Optimized the implementation for running multiple validators by reducing the use of locks, which makes the performance of operator improve a lot.
4. Supported the latest version of lighthouse (v6.0.1) and improved the version management of lighthouse submodule.
5. Updated some dependent libraries, such as using alloy to replace ether.

v3.5.0-mainnet

This release support custom fee recipient address for private mainnet.

Upgrade steps:

1. Run cd dvf
2. Run git pull to update files, especially docker-compose-operator-mev.yml
3. Change IMAGE_TAG to v3.5.0-mainnet in .env file
4. Add CONFIG_CONTRACT_ADDRESS=07FA0F7f3C67e4cdE0FC23A072dcD712CF9a06C1 in .env file
5. Recreate the operator: sudo docker compose -f docker-compose-operator-mev.yml up --force-recreate -d operator

Note: Users need to register validators and then set fee recipient address in the "my account" page. Fee recipient addresses will be set as the same under one owner address.

v3.4.0-mainnet

This release fixed some issues and support private mainnet.

Changes:

1. Support lighthouse v5.3
2. Optimized the logic of operator committee leader selection
3. Fixed the problem of proposal task
4. Optimized p2p node discovery and fixed the problem of cluster IP cache

v3.2.3-testnet

This release fixed some issues on the current holesky testnet.

Upgrade steps:

1. Run cd dvf
2. Change IMAGE_TAG to v3.2.3-testnet in .env file
3. Run the command to recreate the operator: sudo docker compose -f docker-compose-operator.yml up --force-recreate -d operator

Changes:

1. Support lighthouse 5.2.1
2. Optimized the operator committee restart logic
3. Optimized the MEV registration timestamp setting, using the timestamp when validator is registered on the platform
4. Removed the restriction of p2p outbound port, it will be easier for home stakers to set up when using the default port
5. Added a network environment debugging tool

v3.2.2-testnet

This release fixed some issues on the current holesky testnet.

Upgrade steps:

1. Run cd dvf
2. Change IMAGE_TAG to v3.2.2-testnet in .env file
3. Run the command to recreate the operator: sudo docker compose -f docker-compose-operator.yml up --force-recreate -d operator

Changes:

1. Fix the issue that network connections are not released.
2. Optimize the logic of monitoring public IP changes.
3. Remove the memory limit of operator in docker compose file.

v3.2.1-testnet

This release should fix the timeout issue in many operators and increase the performance of operators.

Upgrade steps:

1. Run cd dvf
2. Change IMAGE_TAG to v3.2.1-testnet in .env file
3. Run the command to recreate the operator: sudo docker compose -f docker-compose-operator.yml up --force-recreate -d operator

v3.2-testnet

This release added some major updates in operator code so contract addresses are changed and testnet is relaunched.

Upgrade steps:
you need to run the below commands to stop operator and delete old data:

sudo docker stop dvf-operator-1
sudo rm -rf /data/operator

then follow the operator document to run your operator from scratch. You don't need to recreate geth and lighthouse but can consider upgrade them to the latest version. You can remove the dvf directory and git clone to dvf again because contract addresses are changed.

Changes:

1. Support committe size of 7.
2. Support customizing the base port.
3. Add node_key_hex.json.
4. Change boot node enrs.
5. Change some logs to debug level.