We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Dear developers,
IRC721 Standard token is DEPRECATED in below document. https://developers.iost.io/docs/en/3-smart-contract/Token721.html
And the document encourages to use "pure javascript NFT standard: IRC722".
Does this mean creating a self-deployed token that is ABI compliant with IRC721? (Similar to the relationship between IRC20 and IRC21)
Or is the IRC721 ABI itself DEPRECATED? And [iostnft.abi](published in the Universal CryptoAssetToken) is the new IRC722 ABI? https://github.com/blockchainpower/UniversalCryptoAssetToken/tree/master/src/iost
I don't understand which one, so can you tell me?
Thank you
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Dear developers,
IRC721 Standard token is DEPRECATED in below document.
https://developers.iost.io/docs/en/3-smart-contract/Token721.html
And the document encourages to use "pure javascript NFT standard: IRC722".
Does this mean creating a self-deployed token that is ABI compliant with IRC721?
(Similar to the relationship between IRC20 and IRC21)
Or is the IRC721 ABI itself DEPRECATED?
And [iostnft.abi](published in the Universal CryptoAssetToken) is the new IRC722 ABI?
https://github.com/blockchainpower/UniversalCryptoAssetToken/tree/master/src/iost
I don't understand which one, so can you tell me?
Thank you
The text was updated successfully, but these errors were encountered: