chore: nft service

[shane-moore]

Changes

• nft collection and token queries/types/transformers were added to sdk-ts
• NftService.ts was added to sdk-ui-ts as to make it easy to query for token metadata for nft's created via mainnet codeId 49 or testnet codeId 582
  • the flow is as follows:
    1. query all smart contracts instantiated via the network specific codeId since each contract is a different NFT collection, and we pass the injectiveAddress to determine which nfts a user owns in each collection
    2. the contract calls return ipfs content identifiers (CIDs), which can then be used to query an ipfs gateway and get back metadata associated with each token as json. We also receive back a CID for the NFT's image, which can be used by the FE in an img tag for example
  • the NftService also provides a helper function for querying the contracts to obtain the name of the collection, as to be used for filtering on the FE

Optimizations

• querying IPFS can be quite slow, so it's paramount that we make the calls consecutively. It's also possible that some of the calls fail or timeout. In this scenario, we send back the successful token metadata to the FE and allow the user to pass in an error handler callback function to the service, which triggers when an ipfs query fails. Then, the FE can render the successful images and also show some error message to notify the user of missing NFTS from the query. Some additional context on IPFS complications and potential solutions are detailed in notion doc.