We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There was an ineffective algorithm for data destruction in EVM that got fixed.
We iterate over LevelDB keys belonging to the account that has been destroyed and remove them
@kladkogex please add more description
The text was updated successfully, but these errors were encountered:
There are two levels at which data destruction happens:
EVM call delete keys of LevelDB - there was a bug in this that has been fixed. Note that there is a patch that needs to be enabled.
If keys are destroyed, sometimes LevelDB does not shrink the LevelDB file where the keys are stored. This is a separate problem
Sorry, something went wrong.
#1644 addressed pull request comments
f83d7a3
kladkogex
Successfully merging a pull request may close this issue.
There was an ineffective algorithm for data destruction in EVM that got fixed.
We iterate over LevelDB keys belonging to the account that has been destroyed and remove them
@kladkogex please add more description
The text was updated successfully, but these errors were encountered: