AdaRide - pay and earn through taxi rides

[Proposal setup] Proposal title

Please provide your proposal title

AdaRide - pay and earn through taxi rides

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

85000

[Proposal Summary] Time

Please specify how many months you expect your project to last

8

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

Most taxi rides in Iraq are cash-only. Drivers face slow payouts and high fees; riders have no reason to try crypto. Cardano lacks a visible, daily use case in transport.

[Proposal Summary] Project Dependencies

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

Yes

Describe any dependencies or write 'No dependencies'

Summary: We minimize external dependencies and de-risk each with backups. Our only hard requirements are (a) cooperating taxi fleets/aggregators, (b) Cardano mainnet access, and (c) basic mobile data. Everything else is swappable or has an offline fallback. 1) Fleet & Driver Access Primary dependency: MoUs with two Baghdad/Erbil fleets or aggregators granting access to 150 drivers in months 1–6 and permission to place stickers/QRs and run rider promotions. Mitigation: We maintain a replacement pipeline (additional fleets + independent drivers). Kits are re-assignable within 48 hours if a partner exits. No single fleet controls >60% of pilot drivers. 2) Wallet & Payment Standards Standard, not vendor lock-in: Rider payments use Cardano URI / CIP-30 and standard QR. We support major wallets; no proprietary SDK required. Mitigation: If any wallet is temporarily unavailable, riders can use an alternative wallet or a hosted QR page that renders the same transaction for any wallet that supports CIP-30. 3) Network & Connectivity (with Wi-Fi option in every taxi) Dependency: Mobile data to submit transactions and display confirmations. Design for the street: Driver smartphone data is primary. MiFi hotspot (portable Wi-Fi) per taxi is recommended for campaign drivers; we budget for prepaid data top-ups common in Iraq and use dual-SIM devices when possible. Offline ride codes: If coverage drops, the app issues a signed ride code; once connectivity returns, the payment/loyalty is reconciled on-chain. Receipts & proof: Digital receipts include explorer links; dispatchers can verify in a web console. Mitigation: We pre-test fleet routes for weak areas, keep spare MiFi units, and stock top-up vouchers so drivers can reload data immediately. 4) Hosting & Services Dependency: Cloud hosting for the dispatcher console, public metrics dashboard, and monitoring. Mitigation: Multi-region deployment; nightly backups; infrastructure as code. If a provider outage occurs, the driver app continues in offline mode and syncs later. 5) Stablecoin/ADA Choice Primary path: Accept ADA everywhere; support Cardano-native stablecoins where practical. Mitigation: UX always displays IQD fare totals; loyalty discounts buffer small volatility. No bridges or custodial conversions are required for core operation. 6) Devices Assumption: Drivers already use Android phones. For those without reliable hardware, we issue a low-cost Android unit (limited to our app) and, when needed, a MiFi hotspot. Mitigation: Fast swap pool for failed devices; remote lock/erase; serial numbers logged. 7) Compliance, Permissions, and IP Branding: Permission from fleets to place interior/exterior stickers, QR cards, and a short “how to pay” guide. Data: We store no seed phrases and no unnecessary personal data. Transaction evidence is on-chain; operational data is aggregate and anonymized. Financial: The platform is non-custodial; drivers receive on-chain payments directly to their wallets. 8) People & Training Dependency: Driver participation in short micro-trainings (10–15 minutes) and acceptance of SOPs (refund path, “paid” indicator, how to explain discounts). Mitigation: Simple Arabic/Kurdish quick cards; refresher videos; incentives tied to correct usage. 9) Marketing & Incentives Dependency: Space in cars for cards/stickers and permission to run city campaigns (“Pay with ADA and save 5–10%”). Mitigation: All materials are pre-approved in MoUs; we can convert to driver-only incentives if a fleet pauses public promos. 10) Risks & Backups (concise) Connectivity: Dual-SIM phones + MiFi hotspots + offline codes + receipts; budgeted Wi-Fi top-ups. Driver churn: Reassignment SOP; incentives front-loaded to keep 150 active drivers. Operational error/fraud: Explorer-linked receipts, refund path, device PIN/remote wipe, anomaly alerts. Scope risk: If a fleet withdraws, equipment and drivers are reallocated; milestones are tied to on-chain KPIs so funding pauses automatically if targets are not met. Bottom line: Our dependencies are practical and locally available (drivers, prepaid data/MiFi, standard wallets). Each has a defined fallback so the 8-month, 85k ADA pilot can succeed without single-vendor lock-in.

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

No

License and Additional Information

