Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For indie artist contracts we may have the problem of having to create many transformers and extractors #314

Open
TimDaub opened this issue Oct 11, 2022 · 0 comments

Comments

@TimDaub
Copy link
Collaborator

TimDaub commented Oct 11, 2022

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant