LUKSO Dencun Hard Fork - TESTNET

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

Sep 02, 2024

What is happening?

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

The Dencun hard fork is the latest upgrade for Ethereum clients, bringing many general improvements and proto-danksharding. It is the next iteration for EVM blockchains, bringing rollup scalability and reduced transaction costs. With this update, we are moving along with the proposed Ethereum improvements.

The fork on Ethereum on March 13th was successfully applied and runs successfully on the Ethereum Mainnet. To test the fork we applied the Dencun hard fork on our internal Devnet on March 21st.

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

Sep. 18th, 2024 at 4:20pm GMT

What do you have to do?

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

We suggest applying all updates before Sep. 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 TESTNET, specifically the genesis.json and the config.yaml in your config/testnet/shared/ (config/testnet/teku | config/testnet/nethermind when running Teku or Nethermind client) folder:
👨‍💻 See GitHub pull request

genesis.json

{
  "config": {
    ...

    "cancunTime": 1726676395
  },
  ...
}

config.yaml

...

# Forks
# ---------------------------------------------------------------

...

# Deneb
# GMT: Wednesday, 18 September 2024 16:20:00
DENEB_FORK_VERSION: 0x42010005
DENEB_FORK_EPOCH: 113400

...

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.20.0:

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

After maintenance is completed, restart your node.

lukso start

🐳 Upgrade using a docker setup

Docker containers repository

1) Ensure that you are using latest docker-compose file (by comparing your file with one in the repository)

2) Copy client versions from .env.testnet file into your .env file

3) Update your config.yaml and genesis.json configs with the LUKSO Testnet ones in the network-configs repository.

Docker Factory repository

1) Generate a new docker-compose file using the docker factory 🏭 and replace the old file with a new one

2) Update your config.yaml and genesis.json configs with the LUKSO TESTNET 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 services.

Next steps

🔔 Once the Dencun Fork is successful on the LUKSO Testnet, we will orchestrate the upgrade on the LUKSO Mainnet. 🏞️

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

LUKSO Discord #validators-chat Channel