-
Notifications
You must be signed in to change notification settings - Fork 57
Features added on bug fixed versions #10
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
base: main
Are you sure you want to change the base?
Conversation
I'm wary of making it part of the standard as I don't think we want to encourage this. It makes it harder for someone to request the refund and there doesn't seem to be a benefit for forcing this behaviour (other than making it easier for users to forget to refund). Happy to hear if you think there is a good reason for this. |
|
All features look super useful but I think we should rectify the critical bug first |
|
@qbig, thumbs up. |
I thought if people who minted nfts are refund their nfts immediately that action can be trigger other users to refund their nfts immediately too. My goal is giving a chance to the project to prove themselves to their community that they are really doing their best. (At least first 5-10 days.) This is my thoughts if you want to i can delete this feature. Do you want me to do that? Also do you want me to edit ERC721ChangablePrice.sol with current bug fixed version? |
I'd be happy for the delayed refund feature to not be part of In practice btw we haven't seen the mass refunds happen where it would cascade. Although it's possible this would happen in the future, I'm not sure it will as the refund period is quite long and you don't lose anything by waiting a little longer. |
Yes, we shouldn't definitely keep the bug fixes in |
|
so i think what could be great here is creating contracts that we can extend. so similar to erc721 contracts on openzeppelin. you can choose which portions you want to extend to add each piece of functionality rather than us having lots of copy paste code (especially where a lot of it isnt related to ERC721R) |
|
@elie222 , I agree with your approach. Keep the core clean. Additional features put it over extended features. Stick with this approach. |
| } | ||
|
|
||
| function refund(uint256[] calldata tokenIds) external { | ||
| require(msg.sender != refundAddress, "Can't refund to refundAddress"); |
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.
we had another fix for this already so i think this can be removed
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.
Okay, I will change this with current bug fixed version
|
Work on splitting it into a contract people can inherit is happening here: #16 btw |
ERC721ChangablePrice.sol
mintPrice can be set for different cases (like presale, publicsale). Every NFT's mint price storing with these lines of code,
mapping(uint256 => uint256) public tokenPrices;We have to call this function after mint functions called.
ERC721RefundLock.sol
We might dont want to let users refund their NFTs immediately.
uint256 public constant refundLock = 30 days;We have to use this function with require() inside of refund function.
require(!refundLockActive(), "Refund will be able in 30 days");ERC721Full.sol
This contract is contains both of these files.