-
Notifications
You must be signed in to change notification settings - Fork 7
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
Contract Simplification + Source of Truth #51
Comments
Of course, I don't have the full vision that you all had when building it so some of the functions may be needed for reasons that I'm not thinking of, but I have tried to glean as much background info from the documentation as I can. Cheers! |
The smart contract was designed with advanced features in mind that may be used or not in the future. In terms of documentation you can have a look at the draft for now docs located at https://docs.nftdelegation.com/ . There is also a Developer Center with sample integration examples. |
Understood. There is a world where there are simple calls that can be made for easy integration, while keeping advanced features. Overall, there are some functions that seem to be geared towards simple integration, such as |
Overall, I think there is a need to simplify a lot of the interface in order to get more adoption outside of the 6529 ecosystem. There are too many retrieve functions with lacking documentation, leading to expectations that aren't met in code.
You mainly need just one or two functions to get if a delegated address is delegated or not for a specific use case, collection (or all collections), token, and at a specific timestamp. It would remove a lot of need to loop over delegate addresses found in many of the write functions. If you still want enumerations of all delegates or delegations, you can still achieve a simpler read interface than currently exists. The main point is to have one/two source of truth functions, plus a few other functions that provide nice enumerations for indexing.
The text was updated successfully, but these errors were encountered: