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

Matthew Fox 🌐 pfp
Matthew Fox 🌐
@matthewfox
Massive 👏 squeeze another 2x and we are almost at cost parody with EOAs 🤝
1 reply
0 recast
1 reaction

✳️ dcposch on daimo pfp
✳️ dcposch on daimo
@dcposch.eth
We can do better Maybe not in the current degen case where every 4337 bundle tx contains exactly 1 op But in the near future when every new L2 block = new 4337 bundle = multiple ops We can beat legacy eoas on cost…in the (likely) event that major rollups don’t implement native stateful compression
1 reply
0 recast
1 reaction