This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
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.
This PR adds a
Freeze
andThaw
event. The respective event is emitted whenever some balance is frozen or thawed. This is a continuation of #12287. I decided to split PRs to maintain transparency and to not invalidate the previous audit, see #12287 (comment) for more information.The logic remained the same as in #12287, however two new events
Freeze
andThaw
were added that cover the case thatupdate_freezes
is invoked instead of the deprecatedupdate_locks
. The tests are also equal, except that the calls were adjusted to thefreeze
case. Those are the test scenarios:I decided to follow the approach of adding new events for functionality added in the
Fungible
implementation. Now aLock
andUnlock
event exists for calls into the deprecatedupdate_locks
, whereasFreeze
andThaw
also exist to cover calls into the newupdate_freezey
function. Should we move forward with that approach?