Vitalik Buterin reposted a development update from Ethereum client team Nethermind, saying the project continues to improve Ethereum’s efficiency and runtime performance. The update came from Nethermind core developer Ben Adams, who said the team’s Beacon Chain plugin has completed synchronization and is ready for the Glamsterdam fork on the Sepolia testnet. Adams also said that running Ethereum’s execution layer and consensus layer as a single application does not appear to introduce meaningful additional memory overhead. The timeline for the upgrade had already been set by the Ethereum Foundation, which previously confirmed that Glamsterdam would go live on Sepolia on Oct. 6. Nethermind version 2.1.0 already supports the upgrade, according to the update referenced in Buterin’s post. The remarks point to ongoing client-side work ahead of the scheduled Sepolia activation.
Vitalik Buterin reposted a Nethermind development update and said the client is continuing to improve Ethereum’s efficiency and runtime performance.
Ben Adams, a core developer at Nethermind, said the team’s Beacon Chain plugin has completed synchronization and is ready for the Glamsterdam fork on Sepolia. He also said that running Ethereum’s execution layer and consensus layer as a single application does not appear to add significant memory overhead.
Glamsterdam activation set for Oct. 6 on Sepolia
The Ethereum Foundation had previously confirmed that Glamsterdam would be activated on Sepolia on Oct. 6. Nethermind 2.1.0 already supports the upgrade.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
