vrypan |--o--|
@vrypan.eth
ETH has fixed everything that annoyed me 4 years ago. Except sending your max ETH balance, where it's impossible to not leave some dust that will be lost forever. It's very annoying. I get why it is how it is, but I wish at least L2s had a solution. Even if it was a special transfer op that allowed the sequencer to claim this dust as gas as part of the transaction. Or a send_max op, or something.
9 replies
3 recasts
37 reactions
shazow
@shazow.eth
EIP-7702 + SELFDESTRUCT would do the trick, once that's live. :D
0 reply
0 recast
1 reaction
cqb
@cqb
I feel like if there was enough motivation this could be fixed without much effort. Since 1559 automatically calcs how much a transaction fee is, you could just take it directly from the amount being transferred in a new transaction type, or op as you suggested. I understand that there is motivation to not introduce new transaction types, but if we are all going to switch to sc wallets eventually then having an opcode that does this makes a lot of sense.
0 reply
0 recast
1 reaction
Greg
@greg
I think its possible to do that (effectively burn the dust) with a legacy tx, let me see if I can find a link
0 reply
0 recast
0 reaction
Harris
@harris-
The L1 fee of the L2s is dependent on the tx at the confirmation time or something right?
0 reply
0 recast
0 reaction
links 🏴
@links
Maybe you just need to let some things go, friend. Dust in the wind. All we are is dust in the wiiiiind 🎶
0 reply
0 recast
0 reaction
Shifenqu
@shifenqu
ETH addresses some old issues but still has flaws like dust loss in max balance transfers. L2s could solve this?
0 reply
0 recast
0 reaction
L3MBDA
@l3mbda
it’s like tipping the blockchain forever.
0 reply
0 recast
0 reaction
OmaZeco
@omazeco
It's frustrating indeed
0 reply
0 recast
0 reaction
Echo | Builder
@baseeacc
and confirm every time? any better solution?
0 reply
0 recast
0 reaction
