CIP-60 Music Metadata Enrichment Tooling

[GENERAL] Name and surname of main applicant

Gabriel Talamantes

[GENERAL] Are you delivering this project as an individual or as an entity (whether formally incorporated or not)

Entity (Not Incorporated)

[GENERAL] Requested funds in ada

200000

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

10

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language

No

[GENERAL] Summarize your solution to the problem (200-character limit including spaces)

Tools that simplify the creation of CIP-60 compliant tokens provide developers with the framework to build immersive experiences for users, as well as connecting them to external music libraries.

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

Yes

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.”

While the resulting code aims to be as self-contained as possible, the underlying services do require access to external, albeit redundant, libraries and databases. They are as follows:

MusicBrainz API - (open-source) database for submitting and cross-referencing music repertory

Spotify API - (proprietary, public) fallback music repertory source for cross-referencing existing music

Librosa - (open-source, local copy) music and audio analysis

ACRCloud - (proprietary, public) song-identification and fingerprinting service

[GENERAL] Will your project’s output/s be fully open source?

Yes

[GENERAL] Please provide here more information on the open source status of your project outputs

All code outputs of this project are planned to be made available under an MIT License to allow for mass adoption and implementation across many applications.

[METADATA] Horizons

Developer Tools

[SOLUTION] Please describe your proposed solution

Creating tokens on a permissionless blockchain allows for many data structures to be implemented. While this is a great freedom provided to the ecosystem, the creation of standards allows utility and mature communities to develop and scale. The music ecosystem on Cardano is no different.

CIP60-v3 revisions were initiated to position the existing music standard to allow for more interactability and better user experiences to be created. However, the standard itself offers no enforcement mechanisms to ensure tokens follow the outlined structure, becoming an obstacle for developers.

Cardano has developed a strong music community, and the existing standard offers a great avenue for artists to create and document the works they produce, offering an analog to copyright registration. However, qualifying these releases and cataloging/indexing them are vital to enable verification, searchability, and monetization of such works.

The first phase in this proposal is the generation of CIP60-compliant metadata tooling that assists in the creation of CIP-60 compliant tokens. This will provide a user interface where users can input all the required information about the song(s) in question and generate JSON formatted with the schema outlined in CIP60-v3.

Once metadata has been properly formatted, the next phase of this proposal is to generate tooling that can validate the songs being uploaded against music databases using external libraries and services like ACRCloud and Librosa for audio fingerprinting and analysis. While optional, such services allow for verification layers to be built into dApps such as marketplaces to prevent infringement of established works, as well as identifying covers and derivate works. Other features, like genre and rhythm detection can also be leveraged.

Once the song(s) in question have gone through the optional validation, the resulting data can then be minted on chain, either with transaction-builder SDKs or other custom tooling, or minting services such as NMKR. The song information can then be pushed to external music libraries, such as MusicBrainz. This will allow these works to be discoverable outside of the Cardano ecosystem.

[IMPACT] Please define the positive impact your project will have on the wider Cardano community

Creating the potential for immersive audio experiences on Cardano will not only elevate the developing music community already established but increases the potential for growth to Cardano as a whole, attracting music creators from all walks of the industry.

[CAPABILITY & FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

Many shortcomings of the implementation of the previous versions of CIP-60 were discovered during the development of Arp Radio. To prevent future tokens from following suit, many of the authors of CIP60-v3 are listed as proposers of this project. Having a comprehensive understanding of the correct implementation of the standard, as well as the potentials it enables, the current team is highly capable of developing the services listed above. These services are vital in expanding the functions of projects team members have already begun development on and will serve the ecosystem at large as open-source tooling.

[PROJECT MILESTONES] What are the key milestones you need to achieve in order to complete your project successfully?

Project Inititation

• Assignment of roles and responsibilities
• Technical Outlining and stack determination
• Creation of Project Treasury wallet utilizing Multi-sig wallet
• Roadmap Finalization
• Registration of required services

Duration - 1 month

CIP60-compliant Metadata Generation UI Development

• Design user interface
• Develop backend for JSON generation
• Implement CIP60-v3 schema
• Testing and bug fixes

Duration - 2 months

Audio Validation Tool Development

• Integration with ACRCloud and Librosa
• Implement audio fingerprinting and analysis features
• Testing and optimization

Duration - 3 months

External Music Library Integration

• Develop integration with MusicBrainz
• Implement API for musical work submission to MusicBrainz
• Testing and optimization

Duration - 2 months

User Testing and Refinement

• Conduct user acceptance testing
• Gather and implement feedback
• Testing implementations with existing projects

Duration: 2 months

[RESOURCES] Who is in the project team and what are their roles?

John Nickell - Full Stack Developer/QA Tester - LinkedIn

• Backend/API Development
• Frontend development
• Advises writers drafting user and technical documents
• Product Testing

Gabriel Talamantes - Full Stack Developer/Project Administrator - LinkedIn

• Backend/API Development
• Frontend development
• Ensures adherence to CIP60
• Advises writers drafting user and technical documents
• Management and Oversight of Timelines and Budget
• Project Oversight
• Advises team on applicable music standards

Samuel Hogan - Project Administrator/QA Tester - LinkedIn

• Management and Oversight on Timelines and Budget
• Product Testing
• Ensures adherence to CIP60
• Project Oversight
• Assists in the drafting of user documentation
• Assists in the drafting of technical specifications

Nicodemus Rodriguez - Technical Writer/Project Administrator - LinkedIn

• Management and Oversight on Timelines and Budget
• Creates user documentation and guides
• Drafting of technical specifications
• Project Oversight

Rikardo Rodriguez - Music Artist/QA Tester - LinkedIn

• Assists in the drafting of user documentation
• Assists in the drafting of technical specifications
• Product Testing

Corey Banks - Music Industry Advisor/QA Tester - LinkedIn

• Product Testing
• Advises Dev Team on applicable music standards

[BUDGET & COSTS] Please provide a cost breakdown of the proposed work and resources

Labour & subcontracting costs - ₳120,000

• Development fees ₳60,000
• QA testing ₳10,000
• Advisor fees ₳20,000
• Copywriter fees ₳10,000
• Administrator fees ₳20,000

Overhead - ₳35.000

• VPS rental / Bare Metal equipment cost ₳20,000
• Electricity Costs ₳15,000

Licensing in technologies - ₳5,000

• ACRCloud services ₳5,000 reserves

Unforeseen Expenses Reserve - ₳40,000

---------------------------------------------------

₳200,000

[VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

With the creation of tooling empowering music tokens to connect to services outside blockchain, Cardano has the potential of creating a verifiable and legitimate repertory of music that is not present on other platforms, allowing for great growth to the chain's user count. Music tokens, unlike other tokenized assets, already have underlying value creation potential as the works themselves can be monetized in various ways, attracting the music economy at large.