Skip to content

show remarks in txs and uritokens #683

Description

@Anna15170221

remarks for uritokens

/v2/nft/:uritokenID
/v2/uritoken/:uritokenID

new parameter
remarks - true/false (false is default)

NOTE: only available for single token, not available for search, data is getting directly from network

example response
remarks: [
{
flags: { immutable: true },
name: "image_ipfs_sha512h_base16",
value: "ipfs://f01551320ae43f1953c46549bc09a90c83930e1646d7d6ca31e2b14a18adab0aba07c1f77",
},
{
flags: { immutable: true },
name: "image_ipfs_sha512h_base32",
value: "ipfs://bafkrgifoipyzkpcgksn4bguqza4tbylenv6wziy6fmkkdcw2wcv2a7a7o4",
},
],

We need to show remarks and crawl ipfs

https://xahauexplorer.com/nft/829DD7E8903A1FDD848044709C2D3262EC6F301A0F0B37623270779C925C82A1

Another example: https://xahauexplorer.com/nft/93240119143664E0C4CAA2FC4A9F137A7DFC30CCC741F643E42EFC9050CCD373

UPD: We now show remarks for URITokens but

We need to show remarks in txs too.
https://xahauexplorer.com/tx/4DB32317CAFF7AE440111F514A689DE5342B5190E700EFC4CC2FF96F83CF28CD

Some NFTs fail because their files are no longer available on IPFS. However, the metadata already contains a thumbnail, so we could use it in those cases. Currently, we show the error: "The NFT integrity check failed. The Digest does not match the NFT metadata." This happens because we modify the metadata on our side by embedding data from remarks into it, even though the original metadata still contains a reference to the thumbnail.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions