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

Nice!

Looks excellent

We could evaluate a DeflatePerOpInflator that does whole-bundle DEFLATE in addition to per-op custom compression/templating

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

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

So assuming this is RFC 1951 based DEFLATE, using LZ777 and Huffman encoding, then this is lossless so there should be no data collision risks.

Other than adding an additional step to read the data, the only real concern is encoded data reduced to a hash could have more collisions risk but negligible and rare use case