LUKSO Dencun Hard Fork - MAINNET

🚨 ACTION REQUIRED by node operators and validators of the LUKSO Mainnet

Oct 03, 2024

What is happening?

We ask all Mainnet node operators and validators to implement the Dencun hard fork on their LUKSO Mainnet nodes.

After having a successful Hard Fork on LUKSO Testnet, it is now Mainnet’s turn to apply the latest updates.

The Dencun hard fork for the LUKSO Mainnet is scheduled for:

Nov. 20th, 2024 at 4:20 pm GMT

What do you have to do?

If you are a node operator or a validator on the LUKSO Mainnet, you must update your clients to the latest supported versions and apply updates to your network configuration.

We suggest applying all updates before Nov. 15, 2024, to give you enough time to see your setup running smoothly.

At the end of this post, you find guides for the LUKSO CLI and docker containers, but to summarize you need to do two things:

You need to upgrade your clients to one of the following versions, or above:

Execution Releases:

Consensus Releases:

You then need to update your network config files for the LUKSO Mainnet, specifically the genesis.json and the config.yaml in your config/mainnet/shared/ (config/mainnet/teku | config/mainnet/nethermind when running Teku or Nethermind client) folder:
👨‍💻 See GitHub pull request

genesis.json

...
  "config": {
    ...


    "cancunTime": 1732119595
  },
...

config.yaml

# Forks
# ---------------------------------------------------------------
...

# Deneb
# Date and time (GMT): Wednesday, 20 November 2024 16:20:00
DENEB_FORK_VERSION: 0x42000005
DENEB_FORK_EPOCH: 123075
...

You can then restart your nodes and your system should be ready for the hard fork!

📟 Upgrade using the LUKSO CLI

Please also follow the Node Update Guide if you use a CLI version below 0.8. You will have to move into the node directory, stop the node, and follow these steps:

Install the new LUKSO CLI Release v0.21.1:

curl https://install.lukso.network | sh

Update the client versions to the latest supported releases:

lukso update

Download the latest network configuration:

lukso update configs

You will be able to verify your configuration changes and the availability of your client for the hard fork:

After maintenance is completed, restart your node:

lukso start

As a validator, remember to keep your command flags the same as before stopping:

lukso start --validator --transaction-fee-recipient "<your address>"

📦 Upgrade using the LUKSO Dappnode

Users can receive updates either through the system's auto-update feature or manually after being notified of an available update.

For auto-updates, users should ensure the feature is active for the LUKSO Mainnet network. For manual updates, users will receive a notification within the system dashboard once Dappnode publishes and releases the update. They can then choose to update immediately or postpone it.

It is recommended to prepare your device for the fork as soon as possible by updating it with the LUKSO packages (Geth and Prysm).

The following package versions will be released for the Dencun fork:

prysm-lukso.dnp.dappnode.eth v0.1.2
lukso-geth.dnp.dappnode.eth v0.1.3
teku-lukso.dnp.dappnode.eth v0.1.2

Based on information from Dappnode, updates for end-user devices will be distributed in phases. This means users won't all receive the update simultaneously.

🐳 Upgrade using a docker setup

Docker containers repository:

Ensure that you are using latest docker-compose file (by comparing your file with one in the repository)
Copy client versions from .env.mainnet file into your .env file
Update your config.yaml and genesis.json configs with the LUKSO Mainnet ones in the network-configs repository.

Docker Factory repository

Generate a new docker-compose file using the docker factory 🏭 and replace the old file with a new one
Update your config.yaml and genesis.json configs with the LUKSO Mainnet ones in the network-configs repository.

🔧 Upgrade on a custom setup

Please manually download and configure your node based on the latest executables and configurations for your client setups, customized containers, or service.

The Besu and Teku software includes the LUKSO Mainnet network in its implementation. If using this software, it is essential to update it immediately to the latest version, which has implemented the Dencun fork specification for the LUKSO Mainnet.

If you have any questions, please do not hesitate to contact us through the channel below.

LUKSO Discord #validators-chat Channel