Preparing for the Dencun Fork
Necessary arrangements for the coming network upgrade.
The Decun hard fork is coming for Ethereum clients, including refinements and proto-danksharding, bringing rollup scalability and reduced transaction costs. The update is planned for Ethereum on March 13th. For LUKSO, we plan to enable this feature collaboratively around a month later, beginning with the LUKSO Testnet. The schedule will allow us to guarantee a seamless update experience for everyone and include the latest stability improvements.
How does it affect validators?
Most validators on LUKSO run the Prysm consensus client. If you run a higher Prysm version than 4.0.8, the client already supports the Dencun upgrade and expects new network parameters. If not set, the client returns to the default fork time for Ethereum, set above epoch 269,000. Prysm nodes on other L1 chains, such as LUKSO, must manually adjust these network configurations to match their timeline.
LUKSO is a younger network with a fork epoch of around 66,000, meaning the fork time should not intersect with Ethereum, and validators are expected to remain active. However, as we had to update the network configuration files present across all clients, heavier differences in versions and network configs might still cause local issues or potentially even reorgs and forks, affecting the overall network stability.
What do you have to do?
To be safe and eliminate the risk of nodes validating on an empty network branch, we highly recommend updating your node setups and getting the latest network configurations.
🤹 If you are using Dappnode
You automatically get the latest client versions installed via Auto-Updates. Updates for the clients always include the newest network configuration. If you turned off auto-updates or should run into issues, please visit the LUKSO Stakers page within Dappnode OS and re-install your clients by hand. Changes made to the clients won't affect validator keys within the Staking Brain.
📟 If you are using the LUKSO CLI
Please follow the Node Update Guide on our documentation. After stopping the node, it is as easy as three steps within the node directory:
Install the new LUKSO CLI Release v0.16:
curl https://install.lukso.network | shUpdate the client versions to the latest supported releases:
sudo lukso updateDownload the latest network configuration:
sudo lukso update configs
After maintenance is completed, simply restart your node.
🔧 If you are running 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:
Install the latest supported client versions.
Execution Releases:
Consensus Releases:
Apply the new network configuration files from GitHub.
Next steps
Upon the Dencun Fork on Ethereum and its aftermath, we will orchestrate the hard fork on the LUKSO Testnet. After those steps are successful, a specific fork date will be announced for LUKSO Mainnet, including all mandatory steps for validators.