Check out the latest Rocket Pool bi-weekly update at the link below
+ Validator count increased 5.5%
+ The Saturn Two upgrade is on track for May
+ Onchain votes are live for RPIP-86 & RPIP-88
+ The IMC launched a new liquidity strategy
And much more!
My take on the immutable contracts affected by Glamsterdan:
While I value every protocol that has deployed their code as an immutable contract, expecting a contract to work forever is a heavily wrong assumption. This would require the Ethereum network to ossify at its current state. Every immutable contract is known to work perfectly until the next fork, while it will need to be reviewed and maybe users would need to migrate to a more recent implementation. Those who make fewer assumptions may continue working, some may not.
This is not the first time that an Ethereum fork ships breaking changes. Stable containers, just to name one feature, will also break all contracts that relied on state proofs in the name of making future changes safer and easier for everyone. That EIP broke Merkle tree verifiers a single time, while committing to forward compatibility from that fork onwards. That was very positive, but required many immutable contracts to be replaced by newer versions. If you designed your protocol to be completely immutable on top of a protocol that is mutable you just made a wrong design decision.
Changes on how Ethereum works are expected and positive for the network and if you're trying to stop them because your contract making gas assumptions broke, I would invite you to move to an ossified-too-soon-network like Bitcoin.
I'm against solutions that involve a dual-schedule or versioned approach to this as it just adds more complexity to an already too complex protocol. We should be removing complexity, not adding it.
This is a great write-up and I agree with Justin’s assessment based on what has been shared. I support hearing from the EF their side of the story that will come in due time. However, I believe they need to show leadership at this moment in accordance with their proclaimed principles.
@pcaversaccio@me_jango@z0r0zzz@jchaskin22 Fundamentally do you think that all future forks of Ethereum should be backwards compatible or will it be acceptable to have a breaking change in the future? If breaking changes are acceptable what’s the procedure for release?
We are currently in the process of conducting our audit for @Rocket_Pool's Glamsterdam release.
Be sure to keep yourself informed by following us for important updates.
BailSec - exposes risks that others overlook ✅
The strawmap set a goal of Lean Ethereum by 2029—we now have a fork-by-fork plan to get there.
H* will be the last fork without lean features. I* will ship the leanVM and lean transactions. J* will add lean attestations, DA sampling and PCS. By L*, Lean Ethereum will be complete
EVA Symposium III is tomorrow, November 4, in Mumbai.
@jdetychey and @Pol_Lanski join The Great Issuance Debate, hosted by @0xzak.
📍 Event location
Grand Salon Grand Hyatt Mumbai Hotel & Residences Vakola, Mumbai
If you’re coming directly, head to the Grand Hyatt Mumbai and ask for the Grand Salon.
🚌 Shuttle from Devcon
Buses will line up between 4:15 and 4:45 PM at Gate 20 of the Jio World Convention Center (JWCC).
Look for the team holding EVA signs. The shuttle will take you to the Grand Hyatt Mumbai. Return shuttles are also provided.
🕔 Evening schedule
5 PM — Doors open, high tea and refreshments 6–8 PM — Symposium program 8–11 PM — Dinner and networking
All times are Mumbai local time, IST.
Attendance requires approved registration. We’re at capacity, but the waitlist is open.
https://t.co/rPj3LTKoNb
@ethereum@drakefjustin Serious question: Why are the core developers still debating which EIPs to include in Hegotá, instead of simply declaring Hegotá the post-quantum (PQ) fork and limiting it to only post-quantum cryptography EIPs?
Staking with a decentralised protocol that has a diverse and fully permissionless node operator set means you don’t need to trust any people or companies with your ETH
Rocket Pool is still the only fully permissionless staking protocol
I envisioned the infographic to work like those atom diagrams from physics class: a poster for new learners and for people who already build on Ethereum.
Please reply with corrections or anything that would make the structure easier to see.
I've spent some time drawing an infographic, "The Anatomy of the Ethereum Block."
Updated in Mumbai ahead of Devcon. PDF attached👇.
Looking at it, I'm growing alarmed by how much isn't post-quantum.
BLS signatures, KZG, and secp256k1 are not post-quantum. They break when a relevant quantum computer exists. Hash roots resist Shor's algorithm. Grover only weakens a 256-bit hash.
If we already know the replacements, I wonder if I* is too late. Should Hegotá be the post-quantum fork, and should the list now considered for inclusion in Hegotá move to I*?