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.

v3.1-testnet

This release fixed the problem of querying future blocks and the timeout issue.

Upgrade steps:

1. Run cd dvf
2. Change IMAGE_TAG to v3.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.0-testnet

This release fixed a lot of major issues in holesky testnet so contract addresses are changed and holesky 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 contracts and configurations changed a lot.

Changes:

1. Updated MEV timestamp configuration. Now OP can enable MEV for test.
2. Adapt to SafeStake contract v3.
3. Added the function of status reporting to backend.
4. Increased the frequency of smart contract event query.
5. Fixed the bug of occasional failure to decrypt key share.

v2.2-testnet

This release fixed an issue that operator node failed to get the latest events from smart contract, which made some newly registered validator inactive. Operators need to upgrade to this version as soon as possible.

Upgrade Steps

cd dvf
git pull
# then update IMAGE_TAG to v2.2-testnet in .env
nano .env
sudo docker compose -f docker-compose-operator.yml up --force-recreate -d operator

v2.1-testnet

This release is for Dencun upgrade on both Holesky and Goerli testnet. Operators running on Holesky need to upgrade before Feb 7 2024 @ 11:34:24 (GMT+0).
Geth version: v1.13.11
Lighthouse version: v4.6.0
Operator version: v2.1-testnet

Upgrade Steps

cd dvf
git pull
# then update IMAGE_TAG to v2.1-testnet in .env
nano .env
sudo docker compose -f docker-compose-operator.yml up geth -d
sudo docker compose -f docker-compose-operator.yml up lighthouse -d
sudo docker compose -f docker-compose-operator.yml up --force-recreate -d operator

Other changes:

1. MEV_IP is now changed to MEV_ENDPOINT (should include port) in .env.
2. NODE_IP is now recommended to set in .env for your machine's public ipv4 ip.
3. FEE_RECEIPIENT is now removed in .env. Instead of setting it in operator level, it will be set in the validator level. Execution layer reward will be transferred to the address that registered the validator.