Not fully open source during the pilot. For security and fleet privacy, the driver app & dispatcher console remain closed while we harden anti-fraud. We will open-source: loyalty policies + SDK (MIT), and a Replication Playbook with signage/SOPs and aggregate datasets (CC BY 4.0). Releases go to public repos and are linked on the dashboard at close-out; we’ll reassess opening more modules post-pilot.

[Theme Selection] Theme

Please choose the most relevant theme and tag related to the outcomes of your proposal.

Financial Services

[Campaign Category] Category Questions

Describe what makes your idea innovative compared to what has been previously funded (whether by you or others).

We bring Cardano into taxis—high-frequency, city-wide payments—via a lean QR checkout with on-chain loyalty that mints a reward each ride. Unlike awareness-only campaigns, this is coached, Arabic/Kurdish (RTL), and connectivity-aware: MiFi hotspots, prepaid data top-ups, and offline ride codes that reconcile later. It’s non-custodial, fully auditable with explorer links, and we’ll publish open loyalty policies, a light SDK, and a replication playbook so any fleet can copy it.

Describe what your prototype or MVP will demonstrate, and where it can be accessed.

A working taxi payment + loyalty loop: driver enters IQD fare → CIP-30 QR → rider pays ADA/stablecoin → receipt with explorer link → automatic stamp; refund path + offline code. Dispatcher console shows rides. Deployed with 50 drivers in Baghdad/Erbil. A public alpha dashboard displays live counters and CSVs; policy IDs and a demo video are published. Open repos host loyalty policies + SDK and setup instructions so anyone can inspect or replicate.

Describe realistic measures of success, ideally with on-chain metrics.

Public, on-chain KPIs: ≥12,000 paid rides, ≥3,000 unique rider wallets, ≥800 redemptions. Quality: success ≥95%, median checkout ≤60s, refund <1%, fraud/loss <0.5%. Operational: 150 trained active drivers; ≥2 fleets onboard; MiFi/top-up logs. Evidence: dashboard URL + CSV exports with explorer links, QA “mystery-rider” reports, and monthly field notes. Milestone-gated funding pauses if KPIs or acceptance tests are missed.

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

What we’re solving

In Iraq, most taxi rides are paid in cash. Drivers wait for payouts and absorb high commission; riders have no reason to try crypto; Cardano has little visibility in daily transport. We will change that by making a normal ride the easiest way to pay with ADA or a Cardano-native stablecoin and earn a reward—with public, on-chain evidence that the habit is taking hold.

Our approach in one line

A lean, Arabic/Kurdish/English QR checkout + on-chain loyalty that works in the real conditions of Iraqi taxis, proves adoption with explorer links, and leaves behind open building blocks others can reuse.

What we are building:

1. Driver app & dispatcher console (pilot-closed for security)

• Checkout: Driver enters the IQD fare; the app renders a CIP-30 compatible payment request and QR. Rider scans with any major Cardano wallet and approves.
• Receipts & refunds: Driver sees instant confirmation; a digital receipt includes the tx hash/explorer link. A simple refund path is available for mistakes.
• Payouts: Non-custodial; funds land directly in the driver’s wallet.
• Console: Fleet managers see status (rides, success rate, data usage), manage drivers, and export aggregate logs.

1. On-chain loyalty (open source)

• Every successful payment mints a visible reward to the rider’s wallet—NFT stamp or points under an open policy. After N rides, a redemption script applies a fare discount.
• Policies, rules, and reference code are open-sourced so others can copy the model.

1. Public metrics dashboard (transparent by default)

• Live counters for on-chain rides, unique rider wallets, loyalty redemptions, checkout time/success, and refund rate. CSV downloads and explorer links allow the community to audit our claims.

1. Fleet kit & training

• Seat-back and window stickers, “how to pay” cards, Arabic/Kurdish cashier quick guides, and ten-minute micro-trainings. Drivers are certified before solo use.

Built for Iraqi streets (connectivity first):

• Connectivity is the biggest real-world constraint, so we design for it:
• Primary: driver smartphone data.
• Wi-Fi in taxis: for campaign drivers we issue a portable MiFi hotspot per car and budget prepaid top-ups (widely available in Iraq).
• Dual-SIM devices where possible; we keep spare MiFi units.
• Offline ride codes: when coverage drops, the app issues a signed code; the payment and loyalty reward reconcile to chain once online.
• Clear “paid” indicator and digital receipts prevent disputes even when the car is moving through weak zones.

The user journey

1. Rider enters a taxi and sees “Pay with Cardano & Save” signage.
2. Driver inputs the fare; the app shows IQD total and an ADA/stablecoin amount with QR.
3. Rider scans, approves, and receives a receipt and a stamp in their wallet.
4. After N rides, the redemption script validates and applies a discount—fast, no forms, no PII.
5. The dashboard increments the counters; reviewers can click the tx on the explorer.

Why this design?

• Habit over hype: taxis are high-frequency and city-wide—perfect for turning a first transaction into a repeating behavior.
• Trust: drivers explain, signage reminds, and loyalty rewards the choice each time.
• Evidence: we publish verifiable, on-chain outcomes instead of marketing claims.
• Reuse: open policies, SDK, and a Replication Playbook (AR/KU/EN) make it easy to extend to ride-hailing fleets, delivery couriers, or inter-city shuttles.

Who we engage:

• Taxi fleets/aggregators in Baghdad and Erbil (MoUs for access to drivers and in-car branding).
• Drivers (training, fast payouts, small onboarding incentives).
• Riders/families (fare discounts when paying with ADA or a Cardano stablecoin; simple how-to cards).
• The Cardano community (public data, open code, reusable playbook).

How we will demonstrate impact:

• We tie each disbursement to acceptance tests backed by explorer-verifiable data:
• On-chain rides: cumulative counts with transaction links.
• Unique wallets: distinct rider addresses interacting with our policies.
• Loyalty redemptions: proof of benefits used, not just issued.
• Quality metrics: median checkout time, success %, refund %, and fraud/loss <1%.
• Operational proof: MoUs, training logs, photos of kits in cars, QA “mystery rider” reports.
• Public dashboard: live and downloadable so anyone can audit.
• Targets (listed in Milestones) are conservative for an 8-month, 85k ADA pilot and include 150 drivers, ≥12,000 rides, ≥3,000 unique wallets, ≥800 redemptions, success ≥95%, median ≤60s.

What’s unique:

• First on-chain taxi loyalty in Iraq with Arabic/Kurdish UX, built for moving vehicles and patchy data.
• Connectivity-aware by design (MiFi per car + prepaid top-ups + offline codes).
• Non-custodial + privacy-respecting: no seed phrases or unnecessary personal data stored; receipts and proofs are on-chain.
• Open assets: loyalty policies + rider/driver integration SDK under MIT; Replication Playbook, signage, SOPs, and aggregate datasets under CC BY 4.0.
• Operational discipline: driver certification, device management, anomaly alerts, and milestone-gated funding.

Delivery plan (high level)

Phase 1 — MVP (Months 1–2)

• Ship driver app + console with QR checkout, receipts, and loyalty minting; publish policy IDs; run security review; onboard first 50 drivers; test MiFi/top-ups on routes; launch alpha dashboard.

Phase 2 — City Pilot (Months 3–6)

• Scale to 150 drivers across two fleets; run “Pay with Cardano & Save” campaigns; certify drivers; hold weekly QA rides; hit adoption and quality targets; publish monthly reports and datasets.

Phase 3 — Stabilize & Publish (Months 7–8)

• Reach cumulative KPI targets; publish Replication Playbook and open repo (policies + SDK + examples); short close-out video; present a pipeline of 500+ additional drivers for post-grant scale.

Governance & risk management

• Milestone-gated disbursements; work halts if acceptance tests fail.
• Dual-sig project account; vendor payments only against verified deliverables.
• Device & data security: remote lock/wipe, serial logs, least-privilege access, no private keys.
• Fraud & error controls: explorer-linked receipts, explicit refund flow, anomaly monitoring.
• Continuity: hardware is reusable; drivers can be re-assigned; if a fleet exits, we redeploy to back-ups from our pipeline.

Why this matters to Cardano

Transport touches millions of daily decisions. By putting Cardano checkout + loyalty in taxis, we create a visible, repeatable entry point for non-crypto users and back it with public, verifiable metrics. The ecosystem gains (1) real transactions and new wallets, (2) open, localized building blocks for other teams, and (3) an evidence-based story the community can trust.

Bottom line: we turn a routine taxi ride into a weekly Cardano habit—scan, pay, earn—and document exactly how to replicate it in the next city.

[Your Project and Solution] Impact

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

Cardano becomes part of a normal taxi ride. Riders pay with ADA or a Cardano-native stablecoin, earn an on-chain reward, and do it again next week. Drivers receive fast, transparent payouts. Adoption is verifiable, not anecdotal.

Quantifiable outcomes (public & on-chain):

We will publish a live dashboard with explorer links and downloadable CSVs. Acceptance metrics (cumulative across Baghdad→Erbil):

• ≥12,000 on-chain rides paid in ADA/stablecoins.
• ≥3,000 unique rider wallets (first on-chain tx via taxis).
• ≥800 loyalty redemptions proving repeat use and real value.
• ≥150 drivers trained, certified, and active.
• Quality: median checkout ≤60s; success ≥95%; refund <1%; fraud/loss <0.5%.
• Payouts: non-custodial settlement to drivers’ wallets; median confirmation <5 min (dashboard shows latency).

These counters make the impact auditable by anyone at any time.

Value to the Cardano community

Visible, repeatable usage

A high-frequency, city-scale payment flow demonstrates that Cardano can power everyday transactions—even with patchy connectivity.

Open, reusable assets

We will open-source loyalty policies and a lightweight rider/driver SDK (MIT), and publish a Replication Playbook (AR/KU/EN, CC BY 4.0) with signage, SOPs, device/Wi-Fi tips, and training modules. Teams in other cities can copy/paste the model quickly.

Localized onboarding at the edge

Arabic/Kurdish UX, portable Wi-Fi (MiFi) + prepaid top-ups per taxi, and offline ride codes reduce friction for non-crypto families, expanding access beyond typical tech hubs.

Evidence for researchers & builders

Aggregate, privacy-safe datasets (rides, unique wallets, redemption rates, success/latency) enable wallets, analytics teams, and academics to study adoption and optimize UX.

Merchant & ecosystem pull

Fleets, delivery couriers, and shuttle operators can adopt the same rails; cafés and shops along taxi routes gain Cardano-ready customers primed by loyalty rewards.

How we will measure and share:

• Public dashboard: live counters; per-metric definitions; CSV export; API endpoints for community tools.
• Monthly field notes: short, honest updates (what reduced friction, what didn’t), photos of in-car kits, QA “mystery rider” summaries.
• Open repositories: policy scripts, SDK, examples, and the Playbook; each tagged to milestones.
• Community sessions: webinars in AR/KU/EN for fleets and local devs; bounties for wallet UX improvements and analytics contributions.
• Cardano-friendly map: opt-in listing of active taxis/fleets and campaign areas.

Inclusion, safety, and privacy:

• No seed phrases or unnecessary PII ever stored.
• Receipts include explorer links; drivers have an explicit refund path.
• Driver training emphasizes safe explanations, clear “paid” indicators, and respectful support for first-time users.
• Materials are accessible, right-to-left, and readable at a glance.

Post-grant momentum

• The pilot leaves behind trained drivers, a working dashboard, open assets, and a sustainable path (light platform fee per on-chain fare + optional fleet dashboard subscription).
• With a proven playbook and a pipeline of 500+ drivers, community teams can scale to new districts/cities using the same code, signage, and Wi-Fi practices.
• As loyalty takes hold, incentives taper and Cardano use continues organically.

Why this impact matters:

The community needs adoption that can be seen, counted, and repeated. Taxis provide thousands of small, authentic payment moments every week. By turning those rides into scan → pay → earn habits—and by publishing open code and datasets—we grow transactions, wallets, and credibility for Cardano in Iraq and create a portable blueprint other teams can run with the next day.

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

Why we can deliver:

We are Iraqi builders with deep roots in the transport/auto ecosystem and the technical depth to ship secure, field-ready Cardano software. Our team combines:

• Local relationships & reach. We are well connected with garages, car-service shops, tire/oil chains, and parts markets in Baghdad and Erbil—the same places taxi drivers visit weekly. These partners act as recruitment hubs and support points (flyers, sign-ups, SIM/Wi-Fi top-ups, device swaps). We also maintain links to taxi fleets/aggregators and independent driver groups willing to run the pilot under simple MoUs.
• Engineering capacity. Senior Android and backend engineers with production experience in Arabic/Kurdish apps, plus Cardano developers comfortable with CIP-30 wallets, policy scripts/NFTs, redemption logic, logging, and monitoring.
• Field operations. Staff who have deployed POS/payment flows in noisy, high-throughput environments; we write cashier/driver scripts, run micro-trainings, and manage device fleets (enrollment, remote lock/wipe).
• Bilingual content. All materials (AR/KU/EN) use right-to-left layouts and large, glanceable visuals to reduce mistakes.

What we will deliver (and how)

1. Software & infrastructure (owned by our team)

• Driver app (pilot-closed): fare entry in IQD; CIP-30 QR/URI; success state, refund path, and receipt with explorer link; offline ride codes that reconcile to chain later.
• Dispatcher console: non-custodial status board; driver management; CSV export; anomaly alerts.
• On-chain loyalty (open): MIT-licensed policies for stamps/points with a redemption script; reference SDK and examples.
• Public dashboard: live counters (on-chain rides, unique wallets, redemptions), success/latency, refund rate; CSV/API for community analysis.
• Security & device ops: signed releases; least-privilege backend; telemetry without PII; device enrollment, PIN, and remote lock/wipe

