-
Notifications
You must be signed in to change notification settings - Fork 61
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
Update the CF example contract #32
base: main
Are you sure you want to change the base?
Conversation
@royosherove @lawweiliang lmk if you have any thoughts. may still be some updates and cleanups here |
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.
@elie222 , even after the token had revoked, user still can refund.
I think we need to add an additional checking over refund function
require(!hasRevokedRefund[tokenId], "Refund revoked for this token");
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.
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.
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.
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.
For royalty ERC2981 part, I guess we need the resetTokenRoyalty as well.
Reasons
- Cause if we made mistake, we are still able to change the royalty.
- As the project getting more and more expensive, the royalty will increase as well, so we need to update the royalty.
If worry about the community, before we update the royalty, we will propose and see the feedback.
The ERC2981 part should be standard. Don't think we did anything special there.
we don't have this yet though. ERC721RExample has a lot of extras to it. it needs to be cleaned out a lot
yes, definitely looks like an issue. i'll check what the latest around this is and get an update to the pr |
We could "set" the selected token id to the default amount, but then it won't track any future changes to the default royalty. I agree this should be added. |
No description provided.