\t\t\t\t\t\t\t\t![](\"https:\/\/statics.ambcrypto.com\/wp-content\/uploads\/2023\/03\/IMG-9126-scaled-e1677641698928-80x80.jpg\")
<\/p>\n
Journalist<\/p>\n<\/p><\/div>\n
\t\t\t\t\t\t\t\tPosted: September 30, 2023 \t\t\t\t\t\t On 28 September, <\/span>Ethereum\u2019s [ETH]<\/span><\/a> lead developer Tim Beiko provided an update on the upcoming Dencun upgrade. According to Beiko, there was an All Core Developer Execution (ACDE) meeting. During the meeting, participants talked about various subjects and added some touches to the already-existing development.<\/span><\/p>\n To test that, and to have a devnet with a large enough validator count to trigger EIP-7514, we\u2019ll launch a short-lived devnet-10 after devnet-9. Having a large validator set there will allow us to test the new churn limits.<\/p>\n \u2014 timbeiko.eth \u2600\ufe0f (@TimBeiko) September 28, 2023<\/a><\/p>\n<\/blockquote>\n To be clear, the Dencun upgrade came up as an avenue to bring changes across Ethereum\u2019s two Mainnet layers. This is the execution layer, which oversees smart contract execution, and the consensus layer, centered on blockchain consensus via staking.\u00a0<\/span><\/p>\n Read <\/span>Ethereum\u2019s [ETH] Price Prediction<\/span><\/a> 2023-2024<\/span><\/p>\n Beiko mentioned that there were some audits for the EIP-4788 contract during the meeting. For context, the EIP-4788 is the hash tree root in the Beacon Chain that allows verification of data from the consensus layer.<\/span><\/p>\n Two weeks ago, Beiko also shared some updates regarding the Dencun upgrade. But as of then, he <\/span>focused<\/span><\/a> on improving validator schemes and deploying nodes.<\/span><\/p>\n This time, the developer gave more information on the changes made which are also vital to the Beacon Chain users. He mentioned that the changes would allow contracts on the Beacon roots to be future-proof against block times. Beiko confirmed that other development firms apart from the Ethereum Foundation mentioned that there were no new issues with the contract.<\/span><\/p>\n \u201cBoth ChainSecurity and Dedaub had representatives on the call and confirmed that no other issues had been brought up since the two mentioned in the initial review, which we covered previously.\u201d<\/span><\/p>\n<\/blockquote>\n Furthermore, Beiko mentioned that there were other activities that included testing the MEV-Boost. Known as the Maximal Extractable Value, the MEV-Boost is a middleware developed to allow <\/span>validators<\/span><\/a> to request blocks from a network of builders.<\/span><\/p>\n However, Beiko mentioned that a large number of validators, development, and networking specialists to get the Boost to function on the Ethereum Mainnet as desired. He said,\u00a0<\/span><\/p>\n \u201cTo test that, and to have a devnet with a large enough validator count to trigger EIP-7514, we\u2019ll launch a short-lived devnet-10 after devnet-9. Having a large validator set there will allow us to test the new churn limits.\u201d<\/span><\/p>\n<\/blockquote>\n Other topics discussed included whether Ethereum L1 Mainnet should be Zero-Knowledge (ZK) friendly. Beiko disclosed that the developers all agreed that it wasn\u2019t something to hastily decide. Also, some were not sure if the functionality is something that Ethereum should have.<\/span><\/p>\n
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span><\/p>\n<\/p><\/div>\n
<\/p>\n\n
\n
\n
\nNo more troubles<\/h4>\n
\n
Next up is a difficult discussion<\/h4>\n
\n
\n