Content pfp
Content
@
https://ethereum.org
0 reply
0 recast
0 reaction

Señor Doggo pfp
Señor Doggo
@fubuloubu
Yesterday, pet3rpan_ brought up that solana is more "operationally competent" than Ethereum, and I thought that was an interesting framing to the problem So I asked the question "but how exactly?" One good response so far! https://x.com/Dodecahedr0x/status/1915015222315585954?s=19
3 replies
0 recast
5 reactions

Señor Doggo pfp
Señor Doggo
@fubuloubu
This is actually consistent my experience as a user, enthusiast, app developer, and participant in language/devtooling design: I feel like most hard forks don't end up with something that benefits me
2 replies
0 recast
3 reactions

shazow pfp
shazow
@shazow.eth
Do you consider EOF as something that benefits you or not?
1 reply
0 recast
1 reaction

Señor Doggo pfp
Señor Doggo
@fubuloubu
I think Greg said it best https://x.com/gregthegreek/status/1914811701901623746?s=19
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
What are some examples of things that would benefit you?
1 reply
0 recast
1 reaction

Señor Doggo pfp
Señor Doggo
@fubuloubu
EIP-2315 was a great proposal, exceedingly simple, and provided a beneficial improvement that EOF is trying to capture up in its suite of changes now It could have shipped 3 years ago, is a small change to both clients and devtooling, but was shot down for... reasons Gas model improvements, cheaper memory costs, that sort of thing is most useful
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
IMO the most credible part of EOF is the versioning container, but I 60% agree with @gregthegreek.eth (though I worry the perspective will be misapplied). I'm not sure I benefit much from more structured subroutines. Agree on gas model improvements (I'm surprised blob underpricing cliff hasn't been removed) and more work on repricing opcodes/memory, though I think that's punted to "test it in L2s first". Some big ones I'm excited for: EIP-7251 (max staking limit increase, so validators don't need to run excessive instances for no reason, hopefully reduce bandwidth chatter and give more scaling breathing room) EIP-7702 (I have so many EOAs that are hardcoded in various ways that I'd like to upgrade, also unlocks new UX flows for devs) EIP-7907 (increase contract size limits, just approved)
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
https://x.com/benjaminion_xyz/status/1915007772149555400 aligns with my feels
1 reply
0 recast
1 reaction

Señor Doggo pfp
Señor Doggo
@fubuloubu
They are currently seeking to rework the ACD process to be resistent to criticism during the implementation phase, so we will get an even more brittle version of Ethereum governance where the current fork roadmap cannot be changed after it is approved The problem is we already have stakeholder governance by the "right set of stakeholders" (per ACD, not per the community) primarily because they want to avoid being lobbied from folks in the broader community
0 reply
0 recast
1 reaction