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
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
The text was updated successfully, but these errors were encountered:
Awesome issue. FYI, info on early Boom NFTs and the Stack blockchain launch POAP badges is available in SIP-016.
rafaelcr
changed the title
support og legacy nft contracts (pre sip-016), for the culture
support og legacy nft contracts (pre sip-009), for the culture
Aug 29, 2024
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-016SP497E7RX3233ATBS2AB9G4WTHB63X5PBSP5VGAQ.boom-nfts-50
: not SIP-016SP1K1A1PMGW2ZJCNF46NWZWHG8TS1D23EGH1KNK60.badges
: not SIP-016SPJW1XE278YMCEYMXB8ZFGJMH8ZVAAEDP2S2PJYG.stacks-pops
: lost keys, frozen incorrect metadataThe text was updated successfully, but these errors were encountered: