Feat/send dust to treasury #193
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
When an account is closed but still holds a balance below the Existential Deposit (ED), some PLMC "dust" is generated. This dust should be directed to the Blockchain Operation Treasury instead of being burned.
Why?
The following extrinsic https://explorer.polimec.org/polimec/extrinsic/767479-2 resulted in the account of the sender being killed, and the residual dust was burned rather than allocated to the Blockchain Operation Treasury.
How?
We can adjust this behavior through the
DustRemovalconfiguration option in theBalancespallet.Testing?
A new integration test now compares the total issuance before and after a
DustLostevent to ensure the dust is properly accounted for.