The latest developments in Ethereum's execution layer have arrived. At the 228th Core Developer Meeting(ACDE), the team discussed several important protocol upgrade proposals.
The most notable is EIP-7843 (slot opcode proposal). Since this proposal involves coordination issues between the consensus layer and execution layer, the team decided to postpone the relevant testing scope of BALs Devnet-2, pending further technical evaluation and design refinement.
On the other hand, the meeting officially rejected seven proposed EIPs from being included in the Glamsterdam upgrade plan. This means these proposals either need to be redesigned or may be delayed to future versions.
Good news is that there has been new progress in the discussion of EIP-7954 (raising the contract size limit from 24KB to 32KB). If approved, this optimization will provide more space for deploying more complex smart contracts.
These decisions reflect the Ethereum development team's cautious attitude in balancing innovation and stability. Every proposal's approval requires thorough technical validation and testing.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
15 Likes
Reward
15
2
Repost
Share
Comment
0/400
fomo_fighter
· 9h ago
Again and again, delayed. 7843 is really stuck this time. Is it so difficult for the consensus layer and execution layer to coordinate...
---
Haha, seven proposals were directly rejected. Glamsterdam is a bit strict, but it’s understandable for safety reasons.
---
Raising the 24KB to 32KB doesn’t seem like a big deal, but it’s better than nothing. At least it gives complex contracts some breathing room.
---
Ethereum development is really slow as a turtle. When will there be no more delays?
---
Actually, I think repeatedly debating like this is not bad. It’s better than launching blindly and then crashing.
---
If the slot opcode really passes, that would be amazing. But as for the progress... who knows?
View OriginalReply0
BankruptWorker
· 9h ago
Still changing back and forth, can @7843@ be finalized soon? The continuous delays are a bit annoying...
---
Contract size increased from 24 to 32, finally some tangible progress. Just worried that it might end up being nothing again after all the effort.
---
Seven EIPs were withdrawn? Is this really cleaning up the junk or just another round of reworking?
---
A cautious attitude sounds good, but honestly, it’s just delaying time. The market can’t wait, brother.
---
Is coordinating two layers of slot opcode this difficult? Feels like internal communication within Ethereum is more complicated than expected.
---
At least EIP-7954 has some progress. I’m optimistic about this one.
The latest developments in Ethereum's execution layer have arrived. At the 228th Core Developer Meeting(ACDE), the team discussed several important protocol upgrade proposals.
The most notable is EIP-7843 (slot opcode proposal). Since this proposal involves coordination issues between the consensus layer and execution layer, the team decided to postpone the relevant testing scope of BALs Devnet-2, pending further technical evaluation and design refinement.
On the other hand, the meeting officially rejected seven proposed EIPs from being included in the Glamsterdam upgrade plan. This means these proposals either need to be redesigned or may be delayed to future versions.
Good news is that there has been new progress in the discussion of EIP-7954 (raising the contract size limit from 24KB to 32KB). If approved, this optimization will provide more space for deploying more complex smart contracts.
These decisions reflect the Ethereum development team's cautious attitude in balancing innovation and stability. Every proposal's approval requires thorough technical validation and testing.