OP Stack

Base

Will this approach really reduce ERC-4337 UserOp fees by ~35% to all /op-stack (e.g. /base) users, or am I missing something?

@dcposch.eth

Real World Ethereum 🌎 
building /daimo ✳️ 

Security researcher and blockchain research lead at Fireblocks; built OpenOrdex, /spellcaster

how did you calculate arbitrum calldata compression? and is this code open source?

My PR is here:
https://github.com/daimo-eth/bulk/pull/8

Arbitrum docs explain calldata compression used in gas estimation:
https://docs.arbitrum.io/devs-how-tos/how-to-estimate-gas

Arbitrum code:
https://github.com/OffchainLabs/nitro/blob/27d9d4482c4ada93d4da597373eb41be962348a7/arbos/l1pricing/l1pricing.go#L503

abstractooor @rhinestone • prev oxford and exited web2 founder

cool thanks - so this is using zlib for arbitrum (through pako) instead of brotli right?

why? brotli is still stateless so stateful compression should give u savings right?

Actually I think that this won't give any cost savings on Arbitrum - but it will give ~35% savings on Base/Optimism

My point was more that zlib != brotli so was wondering if you knew roughly how they compare in terms of compression output

And just to clarify - Arbirtum is using brotli when calculating the L1 data cost of an L2 transaction. In comparison, OP-Stack chains just multiply their L2 calldata by 0.684. That's why I think we can gain a "double compression discount" on OP-Stack chains. It also raises alignment/incentive structure questions...