Ethereum

The future is 4337 on L2.

But on L2, the main cost is calldata, and 4337 can use a lot of that.

Enter what @vitalik.eth's called the “infamous 1600-byte transfer”: a bundle (~800 bytes) containing a single Daimo transfer (another ~800). Too fat!

We solved it with bundle compression.

1. RESULTS. 4x less calldata, 2x cheaper, room to go further.

Here’s what a userop looks like before/after: https://tinyurl.com/compression-test-ts

Here’s a prod transfer. ~$1 before, $0.38 now. We can squeeze out another 2x, then pray to the danksharding gods. https://tinyurl.com/2s365wjk

Real World Ethereum 🌎 
building /daimo ✳️ 

@wilsoncusack @bayardo are these real savings or do they have the same dynamics as here?

@wilsoncusack @bayardo.eth are these real savings or do they have the same dynamics as here?

https://x.com/wilsoncusack/status/1736444867763491094?s=46

@base builder #001; onchain cities w/ OAK & city3

Will look through examples, but likely almost all the savings here would be lost with a more “correct” scalar charge for these pre-compressed transactions.

L1 data used is uncompressed. 

Gains from templating should be sustained!

Basescan shows “L1 data used”, is that number accurate? Went down 2x for us

We are not just compressing, we’re also templating.