[Proposal setup] Proposal title
Please provide your proposal title
FairMint Tickets: Anti‑Scalping Ticketing on Cardano
[Proposal Summary] Budget Information
Enter the amount of funding you are requesting in ADA
52000
[Proposal Summary] Time
Please specify how many months you expect your project to last
6
[Proposal Summary] Translation Information
Please indicate if your proposal has been auto-translated
No
Original Language
en
[Proposal Summary] Problem Statement
What is the problem you want to solve?
Online ticketing suffers from scalping, counterfeits, and chargeback abuse. Organizers lose revenue and trust. We’ll enforce fair sales and verifiable resale on Cardano with on-chain authenticity.
[Proposal Summary] Project Dependencies
Does your project have any dependencies on other organizations, technical or otherwise?
Yes
Describe any dependencies or write 'No dependencies'
Cardano ecosystem access and stable mainnet/testnet availability. Wallet compatibility (e.g., Lace, Eternl) and ADA for payments.
[Proposal Summary] Project Open Source
Will your project's outputs be fully open source?
Yes
License and Additional Information
MIT License (contracts, SDKs, apps)
[Theme Selection] Theme
Please choose the most relevant theme and tag related to the outcomes of your proposal.
Smart Contracts
[Campaign Category] Category Questions
Describe what makes your idea innovative compared to what has been previously funded (whether by you or others).
FairMint Tickets innovates by combining on-chain ticket minting with programmable smart contracts that enforce resale price caps, organizer royalties, and anti-bot deposits—features not enabled by typical NFT ticketing projects. Unlike prior solutions, it uses Cardano’s Hydra protocol for high-speed sales and venue scans while anchoring audit trails to L1, reducing scalping, fraud, and chargebacks. This approach ensures fair access, transparent revenue sharing, and verifiable ticket authenticity in a solo-buildable, open-source MVP.
Describe what your prototype or MVP will demonstrate, and where it can be accessed.
The MVP will demonstrate on-chain minting of verifiable tickets with enforced resale caps and organizer royalties, refundable anti-bot deposits, and high-throughput sales via a Hydra head. It includes an organizer dashboard to create events, a buyer web app for queueing and purchasing tickets, and a verifier PWA for venue check-in with dynamic scan codes. The prototype will be deployed on Cardano testnet with a public demo URL and open GitHub repos for code and deployment instructions, enabling community review and integration testing.
Describe realistic measures of success, ideally with on-chain metrics.
Number of on-chain ticket mint transactions per event, demonstrating audience reach.
Percentage of tickets sold to unique wallet addresses, showing fair distribution.
Volume and frequency of controlled resale transactions with royalties correctly captured.
Number and ratio of refundable anti-bot deposits committed versus finalized purchases.
Throughput rates during ticket drops and venue scans using Hydra, measured in transactions per second.
User engagement with verifier PWA scans, reflecting real-time entry processing.
[Your Project and Solution] Solution
Please describe your proposed solution and how it addresses the problem
Solution: How FairMint Tickets solves Web2 ticketing pain
Problem to solve
Web2 ticketing suffers from three persistent issues:
- Scalping and bot abuse that hoard primary sales and inflate resale prices.
- Counterfeit/duplicate tickets and poor provenance checks at venues.
- Chargeback/friendly-fraud disputes that drain organizer revenue and time.
FairMint Tickets: solution overview
FairMint Tickets is a Cardano-based ticketing system that mints each ticket as a verifiable on-chain asset and enforces fair-market rules with smart contracts, while using a high-throughput flow for peak moments. It directly targets scalping, counterfeits, and chargebacks.
Core components and how they address the problems
- Programmable ticket minting (authenticity and provenance)
- Each ticket is minted as a unique on-chain asset (native token/NFT) with an immutable policy ID.
- Benefits:
- Verifiable authenticity and provenance eliminate easy duplication.
- Organizers can set per-event rules in code, not in opaque T&Cs.
- Smart-contract enforcement of fairness (anti-scalping and fair resale)
- Transfer logic encodes:
- Per-wallet purchase limits and enforced delay windows before transfers are allowed.
- Capped resale pricing bands to reduce arbitrage margins.
- Organizer royalties on secondary sales for transparent revenue participation.
- Benefits:
- Reduces bot capture by limiting bulk hoarding.
- Makes price-gouging far less profitable.
- Returns a share of secondary-market value to organizers.
- Anti-bot purchase flow (commit-and-deposit)
- Buyers place a purchase commitment with a small refundable deposit.
- Only successful completions get the deposit back; abandoned/abusive flows forfeit deposits or face cool-downs.
- Benefits:
- Adds cost to mass automation and scripted hoarding.
- Encourages legitimate buyers while preserving UX with quick refunds.
- High-throughput handling for drops and entry (burst capacity)
- Peak phases (sale drops, gate scans) run through a fast path that batches and periodically anchors to L1 for auditability.
- Benefits:
- Smooth buyer experience during high demand.
- Reliable venue check-ins with dynamic QR/NFC codes tied to on-chain ownership.
- Chargeback-light settlement and on-chain receipts
- Purchases use ADA or a supported stable asset; every sale/transfer produces an immutable on-chain receipt.
- If fiat rails are added later via a third party, on-chain receipts provide strong, timestamped evidence to contest chargebacks.
- Benefits:
- Reduces exposure to chargeback abuse.
- Simplifies reconciliation and dispute handling.
- Controlled secondary market with transparent rules
- Built-in marketplace flow respects caps, time windows, and royalties.
- Organizers can toggle transfers (e.g., disable transfers after entry, or allow only within a period).
- Benefits:
- Eliminates “mystery markups” and fake listings.
- Lets legitimate fans resell within fair parameters.
- Verifier PWA and dynamic redemption
- Venue staff use a lightweight scanner app that:
- Validates current ownership and redemption status.
- Issues time-bound dynamic codes to prevent screenshots/reuse.
- Marks tickets redeemed on-chain or via batched updates.
- Benefits:
- Prevents double-entry attempts.
- Works with minimal hardware and training.
User flows
- Organizer
- Create event, supply, price, and rule presets (limits, caps, royalty rate).
- Publish sale schedule and optional presale allowlists.
- Monitor live metrics: unique buyers, bot-block ratio, royalty capture.
- Buyer
- Wait in a fair queue, commit purchase with small refundable deposit.
- Pay in ADA/stable; receive verifiable ticket into wallet.
- If needed, resell within capped band; royalties distribute automatically.
- Venue/Verifier
- Scan attendee’s dynamic code; verify ownership and status.
- Approve entry and mark redeemed; handle offline fallback with periodic sync.
Why this works better than Web2
- Rules in code, not promises in fine print: resale caps, royalties, timing, and limits are enforced by the protocol.
- Built-in provenance and redemption state make counterfeits and duplicate scans much harder to pull off.
- Chargeback exposure is reduced by native settlement and irrefutable on-chain receipts.
- Peak-time reliability is designed into architecture, not left to ad-hoc rate limits.
MVP scope (5–6 months)
- Contracts: ticket minting policy, commit/deposit purchase flow, controlled resale with royalty, redemption status.
- Apps: organizer dashboard, buyer web app, verifier PWA with dynamic codes.
- Throughput: a single high-speed path for sales and scans with periodic L1 anchoring.
- Pilot: 1–2 events (300–1,000 tickets), ADA or one stable asset.
Measurable success (on-chain and product KPIs)
- Ticket mint tx count per event; % sold to unique wallets.
- Resale tx count with royalties distributed; total royalties captured.
- Commit/deposit vs. completed purchase ratio (bot-block proxy).
- Duplicate/invalid scan attempts vs. successful redemptions.
- Peak sale/scan throughput and time-to-finality for buyers and venue.
Sustainability and growth
- Monetize via small primary sale fee, a cut of organizer royalties on secondary sales, and SaaS for organizers (advanced presets, analytics, support).
- Open-source core (contracts, verifier, SDKs) to build trust and foster integrations; revenue comes from hosting, operational excellence, and premium features.
[Your Project and Solution] Impact
Please define the positive impact your project will have on the wider Cardano community
Drives real on-chain activity and adoption
- Every event mints, transfers, royalty payouts, and redemption anchors generate measurable transactions, attracting new users and wallets.
Open-source building blocks for others
- Reusable smart contracts (minting, royalties, commit/deposit, redemption) and SDKs accelerate other Cardano ticketing, membership, and access-control apps.
Showcases Cardano strengths in practice
- Demonstrates smart-contract enforceable fairness and Hydra-style throughput, serving as a public case study for real-world utility.
Onboards venues, artists, and fans
- Easy UX (email/OTP + wallets) introduces mainstream users to Cardano through a familiar activity: events and tickets.
Strengthens ecosystem trust and security culture
- Transparent rules in code and public audits set a standard for fair markets and reduce fraud—benefits transferrable to other dApps.
Stimulates complementary services
- Creates demand for identity, analytics, marketing, and payments integrations, encouraging partner projects and cross-project collaboration.
Regional and grassroots empowerment
- Small venues and community events gain access to programmable, low-fee ticketing, broadening geographic and socioeconomic participation in Cardano.
[Your Project and Solution] Capabilities & 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?
Delivery capability, trust, and feasibility validation
Track record and execution plan
- Prior Cardano dApp experience
- Solo-buildable scope with milestone gating
- Tight MVP scope (contracts + app + single L2 template) and a 5–6 month plan with concrete deliverables, demos, and public artifacts at each stage.
- Open development and auditability
- Public repositories from day one, semantic versioning, CI, test coverage reports, and reproducible deployments (scripts and policy IDs).
- Security policy for responsible disclosure; changelogs and signed releases for traceability.
Accountability mechanisms
- Milestone-based deliverables
- Transparent, on-chain proof of work
- Publish policy IDs, testnet/mainnet transaction hashes, and anchor schedules so anyone can verify progress and functionality.
- Community validation
- Open demo environments, weekly progress notes, and issue triage; invite community reviewers to test purchase, transfer, and redemption flows.
Feasibility validation plan
- Technical feasibility
- Prototype contract logic on testnet with unit tests (property-based where applicable) and scenario scripts for edge cases (double-spend attempts, duplicate scans, out-of-band transfers).
- Load testing for burst sales and entry scans in a controlled environment; document throughput, latency, and fallback behaviors.
- Security and correctness
- Structured test matrix covering minting, ownership, transfers, royalties, deposits, and redemption state transitions.
- Community code review bounty and a lightweight external security pass focused on critical state transitions and policy constraints.
- Usability validation
- Pilot with 1–2 real events (300–1,000 tickets) to measure flows: queue→commit→purchase completion rate, scan success, and helpdesk load.
- Collect organizer/staff feedback on dashboard and verifier PWA to refine UX.
- Measurable success metrics
- On-chain: mint/transfer/royalty/anchor counts; % unique wallets; resale compliance rate; commit vs. finalize ratio (bot deterrence proxy).
- Operational: peak TPS during drops/scans; average purchase time; scan latency and duplicate-attempt rejection rate.
- Risk mitigation and fallbacks
- Offline-tolerant verifier with queued updates; daily anchors if live anchoring is interrupted.
- Parameterized rules (caps, windows, limits) to adapt to venue/legal requirements without contract redeploys where possible.
Governance, transparency, and reporting
- Public roadmap and issues
- Clear backlog and milestone boards; community-visible blockers and resolutions.
- Regular progress reporting
- Biweekly updates with links to commits, deployed artifacts, and screenshots/videos of working features.
- Post-pilot report
- Publish a comprehensive report with metrics, lessons learned, and next-steps plan to move from MVP to open beta and revenue.
[Milestones] Project Milestones
Milestone Title
Architecture, Specs, and Contract Prototypes
Milestone Outputs
Finalized specs: ticket minting, transfer rules, royalties, commit/deposit, redemption.
Contract prototypes on testnet with unit/property tests and deployment scripts.
Public repositories with CI set up and initial docs.
Acceptance Criteria
All core flows have been clearly specified and thoroughly reviewed. Smart contracts compile successfully, deploy to the testnet, and pass baseline tests. A continuous integration pipeline automatically runs tests on each push, blocking any failing builds to ensure reliability and code quality.
Evidence of Completion
These would be made available:
Public spec docs, repo links, testnet policy IDs/tx hashes, CI badges/screens.
Delivery Month
1
Cost
10000
Progress
20 %
Milestone Title
Organizer Dashboard + Buyer Purchase
Milestone Outputs
Organizer app: create event, set supply/pricing, rule presets, royalties.
Buyer app: queue, refundable deposit commit, on-chain purchase, ticket receipt.
End-to-end testnet demo including wallet connection.
Acceptance Criteria
Event creation and sale configuration can be accessed and should be able to persist correctly.
Successful purchase yields ticket in buyer wallet on testnet.
Refundable deposit returns for completed purchases.
Evidence of Completion
These would be made available:
Testnet tx hashes (mints, deposits, refunds), screencast of end-to-end flow, public demo URL.
Delivery Month
2
Cost
12000
Progress
40 %
Milestone Title
Verifier PWA and Redemption Logic
Milestone Outputs
Build a Verifier PWA: scan dynamic code, validate ownership, mark redeemed.
Redemption state transitions on-chain; duplicate-prevention checks.
Offline-tolerant scanning with queued updates and sync.
Acceptance Criteria
All Valid tickets should have the ability to be redeemed only once; while all duplicates should be inevitably rejected. This is a measure to build trust in the system.
Verifier works in low connectivity and syncs state correctly.
Evidence of Completion
These would be made available:
Testnet redemption tx hashes, verifier demo video, test logs showing duplicate rejection.
Delivery Month
3
Cost
8000
Progress
50 %
Milestone Title
High-Throughput Burst Path + Periodic Anchoring
Milestone Outputs
High-throughput path integrated for sale spikes and venue scans.
Periodic L1 anchoring job (e.g., daily) for auditability.
Load/latency tests with documented peak throughput and fallback behavior.
Acceptance Criteria
Demonstrated stable performance under simulated spikes, with anchors which consistently without fail produced on schedule and backed by verifiable references, ensuring reliability.
The application should not only be fast but stable.
Evidence of Completion
These would be made available:
Load test report, anchor tx hashes, monitoring dashboard screenshots.
Delivery Month
4
Cost
8000
Progress
70 %
Milestone Title
Controlled Resale v1 + Security Pass
Milestone Outputs
Capped resale price band and organizer royalty distribution live on testnet.
Security hardening: test matrix, community review bounty, fixes applied.
Metrics instrumentation for on-chain and app KPIs.
Acceptance Criteria
Resale within allowed band succeeds; out-of-band fails with clear errors.
All Royalties disburse automatically to organizer wallet.
Security issues from review addressed with documented patches.
Evidence of Completion
These would be made available:
Testnet resale and royalty tx hashes, test matrix report, security review summary and changelog.
Delivery Month
5
Cost
8000
Progress
80 %
Milestone Title
Mainnet Deployment + Pilot Event + Post-Pilot Report
Milestone Outputs
Mainnet deployment of contracts and apps; published addresses/policies.
Pilot event (300–700 tickets): sales, check-ins, controlled resales.
Post-pilot public report with KPIs and lessons; readiness for open beta
Acceptance Criteria
Achieved successful mainnet ticket sales, verifications, and at least one compliant resale.
Captured KPIs included mints, transfers, royalties, unique wallet counts, bot-block ratio, and scan throughput metrics for detailed performance insights.
Evidence of Completion
These would be made available:
Mainnet tx hashes (mints, resales, royalties, anchors), pilot dashboard screenshots, published report.
Delivery Month
6
Cost
6000
Progress
100 %
[Final Pitch] Budget & Costs
Please provide a cost breakdown of the proposed work and resources
Summary by category
- Engineering & Architecture: ₳28,000
- High‑Throughput Integration & Infrastructure: ₳7,000
- Security Review & Testing: ₳6,000
- UI/UX & Documentation: ₳4,000
- Pilot Operations & Support: ₳4,000
- Contingency (approx. 6%): ₳3,000
Total: ₳52,000
Detailed breakdown
- Engineering & Architecture — ₳28,000
- Smart contracts: ticket minting policy, transfer rules, royalties, commit‑and‑refund deposits, redemption logic — ₳12,000
- Backend services: API, indexing, wallet/payment integration, batching/anchors orchestration — ₳7,000
- Frontend apps: organizer dashboard, buyer purchase flow (queue → commit → purchase), verifier PWA with dynamic codes — ₳7,000
- DevOps: CI/CD, test environments, scripts, deployment automation — ₳2,000
- High‑Throughput Integration & Infrastructure — ₳7,000
- High‑throughput burst path integration and daily anchoring job — ₳4,000
- Hosting/infra: nodes, app hosting, monitoring/logging for MVP and pilot — ₳3,000
- Security Review & Testing — ₳6,000
- Independent contract/security reviewer (part‑time, focused pass) — ₳4,000
- Community review bounty and test coverage expansion (unit/property tests, scenario tests) — ₳2,000
- UI/UX & Documentation — ₳4,000
- Core flow design: queue/commit UX, purchase, resale, verifier scan UX — ₳2,500
- Documentation: open repos, readmes, integration guides, runbooks — ₳1,500
- Pilot Operations & Support — ₳4,000
- Venue onboarding, test runs, staff training materials — ₳1,500
- Pilot event support (300–700 tickets), incident response, post‑mortem — ₳2,000
- Miscellaneous ops (domains, email/OTP provider, small tools) — ₳500
- Contingency — ₳3,000
- Buffer for unexpected infra costs, fixes from security review, or minor feature adjustments required by the pilot.
[Final Pitch] Value for Money
How does the cost of the project represent value for the Cardano ecosystem?
The ₳52,000 budget converts directly into reusable, open-source building blocks, measurable on-chain activity, and real-world adoption:
Reusable primitives for others
- Open contracts (minting, royalties, transfer caps, deposits, redemption) and SDKs become plug-and-play components for ticketing, memberships, access passes, and token-gated apps across Cardano.
Net-new users and transactions
- Each event drives mints, transfers, royalties, and redemption anchors, onboarding venues, artists, and fans while increasing wallets and transaction volume.
Demonstration of Cardano’s strengths
- A public, production-grade case study for smart-contract enforced fairness and high-throughput event flows, improving Cardano’s credibility with non-crypto stakeholders.
Lower ecosystem risk via transparency
- Open repos, test matrices, and audits raise the bar for security and correctness, benefiting future builders.
Catalytic external integrations
- Creates demand for partner services (identity, analytics, stable payments), strengthening cross-project collaboration and network effects.
Sustainable path to continued utility
- A self-sustaining SaaS/fee model ensures the product persists beyond the grant, maintaining infrastructure that keeps generating Cardano activity and visibility.
[Required Acknowledgements] Consent & Confirmation
Terms and Conditions:
Yes