feat: limit transferAndLock to only be callable by the distributor address
#89
Conversation
This file contains hidden or 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
heueristik
changed the title
transferAndCall to be called by the distributor addresstransferAndLock to be called by the distributor address
|
After this PR, the |
heueristik
changed the title
transferAndLock to be called by the distributor addresstransferAndLock to only be callable by the distributor address
heueristik
force-pushed
the
feature/ownable-lock-and-transfer
branch
from
e72da4d to
8a1ff7f
Compare
agureev
previously approved these changes
Sep 16, 2025
cwgoes
approved these changes
Sep 18, 2025
agureev
approved these changes
Sep 18, 2025
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.
This PR introduces a
transferAndLockCallerbeing stored as part of the implementation specificLocking.Datastruct.This change is made to prevent operational difficulties for exchanges receiving locked tokens and wrongly crediting users based on the
Transferevent.The
transferAndLockfunction is intended to be used during the claim window period to distribute locked tokens.After the claim window is over, no tokens will remain in the distributor (either because the balance is already
0orburnUnclaimedTokens()has been called). ThetransferAndLockfunction can then be considered as deprecated.On an upgrade to a new implementation, the
transferAndLockCallerwill, by default, become theaddress(0)if the new implementation does not specify it otherwise.