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

EIP proposal, relevant to gas limit raising discussions:

Increase calldata cost, perhaps back to the original 68 per nonzero byte, now that we have EIP-4844 blobs for data-heavy use cases.

It would address the worst-case data issues and add breathing room to raise not just gas limit but also blob count target.

One alternative, which would keep average-case calldata prices low, is to bring back a separate limit for calldata, eg. via https://eips.ethereum.org/EIPS/eip-4488, assuming that our experience with EIP-4844 de-risks multidimensional limits+pricing in the meantime.

This alternative makes more sense to me. Most SNARK verifications still use a decent amount of calldata even post 4844, and it'd be a shame to make that more expensive IMO.

Researcher at https://chainlight.io 🔗‍💥🔦,
Building https://relicprotocol.com

Builder of things. Dir of Product Research @ Polygon; x: Flow, Augur;

Yes, I can actually write code.

That said I'm also a 4488 fan and love that it's becoming feasible again, at least for exploration.

Also dove tails into some of the cost problems on zk EVMs where the runtime and memory cost doesn't map well to gas.

We should be able to amortize that cost over more updates by aggregating signatures (ideally via STARKs before we produce the snark).

This is the path we are taking for Polygon2 to reduce L1 cost for an ecosystem of L2s (or L3s or whatever).

So at least for this use case I think it's doable to raise the price.