-
Notifications
You must be signed in to change notification settings - Fork 49
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
fix: address audit findings 4, 8, 10 #1132
Conversation
The recipient per se is not included in the NFT metadata, but it would be helpful to update the metadata when the NFT changes hands so that the new recipient can see the most up-to-date information on marketplaces like OpenSea. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feedback below
tests/integration/concrete/lockup-base/renounce-multiple/renounceMultiple.t.sol
Outdated
Show resolved
Hide resolved
tests/integration/concrete/lockup-linear/create-with-durations-ll/createWithDurationsLL.tree
Show resolved
Hide resolved
tests/integration/concrete/lockup-linear/create-with-durations-ll/createWithDurationsLL.tree
Show resolved
Hide resolved
Incorporated all your suggestions @PaulRBerg. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LFG
docs: add MetadataUpdate event in create functions natspecs
Co-authored-by: Paul Razvan Berg <[email protected]>
04f92c2
to
8d7bc50
Compare
This PR addresses the following audit findings:
Note
Regarding 10th finding about
MetadataUpdate
event, I have removed it fromrenounce
but kept it in_update
since transfering stream changes recipient and recipient is a part of stream's metadata.