Update EIP-7708: clarify case where multiple balance-burning selfdestructs occur in the same transaction#11126
Update EIP-7708: clarify case where multiple balance-burning selfdestructs occur in the same transaction#11126jwasinger wants to merge 3 commits into
Conversation
…ccur in the same transaction
github-actions
Bot
added
c-update
jwasinger
changed the title
File
|
eth-bot
changed the title
| A log, identical to a LOG2, is issued for: | ||
|
|
||
| - Any nonzero-value-transferring `SELFDESTRUCT` to the same account, at the time that the value removal executes | ||
| - Any nonzero-value-transferring `SELFDESTRUCT` to the same account at the time of account removal. If there are multiple of these in the same transaction, they should be ordered lexicographically by invoking contract address. |
There was a problem hiding this comment.
Why not in order of SELFDESTRUCT invocations? Otherwise, the order mismatches compared to the flavor where it is sent to a different account, no?
There was a problem hiding this comment.
The burn only occurs at transaction finalization. not when the selfdestruct opcode is invoked.
There was a problem hiding this comment.
Got it, is that also the case for regular SENDALL?
There was a problem hiding this comment.
no I'm wrong. the balance burn happens immediately.
There was a problem hiding this comment.
SENDALL won't cause balance to be burned.
|
Actually. Ether burning can still occur at transaction finalization: if an account self-destructs and ether is sent to it in the same transaction after the selfdestruct occurs, the new balance will be burned when the account is removed at transaction finalization. |
|
Let's go with the other PR you've opened @etan-status |
3 participants
No description provided.