Open-Source Datum Explorer: Decode, Understand, Build

[GENERAL] Name and surname of main applicant

Catalyst Rider

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

Entity (Incorporated)

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

5

[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)

We will create an open-source tool to decode CBOR data into a readable format, with a public registry for datum and redeemer schema definitions.

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

No

[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.”

No dependencies.

[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

Both GitHub repositories will be open-source, with MIT license:

• Registry
• Library + example FE

[METADATA] Horizons

Developer Tools

[SOLUTION] Please describe your proposed solution

The project aims to create a tool that simplifies the decoding of on-chain data, specifically datums and redeemers, on the Cardano blockchain. Currently, developers face challenges when dealing with CBOR-encoded data, as existing tools require manual effort to match data against specific schemas, leading to a cumbersome and error-prone process. Our solution provides an open-source tool that effortlessly converts CBOR data into a more accessible and human-readable format.

This tool will help developers by offering a seamless experience, saving time and reducing errors when working with on-chain data. By creating a public registry of datum and redeemer definitions, this project encourages a collaborative ecosystem where projects can share and use standardized schemas. Ultimately, this solution makes on-chain data more transparent and usable, benefiting the broader Cardano community by supporting more efficient and error-free development.

Project Overview:

1. Public Registry:
2. We will establish a public registry on GitHub where projects can host their datum and redeemer definitions. Our focus will be on optimally representing these definitions based on the CDDL specification, allowing individual elements to be named. The registry will also support type parameters, including inheritance and unions (e.g., Maybe = Just | Nothing).
3. Open-Source Library:
4. An open-source library will be developed, providing a function that converts CBOR into an object. This internal representation can be utilized by third parties—such as blockchain explorers, wallets and browser/IDE extensions—to display data in a custom way.
5. Front-End Application:
6. We will create and host an open-source front-end tool that allows users to paste CBOR data and view the readable datum according to a schema selected from the GitHub registry. The tool will also support locally defined schemas.

Example of Datum Decoding:

• Original CBOR:
• d8799fd87a80d87a801b0000019246e0ed9800ff
• Decoded via cbor.me:
• 121_0([_ 122_0([]), 122_0([]), 1727765999000_3, 0])

Decoded via Cardano explorers (Cexplorer, Cardanoscan):

{

    "fields": [

        {

            "fields": [],

            "constructor": 1

        },

        {

            "fields": [],

            "constructor": 1

        },

        {

            "int": 1727765999000

        },

        {

            "int": 0

        }

    ],

    "constructor": 0

}

Proposed more readable representation (table-aligned, expandable, with tooltips for field descriptions / formatting of timestamps / …)

WingRiders Launchpad node

(Node)

  key: (Nothing)

  next: (Nothing)

  createdTime: 1727765999000

  committed: 0

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

Our project will enhance the Cardano community by improving accessibility and understanding of CBOR data, which is vital for developers and users interacting with smart contracts. By providing a user-friendly tool to decode CBOR into a readable format, we empower developers to create better applications and increase transparency for users. The community is already familiar with the token metadata and contracts registries, which positions us for similar adoption.

Developers and Technical Users: The tool will make it easier for developers to interact with on-chain datums and redeemers by simplifying CBOR decoding. This reduces the development time and risk of errors when working with smart contracts. It also supports development by providing standardized schemas and a collaborative registry, fostering a unified approach to data handling.

Emerging Projects: New projects will benefit from the shared registry of datum and redeemer definitions, allowing them to build upon existing standards rather than reinventing data structures. This helps in quickly establishing their systems, saving resources and improving compatibility within the ecosystem.

Established Projects: Established projects will benefit from better data transparency and the availability of standardized tools for data decoding. This facilitates easier integrations, especially when working with other DApps, and supports growth by providing reliability in on-chain data management.

Blockchain Explorers and Wallets: Tools like blockchain explorers and wallets can utilize the library to present on-chain data in a more readable format, making data interpretation easier for both developers and end users. This enhances user experience and trust by offering transparency in the transactions and data on the Cardano blockchain.

Broader Cardano Community: Making on-chain data accessible and understandable contributes to overall network transparency. By allowing users—both technical and non-technical—to better understand what is happening within the blockchain, this tool indirectly fosters trust and promotes a more engaged and informed community.

Stake Pool Operators (SPOs): As the tool aids developers in building and integrating applications more efficiently, this could drive increased usage of the Cardano network. In turn, increased network activity leads to more transactions, potentially raising rewards for SPOs through higher staking activity.

Knowledge Sharing and Education: By providing a public registry with open access to datum and redeemer schemas, this project enhances the collective knowledge base of the Cardano developer community. This supports continuous improvement and collaboration, ultimately contributing to the technological advancement of the ecosystem.

Measuring Impact:

1. Quantitative Metrics:

• User Engagement: Track the number of users of our front-end tool and GitHub repositories, including downloads.
• Adoption Rate: Monitor projects using our CBOR decoding library and the datum definitions registry.
• Community Contributions: Measure code contributions and new datum definitions added to our GitHub repository.

1. Qualitative Metrics:

• User Feedback: Collect feedback through surveys and interviews to assess usability.
• Case Studies: Document specific instances where our tool has improved CBOR data interpretation.

Sharing Outputs:

We will share our outputs through various channels:

• GitHub Repository: Host the tool and documentation for public access.
• Social Media and Blogs: Provide regular updates on development progress and user testimonials.

[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?

As WingRiders, we have a track-proven record of developing within the Cardano ecosystem. Over the years we’ve shown to be at the forefront of technological advancements when it comes to DEXes and Cardano in general. We were the first ones to bring support for Stableswaps, have a fully on-chain DAO governance, launched the first trustless non-custodial launchpad and recently V2 smart contracts with optimized transaction batching, new features such as Routed Swap, PathFinder, ZapIn/ZapOut and much more. All along the way we were working with Cardano data encoded in CBOR. Created a lot of open source tooling and continues to push the edge of what is possible with the Cardano chain evolving. 

Regarding fund management, we adhere to rigorous protocols ensuring robust financial stewardship and accountability. Our practices encompass the maintenance of transparent financial records, periodic internal audits, and strict compliance with financial reporting standards. We understand the imperative nature of prudent fund management and commit to upholding the highest standards of fiscal responsibility throughout the project's lifecycle.

As evidence, we have 2 Catalyst proposals from F10 and F11 with Proof of Achievement submitted and approved for all completed milestones except the final milestones, which are in progress. Two proposals from F12 are having Milestones 1 and 2 submitted ahead of the schedule. 

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

 Research , Design Phase and Development of the CBOR Decoder Library

• Description: Conduct thorough research on CBOR data structures and the CDDL specification to define the optimal representation of datum definitions. Build the open-source library for decoding CBOR data into a structured object format, according to the Design document.
• Milestone Outputs: 
• A detailed design document outlining the proposed architecture for the decoding tool and registry.
• A list of datum definitions to be included in the registry.
• The functional CBOR decoding library with comprehensive documentation.
• Unit tests covering the core functionality.
• Acceptance Criteria:
• Design document clearly states and explains the architecture for the decoding tool and registry is in the open source GitHub repository.
• A list of at least 10 datum definitions to be included in the registry.
• Code is working and documented.
• All unit tests pass.
• Evidence: 
• Link to the Design document in the open source GitHub repository.
• Link to the list of datum definitions in the open source GitHub repository.
• Link to the open source GitHub repository containing documented code.
• Link to the tests results in the open source GitHub repository
• Timeline: 1 month

Public Registry Setup and Backend Integration

• Description: Create a public GitHub repository for hosting datum and redeemer definitions and schemas, along with backend code for fetching the registry to serve for the front-end application.
• Milestone Outputs:
• A GitHub repository containing the registry with at least 10 well-documented datum definitions.
• Backend code for fetching registry data from the GitHub repository 
•  Endpoint for frontend and 3rd parties.
• A README file explaining how to use the registry and contribute new definitions.
• Acceptance Criteria:
• The repository is publicly accessible and contains at least 10 datum definitions.
• Backend code is functional.
• Endpoint is working and response contains definitions from GitHub repository
• README file has sections
• How to use the registry.
• How to contribute new definitions.
• Evidence: 
• Link to the public GitHub repository.
• Link to the open source GitHub repository containing backend code.
• Screenshot of endpoint response corresponding to GitHub repository definitions.
• Link to the README file.
• Timeline: 2 weeks

Front-End Tool Development

• Description: Develop an open-source front-end tool that allows users to paste CBOR data, select schema, and display readable datum representation. It will fetch cached schemas from backend and will suggest matching schemas based on the pasted CBOR.
• Milestone Outputs:
• Front-end with features:
• Display schemas fetched from backend endpoint
• Select schema
• Decode CBOR data according to schema
• Documentation and a video tutorial on using the front-end tool.
• Acceptance Criteria:
• Code is in the open source GitHub repository.
• The application displays readable representations of CBOR data.
• Users can select schemas or accept suggestions.
• Complete documentation and a tutorial video are provided.
• Evidence: 
• Link to the open source GitHub repository.
• Video showing data provided by the endpoint is visible in the front-ent and ability to select schemas or accept suggestions.
• Timeline: 1 month

Community reach out and marketing

• Description: Provide regular updates on proposal progress through social platforms, including Twitter and Discord. Gather feedback on those updates and github repository and address any major issues, if any.
• Milestone Outputs: Marketing Report Document listing all the updates regarding project progress, feedback on those updates and github repository, list of major issues, fixes for those issues.
• Acceptance Criteria: Marketing Report Document has 4 chapters:
• Social updates: lists all relevant reports on social media and feedback (Twitter and Discord).
• GitHub feedback: lists all the feedback on GitHub repository (empty if none found).
• Major issues: lists all the major issues from all the feedback (empty if none found).
• Issue Fixes: lists all the commits in the GitHub that fix issues found in feedback (empty if none found).
• Evidence: Marketing Report Document provided to the review team.
• Timeline: 1 month

Project Close-out Report and Project Close-out Video

• Description: Create final project completion report and video.
• Milestone Outputs:
• A 2/3 page written summary ‘Project Close-out Report’.
• Short video ‘Project Close-out Video’.
• Acceptance Criteria:
• Project Close-out Report’ listing KPIs and how they were (or were not) addressed and what the next stage plans are with the product or service that was developed.
• Project Close-out Video’ outlining the project achievements and deliverables.
• Evidence:
• Final project report available on a publicly-accessible link.
• Video available on a publicly accessible link.
• Timeline: 1 week

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

List your team, their Linkedin profiles (or similar) and state what aspect of the proposal’s …

WingRiders engineering team is composed of experienced professionals in blockchain technology and software development. Our team members stand behind projects like Adalite, Yoroi wallet, Emurgo’s first blockchain explorer/indexer, firmware for hardware wallets Trezor and Ledger (bringing them to Cardano), and WingRiders DEX and LaunchPad.

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

Milestone 1: Research, Design Phase & Development of the CBOR Decoder Library

1. Milestone Budget: ₳ 60,000
2. Resource MDs: 
3. Software engineer (senior & junior): 32
4. Project manager: 6

Milestone 2: Public Registry Setup and Backend Integration

1. Milestone Budget: ₳ 55,000
2. Resource MDs: 
3. Software engineer (senior & junior): 29
4. Project manager: 3

Milestone 3: Front-End Tool Development

1. Milestone Budget: ₳ 55,000
2. Resource MDs: 
3. Software engineer (senior & junior): 29
4. Project manager: 5

Milestone 4: Community reach out and marketing

1. Milestone Budget: ₳ 20,000
2. Resource MDs: 
3. Software engineer senior: 1
4. Marketing Specialist: 12
5. Project manager: 2

Milestone 5: Project Close-out Report and Project Close-out Video

1. Milestone Budget: ₳ 10,000
2. Resource MDs: 
3. Marketing Specialist: 6
4. Project manager: 1

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

The costs of our project represent excellent value for the Cardano ecosystem by addressing the critical need for effective and accessible tooling. Tooling is the backbone of ecosystem growth—well-designed tools empower developers to create, iterate, and deploy projects faster and with greater confidence. By simplifying CBOR data decoding, our project reduces the barriers for developers and opens opportunities for more projects to flourish on Cardano. More projects mean more adoption, which ultimately strengthens the entire ecosystem.

Investing in developer tooling like this is an investment in Cardano’s future scalability and sustainability. With easier access to essential tools, we will see increased participation from new developers and projects, which in turn leads to a richer variety of DApps and services available to users. This growth drives adoption, resulting in a broader and more engaged user base, further reinforcing the value of the Cardano network.

Furthermore, our project contributes to increased decentralization—a core principle of blockchain technology. By providing an open-source library and a public registry, we enable diverse projects to independently leverage, improve, and share knowledge. This type of decentralization strengthens the ecosystem by preventing reliance on any single entity for essential tools and definitions, thus promoting resilience.

Knowledge sharing is another key value driver in this project. The public registry and open-source nature of the tooling are designed to foster community collaboration and the collective advancement of Cardano. By making our tools and resources accessible, we help developers learn from each other, improve efficiency, and accelerate the overall growth of the ecosystem.

These benefits—accelerated project development, increased adoption, enhanced decentralization, and the promotion of a collaborative knowledge-sharing culture—are the real values that will pay off in the long term for Cardano. Each ADA spent on this project contributes not only to its immediate utility but also to the long-term robustness, inclusiveness, and scalability of the ecosystem.