carlbeek.eth
@CarlBeek
Followers
6K
Following
2K
Media
77
Statuses
1K
throughput/acc @ethereum researcher
Joined December 2011
This manifesto is not Ethereum. Yes, Ethereum should be reasonably decentralised, credibly neutral, censorship resistant, and permissionless, but it also needs to be a great product 1/8
1/ Today, The Account Abstraction Team & @VitalikButerin are publishing something we’ve talked about for years but never wrote down clearly enough: The Trustless Manifesto. And we’re putting it where it belongs: onchain. trustlessmanifesto.eth →
5
1
70
but mr lightclient, you’re forgetting the formula
Consensus via PoW is one of the most beautiful and simple technologies computing has ever seen. Not to say that PoS and zk aren't great innovations, but depicting them as more elegant than PoW is wrong.
6
3
78
In short, while I agree that many of the principles laid out here, if we put all of our skill points into permissionlessness we’ll have a great system that no one will use, and Ethereum can be so much more impactful than that. 8/8
3
0
12
“We measure success not by transactions per second, but by trust reduced per transaction.” Ethereum’s succeeding shouldn’t be measured in either. The product of the two: trust reduced per second, which is a much better metric 7/8
3
0
12
For 99% of humanity, the lack of access to finance (beyond basic transfers) is a major limiting factor on their upward mobility Ethereum should be the platform for that and it should be as efficient as possible 6/8
1
0
5
Financial friction is a cost borne by everyone. You have to pay to overcome it with every financial thing you do and it slows humanity’s progress. 5/8
1
0
9
“Ethereum was not created to make finance efficient or apps convenient.” That might not have been @VitalikButerin et al’s direct intention, but it is a consequence building an open system A good blockchain makes finance more efficient, and that’s a great thing 4/8
1
0
13
“Ethereum has scaled” It’s laughable that this is in the past tense, we’re taking some of the first steps now, but we’re orders of magnitude short of where we need to be. In the greater scheme of things, all blockchains are still very slow. 3/8
2
1
18
In order for Ethereum to have the most positive impact on the world, it needs to be a much more open system and an excellent product. If we build the most robust, decentralised product that almost no one uses, we have failed too. It’s a careful balancing act. 2/8
1
0
14
This manifesto is not Ethereum. Yes, Ethereum should be reasonably decentralised, credibly neutral, censorship resistant, and permissionless, but it also needs to be a great product 1/8
1/ Today, The Account Abstraction Team & @VitalikButerin are publishing something we’ve talked about for years but never wrote down clearly enough: The Trustless Manifesto. And we’re putting it where it belongs: onchain. trustlessmanifesto.eth →
5
1
70
PSA: the Holešky testnet will be shut down two weeks after Fusaka finalizes on it. See the full announcement below 👇
223
117
342
the payload was discovered, we're back to RLP
2
0
13
giga bullish @notnotstorm’s absorb: data collection & processing done right i can finally stop reimplementing hacky versions myself for each project
1
0
5
common misconception: actually ePBS is a scaling feature, not an economic/market one
1
0
4
had a sneak peak at the slides, this one is going to be a banger
I am giving a talk in ~1h at Frontiers on our Ethereum L1 scaling plans. Event livestream below, I also heavily recommend you check out the other talks. It’s a great event again this year! (I am scheduled for 10am PT, 7pm CEST, but currently ~15min behind).
1
2
13
I'm hiring at the EF: https://t.co/TK50zLbEre If you're into Ethereum, cryptography, and formal verification, please get in touch! 🙂
9
46
259
this effectively means that ACD is a sham, the decision is made months before based on what research CL devs want to work on because that is the only feature that will have sufficient research and prototypes for them to be happy to CFI
@CarlBeek yes, this is unfortunately something that will happen more and more often when engineers also want to take an early look at implementation instead of only coding what research has already finalized. Research is pipelined this way as well. It would be crazy if I complained 1/2
2
0
2
would the fusaka delay have actually been needed if instead of playing with ePBS (+ FOCIL) prototypes we’d have have focused on shipping the current fork?
4
1
9