Skip to content
New issue

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

feat(protocol): allow owner to update recipient in TokenUnlock #18184

Merged
merged 3 commits into from
Sep 28, 2024

Conversation

dantaik
Copy link
Contributor

@dantaik dantaik commented Sep 27, 2024

@davidtaikocha We need to upgrade the implementation of 0x2Da30e14dE6a5fcE16a5Ea72199De76cebDC876C and then change the recipient from 0x9c0c06ddbb72f70820d7e55b6b77db175d400fba to 0xf7a0cd60e3b6ab4523a5f54e9a410258895b138d.


Screenshot 2024-09-27 at 15 47 42

@dantaik dantaik marked this pull request as ready for review September 27, 2024 07:48
Copy link

openzeppelin-code bot commented Sep 27, 2024

feat(protocol): allow owner to update recipient in TokenUnlock

Generated at commit: 1ad02efb57e4589cb94c80389b9fcd428a2ddd0a

🚨 Report Summary

Severity Level Results
Contracts Critical
High
Medium
Low
Note
Total
3
3
0
7
43
56
Dependencies Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0

For more details view the full report in OpenZeppelin Code Inspector

@dantaik dantaik added this pull request to the merge queue Sep 28, 2024
Merged via the queue into main with commit 773ae1b Sep 28, 2024
7 checks passed
@dantaik dantaik deleted the token_unlock_change_recipient branch September 28, 2024 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants