-
Notifications
You must be signed in to change notification settings - Fork 538
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
General purpose NFT contract #47
Comments
A few things that I'd like to see in an NFT contract to help keep it useful and flexible:
|
A good next step for this would be to pin down what the The specific implementation can follow, and will probably be able to benefit from some cool new functionality in Sway (ie: vec, improved storage interface). |
Something along the lines of this as a start (may not be complete yet):
And then some supporting internal functions, ie:
|
Eventually, we'll want to add event logging to this as well. I don't know about the |
cc @simonr0204 and @pixelcircuits for input |
A separate (but related) issue is token standards, ie: Following existing standards, or creating a new one. |
We need to also make sure it's just as easy for contracts to hold NFTs as it is for EOAs. This will be necessary for cross domain bridging in the future. I also like how ERC165 allows for interface detection and we should definitely mirror that process to make for easy data crawling for marketplaces, etc. |
Plus one on the use of erc165! |
@bitzoic can you move this checklist into the description above so that GitHub does some nice tracking similar to #1 ? |
This issue's tests are currently blocked by FuelLabs/fuels-rs#326 |
WIP
A general purpose NFT contract that will have the following attribute:
The contract ABI will follow the format below:
The text was updated successfully, but these errors were encountered: