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

Create First Chainlink function #16

Closed
criadoperez opened this issue Jun 13, 2024 · 5 comments · May be fixed by #24
Closed

Create First Chainlink function #16

criadoperez opened this issue Jun 13, 2024 · 5 comments · May be fixed by #24
Assignees

Comments

@criadoperez
Copy link
Contributor

criadoperez commented Jun 13, 2024

We need to create a chainlink function a first testcase.

This will detect the generation of a new ISRC, check it's validity (format of file) and output a binary output to confirm if file is valid or not.

@criadoperez criadoperez moved this to In Progress in Original Works Project Jun 13, 2024
@criadoperez criadoperez changed the title Confirm the cost of Chainlink functions Create First Chainlink function Jun 19, 2024
@criadoperez
Copy link
Contributor Author

As we are now using DDEX messages instead of json file we should validate this with an ERN xml file.
@0xbarath you have a sample here

@criadoperez
Copy link
Contributor Author

@criadoperez
Copy link
Contributor Author

@0xbarath please take a look at sections 7.3 and 7.4 of the web3 nft ddex document.
These allowed value sets and schema validation refered on the document might the first checks the chainlink functions will have to make.

@criadoperez
Copy link
Contributor Author

One way to approach this is for Original Works to create an XML Schema Defiintion (XSD) for every XML message we can receive.

The Chainlink function will need to validate the XML message against the XSD and check for allowed value sets.

The XSD has to be of course compliant with DDEX but as well makes it even more strict, meaning that not only it has to be a DDEX standard but also have the fields the protocol needs to operate. For this we need to define the fields to add in the XSD file. @revelatorltd , @denciu , we can review these fields tomorrow

@criadoperez criadoperez linked a pull request Jul 4, 2024 that will close this issue
@criadoperez
Copy link
Contributor Author

@0xbarath please provide the status of this here. Thank you.

@criadoperez criadoperez added this to the v0.2.2 New Data model milestone Jul 15, 2024
@revelator-labs revelator-labs closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
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

Successfully merging a pull request may close this issue.

3 participants