Closed Kunkka0822 closed 1 year ago
From what I understood in the #294 discussion. We should track all tokenIDs and not only tokenID=1. From the tokenURI we can get trackNumber
. It will let us filter all the unique songs. If two tokenIDs have the same trackNumber then they are the same song.
Please correct me if I am wrong.
From what I understood in the #294 discussion. We should track all tokenIDs and not only tokenID=1. From the tokenURI we can get
trackNumber
. It will let us filter all the unique songs. If two tokenIDs have the same trackNumber then they are the same song.Please correct me if I am wrong.
yes all tokenURIs
From what I understood in the #294 discussion. We should track all tokenIDs and not only tokenID=1. From the tokenURI we can get
trackNumber
. It will let us filter all the unique songs. If two tokenIDs have the same trackNumber then they are the same song. Please correct me if I am wrong.yes all tokenURIs
Okay, I got it. I will work on this issue.
@Kunkka0822 is there a reason why this is a pinned issue?
- We need a
call-soundeditionv1-tokenuri
strategy to get thetokenUri
. The result is something likear://zUTuV0VL7w1z5cuGkBs2b-O3DRY2O2qA_ifSQqjLnzA/1
.
this is now done.
@Kunkka0822 the next step is taking all the called tokenURIs (which are Arweave links) and then sending type: arweave messages to the extraction-worker to download all the JSON objects.
@TimDaub Okay, I got it. So the next step will be sound-protocol-get-tokenuri.
May I implement feature to filter unique songs by tracknumber
in this part or not?
We definitely want that at some point but I'd leave it to your disgression where you think it fits best to implement it
@TimDaub I think this issue is already solved.
We need a
call-soundeditionv1-tokenuri
strategy to get thetokenUri
. The result is something likear://zUTuV0VL7w1z5cuGkBs2b-O3DRY2O2qA_ifSQqjLnzA/1
.We can get tokenUri from the sound edition contracts we found in #295. We should track Transfer events where tokenId is 1.
You can find detail information on #294