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

Implement CAIP-19 - neume IDs #17

Open
reimertz opened this issue May 25, 2022 · 2 comments
Open

Implement CAIP-19 - neume IDs #17

reimertz opened this issue May 25, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@reimertz
Copy link
Member

We currently create our own ID mapping combining address and tokenURI for each track generated by neume.

Preferably, neume would do this and include an id entry in the schema

Example: Sound.xyz Snoop Dogg Death Row Session: Vol. 2 (420 Edition) #563

eip155:1/erc721:0x37A03D4AF1D7046d1126987b20117A0FdCBF6535/680564733841876926926749214863536423475

Reference: CAIP-19

@reimertz reimertz added the enhancement New feature or request label May 25, 2022
@TimDaub
Copy link
Collaborator

TimDaub commented May 25, 2022

Great idea. Additionally, within neume-network/schema we could ask for a string to have a certain "format" or "pattern" using e.g. a regular expression put forth by CAIP

@TimDaub TimDaub transferred this issue from neume-network/core Jun 2, 2022
@TimDaub
Copy link
Collaborator

TimDaub commented Jun 2, 2022

I transferred this issue to the schema repository to get started on it by defining how an ID could be included into the schema. The data itself, e.g. the collection's address and tokenID, we already have in the strategies...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants