Closed ghost closed 2 years ago
Hey @iuliannov Thanks for letting us know. When a user is explicitly passing the metadata prop the contract type was hardcoded as ERC721. Now users can pass the contract type as well.
Just an FYI. You can enable fetchMetadata={true} and it will automatically fetch the data for you 😄
<NFT
address="0xE95A09ed92979622AbaaC65AE72954E61101851a"
chain="rinkeby"
fetchMetadata={true}
tokenId="1"
/>
This was failing for this particular case. Because the fetched video had link in format ipfs://...
.
This is fixed now.Please check our storybook https://web3ui.github.io/web3uikit/?path=/story/1-web3-nft--crypto-punk-01&args=chain:rinkeby;address:0xE95A09ed92979622AbaaC65AE72954E61101851a .
Closing this issue now 🙌🏻
Using the
<NFT />
component like this does not display the right type. Expecting erc1155, got erc721