Content
@
0 reply
0 recast
0 reaction
Brenner @ Edge City
@brenner.eth
Can someone from @eigenfoundation please explain what's happening here? https://etherscan.io/tx/0x9261a0d04fd22f2b36b084f525b15acc6c9a1b9b3eb204555ee81f0412b0803d
3 replies
0 recast
2 reactions
Jay Brower (jaymothy.eth)
@jayb
hey! last night we flushed remaining withdrawals from the DelayedWithdrawalRouter, which was deprecated during our most recent upgrade. Anyone who had queued a withdrawal, we effectively paid the gas to send your withdrawal to you so we could clean up the contract. Hope this helps!
2 replies
1 recast
5 reactions
Jay Brower (jaymothy.eth)
@jayb
The transactions in question all originated from 0x89299fe1f6962AC03E8a2A72870af121288F2C97 (an EigenLabs address), and are multicall3 aggregate writes to the permission-less `DelayedWithdrawalRouter.claimDelayedWithdrawals()`. As a reminder, the DelayedWithdrawalRouter lived here (https://etherscan.io/address/0x7Fe7E9CC0F274d2435AD5d56D5fa73E47F6A23D8) and after the distribution of all withdrawals has 0 ETH remaining. If you have any other questions, please let us know 🤝
0 reply
0 recast
0 reaction
Brenner @ Edge City
@brenner.eth
Appreciate the explanation! And we’re all good to just keep our nodes’ withdrawl addresses pointed at our existing eigenPods?
1 reply
0 recast
0 reaction