Content pfp
Content
@
0 reply
0 recast
2 reactions

0age pfp
0age
@0age
Nothing beats when the EVM enters a new “weird era” First: introduction of DELEGATECALL to replace CALLCODE Then: CREATE2 (this was a huge game-changer & really kicked off my personal journey in understanding yhe EVM) Now: AUTH & AUTHCALL — so much to be (re)built and reconsidered And just wait until EOF 🤯
3 replies
1 recast
27 reactions

shazow pfp
shazow
@shazow.eth
What's your fav use case for EOF? My understanding is it helps simplify the transpiling from higher level languages, right? It wouldn't actually enable new use cases?
1 reply
0 recast
1 reaction

0age pfp
0age
@0age
Oh it’s massive, basically establishes ways to version the EVM by contract and have whole new semantics
1 reply
0 recast
0 reaction

shazow pfp
shazow
@shazow.eth
From an EVM perspective though, does it allow us to do anything that we couldn't do before? Always seemed like a nice-to-have to me.
1 reply
0 recast
0 reaction

Brent Fitzgerald pfp
Brent Fitzgerald
@bf
My understanding is that the EOF pins the contract to a particular EVM version. This explicit versioning will allow the EVM to be upgraded more safely going forward.
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
Good point. I'm mostly focused on the code sections/jumps changes which will require me to redo a bunch of WhatsABI work lol. 500 $DEGEN
1 reply
0 recast
0 reaction