cip25 (NFT) Rust & WASM library

[IMPACT] Please describe your proposed solution.

Currently, there is no native Rust library that supports CIP25. That means Rust projects that many users depend on such as Oura, Carp, CSL and CML all have ad-hoc implementations of CIP25 parsing. This is unfortunately because it allows limited indexing of CIP25 data using these tools and, in the worst case, can lead to subtle errors on CBOR parsing.

We plan to solve this by writing a native Rust library for CIP25 parsing that makes use of dcSpark's latest work on transaction metadata library codegen based off CDDL specifications. We intend to also make this library usable from WASM and therefore Typescript as well which should be usable from most Cardano projects.

[IMPACT] Please describe how your proposed solution will address the Challenge that you have submitted it in.

Currently developer tools written in Rust have ad-hoc implementations of CIP25 which restricts the functionality they can support and increases the chance of subtle bugs. This library will make it easier to write dev tools in Rust, WASM-compatible languages and Typescript that need to consume the CIP25 standard

[IMPACT] What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?

CIP25 is just a standard for Cardano and a lot of NFT projects have made mistakes in its implementation due to the lack of a CIP25 library like the one we are proposing to create. That means this library won't be able to parse these projects properly. Future work may be required to loosen the format to allow for these projects to be supported

[FEASIBILITY] Please provide a detailed plan, including timeline and key milestones for delivering your proposal.

1. Update the cddl-codgen to implement any feature that was needed for NFT support that was not covered under https://cardano.ideascale.com/c/idea/419158
2. Generate the core (de)serialization logic from the CDDL definition
3. Add utility functions as needed
4. Publish as a crate & NPM package
5. Integrate in projects such as Carp & Oura

[FEASIBILITY] Please provide a detailed budget breakdown.

All funds will be used towards the development costs of the project

[FEASIBILITY] Please provide details of the people who will work on the project.

Github handles are SebastienGllmt and rooooooooob

[FEASIBILITY] If you are funded, will you return to Catalyst in a later round for further funding? Please explain why / why not.

No, unless there is a large breaking change to CIP25 in the future that requires a significant rewrite (no such thing planned)

[FEASIBILITY] Are you or any member of your team working on any other proposals in this Fund9?

[FEASIBILITY] Are you or your team working on any other proposals from previous Funds?

[AUDITABILITY] Please describe what you will measure to track your project's progress, and how will you measure these?

Progress towards the implementation as outlined by the steps mentioned above

[AUDITABILITY] What does success for this project look like?

Successful release of this project and having it integrated into other tools

[AUDITABILITY] Please provide information on whether this proposal is a continuation of a previously funded project in Catalyst or an entirely new one.

New project