A place for talking about the Ethereum Virtual Machine on Farcaster.

Optimizing my first serious L2 contracts has been a journey:

1) Dev: your intuitions are all wrong now.
2) Testnet: cheap L2 gas, cheap L1 calldata. Many tools overestimate L2 gas and it can outweigh calldata unlike IRL.
3) Mainnet: cheap L2 gas, L1 calldata is 20-100x testnet cost. Calldata costs dominate everything.

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Thoughts on optimizing for L1 calldata now and then after 4844, L1 calldata costs plummet? Rewrite?

eng @megaphone-hq | prev @0xproject | Interested in walkable cities

Internal calls are not affected by L1 DA costs so it doesn't necessarily make sense to design the whole interface for optimal calldata use. Add a calldata-optimized interface as a secondary set of functions that invoke unoptimized functions. By decoupling this way you don't have to rewrite everything when costs change.

+1 to this, kind of like a router pattern. Also your optimization function may be different. L1 is so expensive it’s pretty much always worth it, on L2 time and effort vs impact is not as clear cut. “Cheap enough now and even cheaper later” might be OK.

Beautiful

And great to see you here on FC @frangio!