neume-network / neume-network/data
For platforms like soundxyz that implement custom editions, attempt to filter by unique audio manifestations and see if editions get reduced to unique works
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- soundxyz implements editions such that each tokenId is an NFT but can at the same time be an edition
- Two NFTs can have practically the same metadata (with some minor differences) but be editions of one another
- So the question is: How can we detect editions efficiently without having to deal with the many implementations. What's the common denominator?
- One idea was for each Soundxyz NFT to reduce it its audio manifestation and to then check if that reduces all event logs down to the actual newly created media files
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how Sound.xyz token metadata and event logs are represented, then determine whether reducing NFTs to unique audio manifestations consistently collapses editions to unique works without platform-specific assumptions. Done means a documented approach and validation criteria for detecting editions efficiently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, javascript
- Domain
- blockchain, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100