1. Hardware, connectivity, and materials

• Connectivity kit: we budget portable MiFi hotspots for campaign drivers, dual-SIM where possible, and prepaid data top-ups (widely available in Iraq).
• In-car kit: window/seat-back stickers, QR cards, and “How to pay with Cardano” cards; all with AR/KU/EN text.
• Training assets: 10–15-minute micro-modules, laminated quick guides, and short videos. Drivers are certified before solo operation.

1. Recruitment & support

• Driver funnel: garages/service shops distribute QR sign-ups and vouchers; fleets/aggregators supply initial cohorts.
• Support points: our garage partners serve as local counters for device swaps and Wi-Fi/data top-ups; hotline + WhatsApp group for drivers.
• QA program: weekly “mystery rider” tests capture real friction; we publish short field notes and apply hotfixes.

Risk management (with concrete mitigations):

• Connectivity gaps: portable MiFi per car, dual-SIM where possible, prepaid top-up vouchers distributed via garage counters; offline ride codes with later reconciliation; printed/digital receipts; clear “PAID” indicator.
• Driver churn: onboarding incentives are front-loaded; quick re-training; device/account re-assignment SOP (under 24 hours); backup driver pool from garages.
• Fleet withdrawal: kits are redeployed to alternate fleets or independent drivers; no single fleet holds >60% of active drivers.
• Operational error/fraud: explorer-linked receipts, explicit refund path, device PIN/remote wipe, serial logs, and anomaly alerts (e.g., repeated cancels).
• Volatility: fares always shown in IQD; support Cardano-native stablecoins where available; loyalty discounts buffer small swings.
• UX friction: AR/KU/EN UI; right-to-left layouts; large targets; one-scan flow; weekly QA tests feed fast UI tweaks.
• Data protection: no seed phrases; no unnecessary PII; only aggregate data published; GDPR-style deletion on support requests.

Trust & accountability in fund management:

• Milestone-gated disbursements. Funds move only when acceptance tests are met and artifacts are published.
• Dual-signature treasury. A dedicated project wallet with two signers; spend approvals logged.
• Procurement discipline. At least two quotes for devices/printing/hosting where practical; commodity Android and MiFi hardware to avoid lock-in.
• Independent reconciliation. Monthly ledger matching invoices/receipts to deliverables; device serial logs; budget vs. actuals shared with Catalyst on request.
• Transparency. Public dashboard, monthly progress notes (what worked/what didn’t), and open repositories (policies/SDK/playbook) linked in updates.
• Conflict-of-interest policy. Any related-party expense disclosed and pre-approved; if an equal-quality third-party option is cheaper, we use it.

Why this plan is feasible

• Known environment: we already operate inside the exact garages and shops taxi drivers use, giving us recruitment and support reach that pure software teams lack.
• Proven patterns: the product reuses flows we have shipped before—QR checkout, Arabic/Kurdish UI, offline-first sync, and device management—adapted for moving vehicles.
• Tight scope + open outputs: a clear, verifiable pilot with conservative KPIs and open artifacts that the community can reuse the next day.

Bottom line: We have the relationships to reach drivers at scale, the engineering to ship secure, offline-aware Cardano payments and loyalty, and the controls to manage funds responsibly. With milestone gating and public evidence, the feasibility of this project is high—and auditable by the community throughout the 8-month delivery.

[Milestones] Project Milestones

Milestone Title

MVP Live + First 50 Drivers Onboarded

Milestone Outputs

• Driver app (MVP): IQD fare → CIP-30 QR; success & refund flow; receipt w/ explorer link.

• Dispatcher console (alpha); logging & anomaly alerts.

• On-chain loyalty policies live; stamp/points mint on payment.

• Connectivity kit: MiFi units issued to campaign cars; prepaid Wi-Fi/data top-ups workflow; offline ride codes.

• 50 drivers trained & certified; MoUs with ≥2 fleets/aggregators.

• Public dashboard (alpha) online.

Acceptance Criteria

A rider can complete an end-to-end mainnet taxi payment in ADA/stablecoin with the MVP app and receive a loyalty stamp automatically; the driver sees a success state and a refund option. The printed/digital receipt must contain a valid explorer link to the payment. The dispatcher console shows the ride and status. The dashboard (alpha) is public and displays counters for on-chain rides, unique wallets, redemptions, success rate, and median checkout time. Connectivity features are verified: at least 10 successful payments using MiFi, 10 using dual-SIM, and 10 using offline ride codes that reconcile on-chain within 24h. ≥50 drivers are trained and active (listed with IDs), and ≥2 signed MoUs with fleets/aggregators are on file. Cumulative adoption by milestone close: ≥2,000 on-chain rides, success ≥90%, median checkout ≤70s. A brief external security review of refund and reconciliation flows is delivered.

Evidence of Completion

Public links to: (1) a short demo video of the full flow (fare→QR→pay→receipt→loyalty); (2) the policy IDs used for loyalty; (3) a timestamped dashboard URL showing rides, wallets, redemptions, success/latency; and (4) a CSV export containing at least 2,000 payment tx hashes and 2,000 loyalty mint tx hashes (deduped), each checkable on an explorer. Operational artifacts include photos of in-car kits, MiFi devices, and top-up vouchers; a log of offline ride codes with their later tx links; signed MoUs; and training rosters (≥50 drivers) with date/time and trainer signature. Attach the security review summary (PDF) covering refund path, device loss, and offline reconciliation, plus screenshots of the dispatcher console registers matching a random sample of explorer links.

Delivery Month

2

Cost

30000

Milestone Title

City Pilot: 150 Drivers, Wi-Fi Enabled, Public Campaign

Milestone Outputs

• Scale to 150 active drivers; install stickers/QR cards.

• “Pay with Cardano & Save 5–10%” campaign; driver referral rewards.

• Dashboard v1 adds latency, refund %, redemption totals.

• Weekly QA “mystery rider” tests; monthly field notes.

• Connectivity ops: dual-SIM where possible, MiFi swap pool, top-up distribution via garages.

Acceptance Criteria

By the end of the city-pilot phase we have ≥150 drivers certified and active (no single fleet >60%). The public dashboard shows cumulative ≥8,000 on-chain rides, ≥2,000 unique rider wallets, and ≥400 loyalty redemptions. Quality thresholds are met: success ≥95%, median checkout ≤60s, refund <1%, fraud/loss <0.5%. The rider campaign runs across participating fleets with visible in-car materials; at least two monthly field notes are published describing friction removed and updates shipped. Connectivity ops are proven: a MiFi swap log exists; ≥300 top-ups are issued; and at least 50 rides originate in known weak-signal zones and reconcile successfully within 24h. The dispatcher console tracks drivers and provides CSV exports matching dashboard figures. All materials are available in Arabic/Kurdish/English and are used in training refreshers.

Evidence of Completion

Provide the dashboard URL plus downloadable CSVs for payments, redemptions, and latency/success metrics (row counts matching the acceptance thresholds) with random samples verified by explorer links. Publish the two monthly field notes (blog or PDF) and the QA “mystery rider” logs showing routes, attempt outcomes, checkout times, and any refunds issued. Upload campaign photos (seat-back cards, window stickers, QR placement), training rosters proving 150 active drivers, and the MiFi/top-up records (counts per driver, swap events). Include anonymized coverage snapshots (heatmap or list of zones) demonstrating rides in weak-signal areas plus reconciliation timestamps. Attach a short management statement confirming no single fleet exceeds 60% of active drivers.

Delivery Month

6

Cost

40000

Milestone Title

Stabilize, Open Assets & Close-Out

Milestone Outputs

• Hit cumulative targets: ≥12,000 rides, ≥3,000 unique rider wallets, ≥800 redemptions.
• Publish Replication Playbook (AR/KU/EN, CC BY 4.0) incl. signage/SOPs, Wi-Fi route tips, and offline code guidance.
• Release MIT-licensed loyalty policies + reference SDK & examples.
• Final datasets; 3–5 min close-out video; pipeline of ≥500 additional drivers; sustainability model (platform fee + optional dashboard plan).

Acceptance Criteria

The public dashboard shows final cumulative metrics of ≥12,000 on-chain rides, ≥3,000 unique rider wallets, and ≥800 redemptions, with quality still at success ≥95%, median ≤60s, refund <1%, fraud/loss <0.5%. The Replication Playbook is published in Arabic/Kurdish/English under CC BY 4.0 and includes signage files, scripts, SOPs, device setup, MiFi/top-up guidance, route/coverage tips, and an implementation checklist. The open repository contains the MIT-licensed loyalty policies, redemption script, reference SDK, tests, and examples with readme and versioned releases. A short close-out video summarizes results and lessons. A written sustainability note details the platform fee and optional dashboard subscription. We present ≥2 letters/MoUs from fleets indicating interest in onboarding ≥500 additional drivers post-grant.).

Evidence of Completion

Links to: (1) the open repositories (tags/releases, MIT license, tests passing); (2) the Playbook download (AR/KU/EN) with CC BY 4.0 notice and editable signage/source files; (3) the final dashboard and frozen CSV datasets for payments, unique wallets, redemptions, and quality metrics, each row traceable to an explorer record. Provide the close-out video and a written report (results, lessons, next steps). Attach the sustainability memo (fee structure, cost assumptions) and two or more letters/MoUs from fleets or aggregators expressing post-grant expansion intent (counts, timeline). Include screenshots of the SDK examples running against test data and a checksum or commit hash for reproducibility.

Delivery Month

8

Cost

15000

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Principles:

• Spend drives on-chain rides, unique wallets, and redemptions—not capex on vehicles.
• Commodity Android/MiFi hardware, prepaid data top-ups, and Arabic/Kurdish materials.
• Milestone-gated draws (M1 ₳30k • M2 ₳40k • M3 ₳15k). Unused incentives/contingency are re-scoped to add drivers/rides or returned.

Cost breakdown by workstream:

Engineering & Product (driver app + dispatcher + device ops) — ₳24,000

• Android app: IQD→CIP-30 QR, receipt & refund flow, offline ride codes, Arabic/Kurdish UI.
• Dispatcher console: driver management, logs/alerts, CSV export.
• CI/CD, code review, telemetry (no PII), remote lock/wipe, hotfixes.

Loyalty Contracts & Public Dashboard — ₳9,000

• MIT-licensed policies (stamps/points) + redemption scripts; reference SDK & examples.
• Public metrics dashboard (rides, unique wallets, redemptions, success/latency) with CSV/API.

Driver Onboarding Incentives — ₳19,000

• Signup/first-rides bonuses tied to correct usage, certification, and weekly activity.
• Referral rewards to seed cohorts across fleets/garages.

Rider Rewards (fare discounts when paying with ADA/stablecoin) — ₳12,000

• On-chain loyalty redemptions + campaign vouchers; tapered as habit forms.

Connectivity & Devices — ₳7,000

• Portable MiFi hotspots for campaign drivers; dual-SIM where practical.
• Prepaid Wi-Fi/data top-ups distributed via garage counters.
• Cables/mounts/spares; small pool of limited-purpose Android phones for drivers lacking reliable devices.

Signage, Printing & In-car Kits — ₳4,000

• Window/seat-back stickers, QR cards, “How to Pay with Cardano” cards (AR/KU/EN), replacement stock.

Training, QA & Field Ops — ₳4,000

• Driver micro-trainings and certification, mystery-rider tests, travel between hubs, WhatsApp/helpline.

External Security Review (focused) — ₳2,000

• Review refund path, offline reconciliation, device loss, and log integrity (summary at M1; spot checks later).

Hosting, Monitoring & Backups — ₳1,000

• Multi-region cloud, alerting, nightly backups, domain/SSL.

Contingency (risk buffer, ~3.5%) — ₳3,000

• Only for validated needs (e.g., replacement hotspots, extra top-ups); any surplus re-scoped to add drivers/rides or returned.

Total: ₳85,000

Drawdown & milestone alignment:

• M1 (₳30,000) – Engineering (₳14k), Loyalty/Dashboard (₳5k), Connectivity (₳3k), Signage (₳2k), Training/QA (₳3k), Security (₳1k), Contingency (₳2k).
• M2 (₳40,000) – Engineering (₳8k), Loyalty/Dashboard (₳3k), Driver Incentives (₳14k), Rider Rewards (₳9k), Connectivity (₳2k), Training/QA (₳3k), Hosting (₳1k).
• M3 (₳15,000) – Driver Incentives (₳5k), Rider Rewards (₳3k), Engineering polish & open-sourcing (₳2k), Playbook packaging design (from Training/QA, ₳1k), Security follow-up (₳1k), Contingency/ops (₳3k).

Unit assumptions (illustrative):

• Driver incentives: avg ₳125/driver across 150 active drivers, tied to certification + verified rides.
• Rider rewards: sized to ~₳1/ride equivalent across early redemptions, tapering as usage becomes habitual.
• Connectivity: mix of MiFi devices, dual-SIM packs, and prepaid top-ups (common in Iraq) to sustain reliable QR checkout in motion.

Third-party services & procurement:

• Hardware (Android/MiFi/printing) via multi-quote procurement; serials logged; remote lock/wipe enabled.
• Hosting/monitoring via reputable cloud provider; infrastructure as code; backups verified.
• Security review by an independent auditor (fixed-scope).
• Printing by local vendors experienced with Arabic/Kurdish right-to-left layouts.

Accounting & controls:

• Dual-signature project wallet; spend only against verified deliverables.
• Monthly reconciliation: invoices/receipts matched to milestones; public summary in updates.
• Conflict-of-interest policy: any related-party purchase disclosed and used only if best-value; otherwise an equal-quality third party is chosen.

No vehicle purchases (at this stage). All costs directly enable on-chain rides, wallets, and redemptions and produce open assets (policies/SDK/playbook) the community can reuse.

[Final Pitch] Value for Money

How does the cost of the project represent value for the Cardano ecosystem?

What you fund: a lean, verifiable adoption engine—QR checkout + on-chain loyalty in taxis—plus open assets (policies/SDK/playbook) others can reuse. We do not buy vehicles. Spend is tied to explorer-verifiable KPIs and released only when acceptance tests are met.

Why the budget is efficient

• Outcomes > overhead. 85k ₳ buys a working product, a city pilot, and open materials—not office costs. Incentives are disciplined and taper as habit forms.
• Reusable software. ~39% (₳33k) funds engineering, loyalty contracts, and the public dashboard that any fleet can reuse.
• Targeted incentives. ~36% (₳31k) is time-boxed driver/rider incentives that kick-start behavior and are contingent on real, on-chain rides.
• Connectivity, not infrastructure. ~8% (₳7k) equips cars with MiFi hotspots + prepaid top-ups and dual-SIM devices—cheap, portable, and proven in Iraq—rather than building servers or new networks.
• Field materials. ~9% covers signage, training, and QA to make checkout succeed in motion (AR/KU/EN, large targets, quick guides).
• Independent checks. Security review + monitoring/backups (~4%) safeguard funds and user experience.

Rough split of ₳85k: Engineering 28%, Loyalty/Dashboard 11%, Incentives 36%, Connectivity 8%, Kits/Training 9%, Security/Hosting 3%, Contingency 4%.

Cost per verified result (ceiling, given our targets):

• ≤7.1 ₳ per on-chain ride (₳85,000 / 12,000).
• ≤28.3 ₳ per new unique wallet (₳85,000 / 3,000).
• ≈566 ₳ per active driver (₳85,000 / 150).

Every figure is backed by a dashboard and explorer links, not survey claims.

Proportionality to local delivery

• Labor: We deploy local Android/Cardano engineers and field ops in Baghdad/Erbil. Rates are below typical EU/US contract prices, yet we still budget a security review and QA to keep quality high.
• Hardware & data: Commodity Android/MiFi devices and prepaid data top-ups keep unit costs low and swappable; garage partners already sell/handle these products for drivers.

Risk handling that protects value

• Milestone-gated disbursements halt spend if KPIs lag.
• Non-custodial design avoids treasury/float risk; refunds are explicit and auditable.
• Device ops (enrollment, remote lock/wipe) prevent leakage; anomaly alerts flag misuse early.

Ecosystem return beyond the pilot

• Open assets: MIT-licensed loyalty policies + SDK and a CC BY 4.0 Replication Playbook (AR/KU/EN) with signage/SOPs and Wi-Fi/top-up guidance. Teams in other cities can copy/paste with minimal engineering.
• Data for builders: Public datasets (rides, wallets, redemptions, success/latency) help wallets, analytics teams, and researchers improve UX and target future campaigns.
• Merchant pull: Once riders learn “scan → pay → earn” in taxis, nearby cafés/pharmacies can adopt the same flow using our contracts and materials.

Path to sustainability:

• Platform fee 3–5% on on-chain fares + optional dispatcher dashboard subscription cover ongoing support, MiFi swaps, and device maintenance.
• Incentives taper as loyalty repeats take hold; signage and kits are reusable.
• Hardware is redeployable; if a fleet exits, kits move to backup partners.

Future outlook: normalizing Cardano in daily Gulf life:

This small, focused investment seeds a repeatable habit at city scale. With 150 drivers we demonstrate reliable checkout with Wi-Fi top-ups and offline codes. With the same code and playbook, adding +500 drivers (letters/MoUs at close-out) can lift usage dramatically: even a conservative 100 on-chain rides/driver/month yields 50,000 rides/month across Baghdad/Erbil—visible, verifiable activity that spills into cafés, deliveries, and service shops that already interact with taxi drivers daily. Because the contracts, SDK, and materials are open and localized, any Cardano team in the Gulf can extend the model in weeks, not months.

Bottom line: For ₳85k, the community gets thousands of verified transactions, thousands of new wallets, a working connectivity-aware pattern (MiFi + top-ups) for the region, and a public playbook that turns one city pilot into a template for everyday Cardano across the Gulf.

[Required Acknowledgements] Consent & Confirmation

Terms and Conditions:

Yes