Decentralized Ticketing Platform

[GENERAL] Name and surname of main applicant

Sandro Schaier

[GENERAL] Email address of main applicant

sandro@schaier.io

Additional applicants

Sandro Schaier

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

The solution will depend on NMKR, because they are offering competitive fees to credit card payments, as well as the option to pay in FIAT for people new to blockchains.

And most importantly their solution is battle tested to scale and deal effectively with bots

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

No

[GENERAL] If NO, please describe which outputs are not going to be open source. If YES, please write “Project will be fully open source.”

The primary focus of this project is to provide a robust, user-friendly solution, offering all aspects of a modern ticketing platform.

An additional goal is to develop a decentralized and open system that serves as a foundation for other businesses to build upon. For instance, this could be by the creation of a ticket marketplace or similar concepts.

Those two goals are however not necessarily easy to combine.

For example developers of bots, might use the same API and documentation or open source code, intended to be used for legitimate use cases.

We will aim to provide the best solution by being as open as possible and therefore will let the community decide. By conducting a vote if the project should be fully or only partially open-sourced. Afterwards we will act accordingly.

Regardless of the decision we we will always give access and support legitimate businesses who want to build ontop of this platform.

This means, in practice we will initially, after the MVP launch, release only certain parts of the code and allow the community to decide on the release of the remaining critical parts later on.

[METADATA] Category of proposal

dApp

[IMPACT] Please describe your proposed solution.

One of the main drawbacks of centralized ticketing systems is the presence of numerous small competitors, each with different features, user flows, and data collection practices. This often results in a intransparent user experience, leading to confusion and frustration.

Additionally, feature limitations such as non existing ticket reselling, or the risk of purchasing invalid tickets can be a direct result.

Furthermore Bots frequently exploit these systems by purchasing tickets in bulk and reselling them at inflated prices, creating unfairness for genuine fans.

Not only that, but high fees associated with centralized ticketing solutions, both for attendees, in form of direct ticket fees and organizers in form of upfront fees, pose financial barriers that prevent smaller events from utilizing (good) online ticketing services.

By building our ticketing platform on Cardano, we can leverage the benefits of native tokens and enable the interaction with smart contracts and customized solutions.

NMKR's battle-tested bot prevention and high scalability features eliminate the need for additional payment infrastructure, providing a seamless payment experience.

Moreover, the inclusion of FIAT payment options offered by NMKR ensures an accessible solution for new users. Which is ideal since our goal is to provide a user-friendly experience where individuals who prefer not to set up custom wallets can still participate by using a custodian wallet.

This approach results in an enhanced user experience (UX) and enables real-world use cases, beyond the Cardano community.

To measure the impact of our solution, we can track the number of custodian wallet users. By assuming that individuals with existing wallets will continue using them, we can observe the real world adoption rate of new users utilizing our custodian wallet option. This metric then serves as an indication of the impact and acceptance of our platform and Cardano.

[IMPACT] How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

From a feature perspective, our decentralized ticketing platform will provide

• users with both a mobile app and a website. Through these platforms, users will be able to view their tickets and generate offline QR codes for entry. They will also have the flexibility to link existing wallets of their choice to their account or use a built-in custodian wallet.

• For event organizers, we offer a dedicated webpage where they can set up events, create various ticket types, and manage other aspects related to their events. These events will be linked to an NFT collection or NMKR Project.

• Moreover, organizers will have access to an app specifically designed for ticket validation, allowing them to scan and verify tickets even in offline environments.

The impact of our project will happen in two main stages:

In the initial stage, we will launch a Minimum Viable Product (MVP), primarily targeting the Cardano community.

This will enable us to gather valuable feedback and insights to further enhance our solution. We are currently in discussions with potential event partners who have expressed interest in utilizing our platform, although we cannot provide concrete numbers at this stage of the project.

In the second stage, we will introduce custodian wallets and streamline the user experience to match the simplicity of centralized solutions.

By leveraging scalable cloud infrastructure, our platform will be capable of accommodating events with thousands of tickets, ensuring smooth and efficient ticketing operations and generating lots of transactions on the blockchain.

[IMPACT] How do you intend to measure the success of your project?

As mentioned earlier, we have identified a means of indirectly measuring how many new users we bring to the Cardano ecosystem by tracking the number of custodian wallet users.

This metric serves as an indicator of real-world adoption and will be publicly shared to provide transparency and insights.

In addition to quantitative measurements, we place great emphasis on gathering qualitative feedback to improve the usability and efficiency of blockchain solutions in real-world scenarios.

We believe in the power of sharing and aim to share our key learnings and takeaways with other projects that are focused or interested on achieving real-world adoption.

By doing so, we hope to contribute to the ecosystem as a whole, and show a way for "early" adopter

[IMPACT] Please describe your plans to share the outputs and results of your project?

The codebase, subject to a vote, will be made available as open source, either in its entirety or partially. This aims to provide newer dApp developers with a starting point and reference to them in building their own ideas.

Nevertheless, our primary focus is on driving real-world adoption, which in turn will bring indirect benefits to the Cardano community.

To facilitate this, we will create documentation and APIs, enabling other businesses to seamlessly connect with and enhance our solution. For example, they could utilize our infrastructure to build a ticket sale marketplace or explore similar possibilities.

By developing for collaboration and offering options for integration, we aim to create a robust ecosystem that encourages innovation and features beyond the traditional ticketing solutions.

Furthermore we aim to provide other real world projects help and guidance to speed up cardano adoption in general

[CAPABILITY/ FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability?

I am a student pursuing a Master's degree in Computer Science and Economics. My previous experience includes working on several Cardano projects, where I have been involved in tasks such as developing authentication flows for HHMC and other projects, creating custom scripts for large-scale NFT projects, and working on internal projects for NMKR.

In addition, I am also the developer for Whiskees NFTs. A project focusing on crowd investments in whiskey casks. The project recently purchased the first batch of whiskey casks using funds entrusted to us by the community.

Outside the cardano ecosystem I am also working as a freelance developer on various web/app projects. Gainig experience in real world development.

Besides the technical side, there is the business side by working as a freelancer. Furthermore by regularly approaching clients I think I also gained some insights into working with real world businesses.

Building on my background, I have spent the past two months building upon this idea, conducting market research, defining technical requirements, and starting the development of an MVP codebase.

These efforts have laid the groundwork for the project's initial stages and hopefully show that I can be trusted.

[CAPABILITY/ FEASIBILITY] What are the main goals for the project and how will you validate if your approach is feasible?

Our primary objective is to develop a real-world project that provides a better ticketing solution compared to centralized systems, for cardano and even new users.

To achieve this long-term goal, we have established several sub-goals which we will work towards initially.

Generally our approach involves rapid development and actively seeking feedback from events, with focus on the Cardano community first. This feedback will help us validate our solution and identify areas for improvement.

Afterwards we will also implement specific improvements to accommodate new users, such as incorporating custodian wallets and similar functionalities.

By following this approach, we aim to gradually refine and enhance our solution, ultimately delivering a high-quality ticketing system that surpasses traditional centralized alternatives, even for users beyond the Cardano ecosystem.

[CAPABILITY/ FEASIBILITY] Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

As mentioned earlier, I have conducted market research, worked out technical details, and have made significant progress (80% completion) on an MVP codebase in the previous 1,5 months. Additionally, there are some potential events that have shown interest in utilizing this solution.

Those steps will not be included in the following

Milestones are:

1. Complete MVP (End of July)
2. Task -> Build a functioning prototype
3. (Android App) for Organiser to validate tickets (offline)
4. Web page for users with account system to link their wallets and generate QR-Codes from their NFTs
5. Backend infrastructure, scalable and reliability first
6. Success -> Usable MVP with first users
7. Gather feedback and build improvements (Mid September)
8. Task -> Gather valuable feedback and improve solution
9. Focus on feedback from cardano community
10. Testrun with event
11. Add smaller quality of live improvements
12. Release Event organiser webpage to setup events, link them to NMKR-NFT projects, grant access to validate tickets...
13. Release user app
14. Release both apps publicly for iOS and Android (Stores) and in open source stores (Android)
15. Success -> Release of improved Apps
16. Build custodian wallet solution (Mid - End Oktober)
17. Task -> Integrate a custodian wallet in existing systems/apps
18. Offer seamless experience for new users
19. Export of wallets
20. FIAT payments with wallet
21. Success -> Open source code of wallet released, Systems updated
22. Code reworks and documentation for open source release (Early November)
23. Task -> Document and make project open source
24. Vote on which parts to publish (with or without bot critical parts)
25. Code cleanup
26. Code documentation
27. User guides
28. Success -> Public release of source code

[CAPABILITY/ FEASIBILITY] Please describe the deliverables, outputs and intended outcomes of each milestone.

Milestone

1. Complete MVP (End of July)
2. Deliverable
3. MVP, Including Organiser App (initially Android), Webpage for users and backend infrastructure
4. Output
5. Fully usable prototype with necessary functionality
6. Intended outcomes
7. Work with some small scale events to evaluate the product
8. Measurements
9. Based on qualitative feedback from the community and selected events
10. Gather feedback and build improvements (Mid September)
11. Deliverable
12. Platform usable and easy to signup for organisers, fully working ticketing
13. Output
14. Improves Apps, Improvement on website
15. Intended outcomes
16. Gather more feedback and work out problems by opening the solution to a public audience of organisers
17. Measurements
18. Amount of usage (Ticket sales) and Organiser user
19. Build custodian wallet solution (Mid - End Oktober)
20. Deliverable
21. Easy to use custodian wallet integration
22. Output
23. Updates to the whole system
24. Intended outcomes
25. Make it frictionless for users outside the cardano ecosystem
26. Measurements
27. Users of the custodian wallet and events organised by people outside of the community
28. Code reworks and documentation for open source release (Early November)
29. Deliverable
30. Publish the source code
31. Output
32. Either partial or full release of the source code on GitHub
33. Intended outcomes
34. Give new dApp developers a reference and make it easier for potential cooperations
35. Measurements
36. Feedback through GitHub (Stars, Forks, PR, Feature Requests ...)

[RESOURCES & VALUE FOR MONEY] Please provide a detailed budget breakdown of the proposed work and resources.

The budget plan will mention completed steps, however will assign 0 ADA.

Furthermore the plan is stating (external) for estimated costs for external services.

Costs marked with (internal) are development costs to work full time on the project.

• Market research
• completed (0 ADA)
• Technical research
• completed (0 ADA)
• Legal costs
• 2.500 ADA (external)
• Company and organisational setup
• 1.500 ADA (external)
• Development costs
• Milestone 1
• MVP initial codebase
• completed (0 ADA)
• Finish MVP
• Backend
• 2.000 ADA (internal)
• Organiser App
• 3.500 ADA (internal)
• Milestone 2
• Improvements based on feedback and quality of live
• 4.500 ADA (internal)
• Event organiser page (including backend)
• 6.500 ADA (internal)
• User companion app
• 8.000 ADA (internal)
• Milestone 3
• Custodian wallet update (including backend, apps ...)
• 10.000 ADA (internal)
• Milestone 4
• Code cleanup and refactoring for open source release
• 1.500 ADA (internal)
• Infrastructure cost
• Separate Google and Apple Accounts for release
• 400 ADA
• Domain
• 100 ADA (external)
• Hosting and Cloud
• 50 ADA/month (=250 ADA)
• Other costs (email, cloud services)
• 50 ADA/month (=250 ADA)
• Travel expenses
• Attend events in the MVP stage
• 1.500 ADA (external)
• Marketing
• 10.000 ADA (external)
• Community manager and support
• 500 ADA/month (=2.500 ADA)

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

I directly benefit from costs totaling 36,000 ADA or approximately $10,000 (excluding external costs). Considering an estimated duration of 4-5 months for the project, this translates to a monthly income of $2,000-$2,500, which is considerably lower than the average wage in Germany. This calculation does not account for taxes, insurance, and other expenses.

Considering these factors, I believe these costs are reasonable and will cover the basic cost of living, even after considering taxes and insurance.

In addition to these direct costs, there are other estimated expenses, such as legal expertise required for custodian wallets and ensuring to meet regulatory requirements.

Travel expenses may also be necessary to attend and support events following the initial launch.

[IMPORTANT NOTE] The Applicant agreed to Fund10 rules and also that data in the Submission Form and other data provided by the project team during the course of the project will be publicly available.

I Accept