Join the Gaters on the rekt party in Paris and develop together with the team the roadmap 2025๐ฅ
The first 2 who DM me get a free rekt party ticket๐ฅ
Requirement: You have a GiantGaters NFT and you are in Paris on 13 Feb 2025๐ซ๐ท๐ฅ
REKT IN PARIS is back for @nft_paris ๐ซ๐ท
๐ 13TH FEB
โฒ๏ธ 10PM - REKT
๐LE CARMEN
The event is closed to holders of $REKT, Rektguy, Tabz and OSF Art.
Register here: https://t.co/xQVKdYHS8q
An important, and perenially underrated, aspect of "trustlessness", "passing the walkaway test" and "self-sovereignty" is protocol simplicity.
Even if a protocol is super decentralized with hundreds of thousands of nodes, and it has 49% byzantine fault tolerance, and nodes fully verify everything with quantum-safe peerdas and starks, if the protocol is an unwieldy mess of hundreds of thousands of lines of code and five forms of PhD-level cryptography, ultimately that protocol fails all three tests:
* It's not trustless because you have to trust a small class of high priests who tell you what properties the protocol has
* It doesn't pass the walkaway test because if existing client teams go away, it's extremely hard for new teams to get up to the same level of quality
* It's not self-sovereign because if even the most technical people can't inspect and understand the thing, it's not fully yours
It's also less secure, because each part of the protocol, especially if it can interact with other parts in complicated ways, carries a risk of the protocol breaking.
One of my fears with Ethereum protocol development is that we can be too eager to add new features to meet highly specific needs, even if those features bloat the protocol or add entire new types of interacting components or complicated cryptography as critical dependencies. This can be nice for short-term functionality gains, but it is highly destructive to preserving long-term self-sovereignty, and creating a hundred-year decentralized hyperstructure that transcends the rise and fall of empires and ideologies.
The core problem is that if protocol changes are judged from the perspective of "how big are they as changes to the existing protocol", then the desire to preserve backwards compatibility means that additions happen much more often than subtractions, and the protocol inevitably bloats over time. To counteract this, the Ethereum development process needs an explicit "simplification" / "garbage collection" function.
"Simplification" has three metrics:
* Minimizing total lines of code in the protocol. An ideal protocol fits onto a single page - or at least a few pages
* Avoiding unnecessary dependencies on fundamentally complex technical components. For example, a protocol whose security solely depends on hashes (even better: on exactly one hash function) is better than one that depends on hashes and lattices. Throwing in isogenies is worst of all, because (sorry to the truly brilliant hardworking nerds who figured that stuff out) nobody understands isogenies.
* Adding more _invariants_: core properties that the protocol can rely on, for example EIP-6780 (selfdestruct removal) added the property that at most N storage slots can be changedakem per slot, significantly simplifying client development, and EIP-7825 (per-tx gas cap) added a maximum on the cost of processing one transaction, which greatly helps ZK-EVMs and parallel execution.
Garbage collection can be piecemeal, or it can be large-scale. The piecemeal approach tries to take existing features, and streamline them so that they are simpler and make more sense. One example is the gas cost reforms in Glamsterdam, which make many gas costs that were previously arbitrary, instead depend on a small number of parameters that are clearly tied to resource consumption.
One large-scale garbage collection was replacing PoW with PoS. Another is likely to happen as part of Lean consensus, opening the room to fix a large number of mistakes at the same time ( https://t.co/UnD191Yiza ).
Another approach is "Rosetta-style backwards compatibility", where features that are complex but little-used remain usable but are "demoted" from being part of the mandatory protocol and instead become smart contract code, so new client developers do not need to bother with them. Examples:
* After we upgrade to full native account abstraction, all old tx types can be retired, and EOAs can be converted into smart contract wallets whose code can process all of those transaction types
* We can replace existing precompiles (except those that are _really_ needed) with EVM or later RISC-V code
* We can eventually change the VM from EVM to RISC-V (or other simpler VM); EVM could be turned into a smart contract in the new VM.
Finally, we want to move away from client developers feeling the need to handle all older versions of the Ethereum protocol. That can be left to older client versions running in docker containers.
In the long term, I hope that the rate of change to Ethereum can be slower. I think for various reasons that ultimately that _must_ happen. These first fifteen years should in part be viewed as an adolescence stage where we explored a lot of ideas and saw what works and what is useful and what is not. We should strive to avoid the parts that are not useful being a permanent drag on the Ethereum protocol.
Basically, we want to improve Ethereum in a way that looks like this:
Welcome to 2026! Milady is back.
Ethereum did a lot in 2025: gas limits increased, blob count increased, node software quality improved, zkEVMs blasted through their performance milestones, and with zkEVMs and PeerDAS ethereum made its largest step toward being a fundamentally new and more powerful kind of blockchain (more on this later)
But we have a challenge: Ethereum needs to do more to meet its own stated goals. Not the quest of "winning the next meta" regardless of whether it's tokenized dollars or political memecoins, not arbitrarily convincing people to help us fill up blockspace to make ETH ultrasound again, but the mission:
To build the world computer that serves as a central infrastructure piece of a more free and open internet.
We're building decentralized applications. Applications that run without fraud, censorship or third-party interference. Applications that pass the walkaway test: they keep running even if the original developers disappear. Applications where if you're a user, you don't even notice if Cloudflare goes down - or even if all of Cloudflare gets hacked by North Korea. Applications whose stability transcends the rise and fall of companies, ideologies and political parties. And applications that protect your privacy. All this - for finance, and also for identity, governance and whatever other civilizational infrastructure people want to build.
These properties sound radical, but we must remember that a generation ago any wallet, kitchen appliance, book or car would fulfill every single one of them. Today, all of the above are by default becoming subscription services, consigning you to permanent dependence on some centralized overlord.
Ethereum is the rebellion against this.
To achieve this, it needs to be (i) usable, and usable at scale, and (ii) actually decentralized. This needs to happen at both (a) the blockchain layer, including the software we use to run and talk to the blockchain, and (b) the application layer. All of these pieces must be improved - they are already being improved, but they must be improved more.
Fortunately, we have powerful tools on our side - but we need to apply them, and we will.
Wishing everyone an exciting 2026.
Milady.
Did you think they would make it easy to disrupt 7000 years of money, 4000 years of property rights and ownership, and 423 years of capital markets?
Just gonna show up with a wallet and click your way to freedom?
The system upgrade is in progress.
Itโs still day 0.
https://t.co/8mXPAse4GV
Peter Bofinger: "Wenn ich eine EUR Banknoten in der Hand halte, dann weiss ich, dass ich damit nicht reich werde!"
Danke Herr Bofinger! Ich habe geklatscht zuhause vor meinem PC! Sogar das Publikum musste laut lachen...
Join the Gaters on the rekt party in Paris and develop together with the team the roadmap 2025๐ฅ
The first 2 who DM me get a free rekt party ticket๐ฅ
Requirement: You have a GiantGaters NFT and you are in Paris on 13 Feb 2025๐ซ๐ท๐ฅ