You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
selfdestruct only destroys accounts if done in same tx
if an account is destroyed we need to clear its storage
to clear the storage currently we have an unsound way where the prover sends us all keys to delete
a better way would be to rely on the state object
when finishing a tx we have two cases
if no deleted account do nothing
if an account is deleted, squash the state, and in the resulting squashed state, remove any information about the deleted account (address -> Account and all storage keys)
this will probably require, upon iterating on each hashed(address, key), we verify the prev->new_value constraints, but we don't push to the new squashed_state segment the data of the account if address == destroyed address
The text was updated successfully, but these errors were encountered:
TODO: detail this issue
The text was updated successfully, but these errors were encountered: