You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there!
I want to share my thoughts about expanding NFT Enumeration Standard.
Let me know what do you think.
Summary
Standard interface to fetch single token metadata (or token metadata + owner id) by token id.
Motivation
As the NFT ecosystem grows on NEAR, more gallery apps and viewers will appear. And it's very useful to have the ability to fetch token information by contract id & token id. In this case, the viewer app doesn't need to loop through nft_tokens (especially for large collections) or implement additional caching. And using this method + NftMintLog events, you can implement a clickable separate token page on https://explorer.near.org/.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
UPD:
looks like already implemented https://github.com/near/NEPs/blob/master/specs/Standards/NonFungibleToken/Core.md
Hey there!I want to share my thoughts about expanding NFT Enumeration Standard.
Let me know what do you think.
Summary
Standard interface to fetch single token metadata (or token metadata + owner id) by token id.Motivation
As the NFT ecosystem grows on NEAR, more gallery apps and viewers will appear. And it's very useful to have the ability to fetch token information by contract id & token id. In this case, the viewer app doesn't need to loop throughnft_tokens
(especially for large collections) or implement additional caching. And using this method +NftMintLog
events, you can implement a clickable separate token page on https://explorer.near.org/.Similar method in ERC-721Interface
Beta Was this translation helpful? Give feedback.
All reactions