i struggle with the idea of protocol ossification
a boat wanting to stay put in the center of a river needs to do a lot to "not move"
not changing is contingent on a socio-political consensus. when core devs move on, motivated parties may insert themselves into the vacuum
Over the past year, many people I talk to have expressed worry about two topics:
* Various aspects of the way the world is going: government control and surveillance, wars, corporate power and surveillance, tech enshittification / corposlop, social media becoming a memetic warzone, AI and how it interplays with all of the above...
* The brute reality that Ethereum seems to be absent from meaningfully improving the lives of people subject to these things, even on the dimensions we deeply care about (eg. freedom, privacy, security of digital life, community self-organization)
It is easy to bond over the first, to commiserate over the fact that beauty and good in the world seems to be receding and darkness advancing, and uncaring powerful people in high places are making this happen. But ultimately, it is easy to acknowledge problems, the hard thing is actually shining a light forward, coming up with a concrete plan that makes the situation better.
The second has been weighing heavily on my mind, and on the minds of many of our brightest and most idealistic Ethereans. I personally never felt any upset or fear when political memecoins went on Solana, or various zero-sum gambling applications go on whatever 250 millisecond block chain strikes their fancy. But it *does* weigh on me that, through all of the various low-grade online memetic wars, international overreaches of corporate and government power, and other issues of the last few years, Ethereum has been playing a very limited role in making people's lives better. What *are* the liberating technologies? Starlink is the most obvious one. Locally-running open-weights LLMs are another. Signal is a third. Community Notes is a fourth, tackling the problem from a different angle.
One response is to say "stop dreaming big, we need to hunker down and accept that finance is our lane and laser-focus on that". But this is ultimately hollow. Financial freedom and security is critical. But it seems obvious that, while adding a perfectly free and open and sovereign and debasement-proof financial system would fix some things, but it would leave the bulk of our deep worries about the world unaddressed. It's okay for individuals to laser-focus on finance, but we need to be part of some greater whole that has things to say about the other problems too.
At the same time, Ethereum cannot fix the world. Ethereum is the "wrong-shaped tool" for that: beyond a certain point, "fixing the world" implies a form of power projection that is more like a centralized political entity than like a decentralized technology community.
So what can we do? I think that we in Ethereum should conceptualize ourselves as being part of an ecosystem building "sanctuary technologies": free open-source technologies that let people live, work, talk to each other, manage risk and build wealth, and collaborate on shared goals, in a way that optimizes for robustness to outside pressures.
The goal is not to remake the world in Ethereum's image, where all finance is disintermediated, all governance happens through DAOs, and everyone gets a blockchain-based UBI delivered straight to their social-recovery wallet. The goal is the opposite: it's de-totalization. It's to reduce the stakes of the war in heaven by preventing the winner from having total victory (ie. total control over other human beings), and preventing the loser from suffering total defeat. To create digital islands of stability in a chaotic era. To enable interdependence that cannot be weaponized.
Ethereum's role is to create "digital space" where different entities can cooperate and interact. Communications channels enable interaction, but communication channels are not "space": they do not let you create single unique objects that canonically represent some social arrangement that changes over time. Money is one important example. Multisigs that can change their members, showing persistence exceeding that of any one person or one public key, are another. Various market and governance structures are a third. There are more.
I think now is the time to double down, with greater clarity. Do not try to be Apple or Google, seeing crypto as a tech sector that enables efficiency or shininess. Instead, build our part of the sanctuary tech ecosystem - the "shared digital space with no owner" that enables both open finance and much more. More actively build toward a full-stack ecosystem: both upward to the wallet and application layer (incl AI as interface) and downward to the OS, hardware, even physical/bio security levels.
Ultimately, tech is worthless without users. But look for users, both individual and institutional, for whom sanctuary tech is exactly the thing they need. Optimize payments, defi, decentralized social, and other applications precisely for those users, and those goals, which centralized tech will not serve. We have many allies, including many outside of "crypto". It's time we work together with an open mind and move forward.
100% support this, The Merge introduced insane complexity not only for UX of running a node, but also for testing and debugging the protocol, and ample surface for IPC-layer bugs.
We should be open to revisiting whole beacon/execution client separation thing.
Running two daemons and getting them to talk to each other is far more difficult than running one daemon.
Our goal is to make the self-sovereign way of using ethereum have good UX. In many cases that means running your own node. The current approach to running your own node adds needless complexity.
Short-term, maybe we want some more standardized basic wrapper that lets you install dockers of any client and make them talk to each other easily? Also good that @ethnimbus unified node https://t.co/BWpU939wIM exists. Longer term, we should be open to revisiting the whole architecture once @leanethereum lean consensus is more mature.
A landmark moment in onchain security.
@Coinbase has launched a $5M bug bounty on Cantina, a new program focusing exclusively on all its onchain products and @baseโs smart contracts. It sets a new standard for securing Web3 organizations at scale. Details below.
With the Interop Testing call happening over the next hour, which will (yet again) decide the fate of EOF, we would like to address a few misconceptions.
[๐ฃCall agenda:https://t.co/2R3xnej5Dw]
The team prepared valuable input to the discussion on @solidity_lang libraries "compilation to EOF" issues.
https://t.co/tGO2mC40Jw
It's worth reading and decide if it's complicated or easy.
A short explainer of why JUMPDEST-analysis exists by @chfast.
It makes code-compilation feasible (fast JIT/AOT execution) and helps preventing certain kind of security problems.
https://t.co/ClbRvT8LY9
The EVM Object Format (EOF) is a long-awaited upgrade for the EVM. We wrote about our stance in support of it.
Topics to expect in the post:
โง Benefits of EOF
โง Is EOF the only way?
โง Can we solve "Stack Too Deep" without EOF?
โง Why not EIP-615/EIP-2315?
โง Do we really need immediate arguments?
...and more!
Give it a read.
โhttps://t.co/9JudUIqF2j
I want to remind, that EVMMAX is dependent on immediate arguments.
Any alleged no-EOF alternative is not viable: stack-based arguments would be too expensive, making entire EVMMAX useless; trying to introduce immediates without EOF quickly becomes complex, requiring validation similar to EOF.
We haven't even seen anything resembling concrete spec from the proponents of such "solutions" anyway.
To pick just one point from the latest anti-EOF doc:
The concern is described accurately. The proposed "solution" is not coherent at all: BEGINDATA wouldn't in any way affect the existing contracts, but can only be used in the new ones. It does not provide any extra safety for contacts deployed before BEGINDATA was available.
@lightclients Published new EIP for TXCREATE instruction in EOF https://t.co/ML2nON4tZx
Also some final polishing of EIP-7702 implementation in evmone.