-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Multi-class Token Standard #1178
Conversation
* eip-1169 * added standard * Update and rename eip-1169.md to eip-1179.md * Update eip-1179.md * name change * Update eip-1178.md * Update eip-1178.md
Perhaps, but the implementation interface is practically identical in its intent. Some projects have given meaning to their ERC-721 IDs while still being compliant to ERC-721 standard. I agree that I believe most projects will not want to have the complexity proposed by #1155, but having the same interface would make everyone's life much easier. |
@PhABC from a developer standpoint and given the fact that smart contracts are meant to be inspected by the public before usage, getting rid of unnecessary complexity is desired. So, in the case where NFTs are not being used in an 1155 contract, I don't see who's lives would be made easier. Also, there is a discussion section for this EIP. I suggest posting any additional concerns you may have there so the community can weigh in, as opposed to commenting on this pull request that is hard to find. |
|
No description provided.