hirosystems / hirosystems/token-metadata-api
support og legacy nft contracts (pre sip-009), for the culture
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 7
- Avg merge
- 35m
- Merged PRs (30d)
- 2
Description
There are a couple NFT contracts that exist on mainnet but were launched before SIP-009 existed, so the current API implementation skips them because they don't have standardized methods for pulling its token URIs, supply, etc.
There are requests from the community to still support them, though, because of their historical significance to the Stacks network. We should evaluate if/how we should support them.
Example contracts:
* `SP497E7RX3233ATBS2AB9G4WTHB63X5PBSP5VGAQ.boom-nfts`: not SIP-016
* `SP497E7RX3233ATBS2AB9G4WTHB63X5PBSP5VGAQ.boom-nfts-50`: not SIP-016
* `SP1K1A1PMGW2ZJCNF46NWZWHG8TS1D23EGH1KNK60.badges`: not SIP-016
* `SPJW1XE278YMCEYMXB8ZFGJMH8ZVAAEDP2S2PJYG.stacks-pops`: lost keys, frozen incorrect metadata
Contributor guide
Assessment
This issue has not been assessed yet.