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
Consider that there are two artists A and B that both launch independent NFT collections C_a and C_b and then those implement function tokenURI but the JSON schema they are using is that for e.g. C_a the the audio manifestation is at the property mp3_link and for C_b it's at lossless_Audio.
Then potentially in this case, first of all, there is no generic "crawl this NFT collection" strategy
But also, we'd have to manually implement a transformer for C_a-get-tokenuri and for C_b-get-tokenuri
Additionally, in neume-network/data, since we're relying on e.g. block event logs information for tracking when an NFT was minted, someone like me with access to an Erigon full node also has to manually update the call-block-logs-transformation file
The text was updated successfully, but these errors were encountered:
function tokenURI
but the JSON schema they are using is that for e.g. C_a the the audio manifestation is at the propertymp3_link
and for C_b it's atlossless_Audio
.The text was updated successfully, but these errors were encountered: