Content pfp
Content
@
0 reply
0 recast
0 reaction

✳️ dcposch on daimo pfp
✳️ dcposch on daimo
@dcposch.eth
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.
3 replies
5 recasts
70 reactions

✳️ dcposch on daimo pfp
✳️ dcposch on daimo
@dcposch.eth
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
3 replies
1 recast
8 reactions

✳️ dcposch on daimo pfp
✳️ dcposch on daimo
@dcposch.eth
2. How does this work? - Compress ops in arbitrary app-specific ways - Bundler sends via a proxy contract - Proxy inflates > calls EntryPoint In our prototype, any app can register their own onchain inflator contract.
1 reply
0 recast
4 reactions

​woj ツ pfp
​woj ツ
@woj.eth
sexy engineering
3 replies
0 recast
2 reactions

jesse.base.eth 🔵 pfp
jesse.base.eth 🔵
@jessepollak
@wilsoncusack @bayardo.eth are these real savings or do they have the same dynamics as here? https://x.com/wilsoncusack/status/1736444867763491094?s=46
1 reply
0 recast
1 reaction