EchoSafe: A Cardano dApp Securing Medical and Mental Health

[Proposal setup] Proposal title

Please provide your proposal title

EchoSafe: A Cardano dApp Securing Medical and Mental Health

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

36500

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

Millions of trauma survivors risk losing their stories to paper loss or data leaks. They deserve a safe, private home for their health and healing one that protects dignity and ownership for life.

[Proposal Summary] Supporting Documentation

Supporting links

• https://x.com/EchoSafeHQ
,
• https://github.com/Nazrawi15/Echosafe
,
• https://medium.com/@EchoSafe
,
• https://www.researchgate.net/publication/394356073_EchoSafe_A_Cardano-Based_dApp_for_Trauma_Recovery_Privacy_and_Decentralized_Health_Logging_Authors
,
• https://docs.google.com/document/d/1wUtEfAyzdLsHw0Hca0VYC0Q52cWqFGekonfcdTRHsZI/edit?usp=sharing

[Proposal Summary] Project Dependencies

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

No

Describe any dependencies or write 'No dependencies'

No dependencies

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

Yes

License and Additional Information

All EchoSafe source code (smart contracts, Android, backend/frontend) is released under Apache-2.0, which allows use, modification, and commercial redistribution with LICENSE/NOTICE kept and changes marked. Documentation is under CC BY 4.0 (reuse with attribution), and schemas/example data are under CC0 1.0 (public domain). The “EchoSafe” name and logo are reserved trademarks and not covered by these licenses.

[Theme Selection] Theme

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

Healthcare

[Campaign Category] Category Questions

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

EchoSafe is the first trauma recovery platform on Cardano, built by a survivor for survivors. It unites secure medical record storage (CIP-25 metadata), private mental health journaling, and anonymous peer-support in one app. Leveraging blockchain, IPFS, and AES-256 client-side encryption, it ensures records are permanent, private, and user-owned. Designed for low-infrastructure and crisis regions, it restores dignity, safety, and control—proving Cardano can protect people, not just money.

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

By the final phase, EchoSafe’s MVP will be live on the Cardano testnet, showing how survivors can securely store medical records, journal privately, and connect for support all in one app. It will be accessible on web or mobile using Eternl, Yoroi, or other Cardano-supported wallets. Before mainnet, we’ll run a 50 person workshop to test it, gather feedback on Discord, GitHub, and Telegram, refine the app, and then host a two-day “Help Us Heal” public testnet campaign to collect wider community feedback before launch.

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

Over the 8-month build, EchoSafe aims to onboard 150 trauma survivors, 15 NGO facilitators, and 10 healthcare professionals.

Expected on-chain impact: ~1,800 metadata transactions for encrypted medical logs and journals, ~450 Plutus smart contract calls for forum moderation and NFT access control, and ~700 encrypted IPFS pins. Around 70 weekly active users will generate ~250 peer support posts. All results will be transparently verifiable via Cardano Explorer and Pinata dashboards.

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

Understanding The Problem

Millions of trauma survivors — from accident victims and refugees to people with chronic illness or PTSD — don’t have a safe, private way to keep their medical and recovery records. In places with few resources or political instability, paper files can be lost or destroyed, and centralized digital systems can be hacked, censored, or deleted. Without a secure, survivor-owned platform, people lose control of their health history, making it harder to get proper care, protect their rights, or heal emotionally. The lack of mental health support makes this even worse, leaving many without safe spaces to share, connect, or seek help.

Our Solution

EchoSafe is a decentralized, survivor-led trauma recovery and health journaling platform built on Cardano. It’s designed to ensure privacy, long-term access, and complete user control. The platform combines four integrated, open-source modules:

Medical Records Module

• Use CIP-25 initially; evaluate a CIP-68-style updatable pointer for evolving records; no PHI on-chain
• Stores large files (CT scans, X-rays) on IPFS, encrypted client-side with AES-256.
• Survivors keep their own decryption keys in their Cardano wallets, with optional secure re-encryption for sharing.

Encrypted Mental Health Journal

• End-to-end encrypted diary entries and mood tracking.
• Immutable CIDs on-chain create a verifiable recovery timeline.
• Survivors control who can access entries and when, with visibility revocable at any time (even though the underlying data remains permanently stored).

Peer Support Forum

• CIP-30 wallet login for pseudonymous, KYC-free participation.
• Plutus moderation contracts enforce community rules set and updated through survivor-led DAO governance.

Why This Approach

We built EchoSafe with a privacy-first mindset, shaped by the real experiences of trauma survivors. Every feature is designed to be safe, trigger-free, and usable even with poor internet access. Cardano’s blockchain ensures records are permanent and tamper-proof, IPFS keeps storage affordable, and AES-256 encryption means only the survivor can unlock their data. Our open-source, modular design lets NGOs, developers, and communities worldwide adapt and grow the platform for their own needs.

Who We Engage

EchoSafe brings together people who can make real change:

• Trauma Survivors – Giving them back control of their recovery story, their data, and their dignity.
• NGOs and Healthcare Workers – Providing secure, anonymized insights to better support those in need.
• Cardano Developers – Offering a ready-to-use, standards-based codebase to inspire the next wave of social-good dApps.
• Everyday People New to Crypto – Introducing blockchain in a way that’s practical, safe, and meaningful — far beyond speculation.

Proving Impact

We’ll prove EchoSafe works — both in the data and in people’s lives.

• 1,800+ blockchain transactions, 450+ smart contract calls, and 700+ encrypted journals in 8 months
• 150 survivors, plus NGO and healthcare partners, actively using the platform
• 80%+ satisfaction rate, backed by real survivor stories and NGO case studies
• All results 100% transparent and verifiable on Cardano Explorer, IPFS, and GitHub

Because in the end, success isn’t just numbers — it’s trust, dignity, and lives improved.

Why This Matters to Cardano

EchoSafe proves Cardano can change lives, not just finance. Built by a trauma survivor, it’s the first holistic trauma-recovery dApp on the network — private, resilient, and designed for real-world use. Every journal entry or medical log creates a tamper-proof, timestamped blockchain record, with encrypted content stored off-chain on IPFS. This generates thousands of purposeful transactions, Plutus calls, and IPFS integrations, driving real network utility.

Beyond numbers, EchoSafe brings in survivors, NGOs, healthcare workers, and non crypto users, introducing them to blockchain through a meaningful, non-speculative application. Its open-source design gives developers a blueprint for future social-good dApps, strengthening Cardano’s reputation as a platform for ethical, impactful technology.

[Your Project and Solution] Impact

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

Value to the Cardano Community

EchoSafe brings Cardano into spaces Web3 has often ignored — healthcare, mental wellness, and humanitarian aid. As the first survivor-led trauma recovery dApp on the network, it proves blockchain can protect people, not just assets, using metadata standards (CIP-25), wallet integration (CIP-30), and smart contracts for real-world good.

By engaging trauma survivors, NGOs, and health workers — including refugees, rural communities, and crisis-affected populations — EchoSafe introduces blockchain through a life-changing, trust-based experience. This broadens Cardano’s user base, drives new types of transactions, and strengthens its standing as the blockchain for ethical, impactful innovation.

Because the entire codebase is open-source, developers can reuse EchoSafe’s trauma-informed design, metadata schema, and NFT-based access controls to build other social-good dApps, accelerating progress in health, education, and identity on Cardano..

Expected On-Chain and Community Impact

Expected On-Chain & Community Impact

We expect EchoSafe to generate real, verifiable activity on Cardano — not just promises. In the first 8 months, we aim for:

• ~1,800 blockchain transactions for encrypted medical logs and journals

• ~450 Plutus smart contract calls for forum moderation and NFT-based access control

• ~700 encrypted files pinned on IPFS

• ~70 weekly active users posting about 250 peer-support messages

• Onboarding 150+ survivors and 15 NGO staff

All of this will be fully transparent: anyone can check our progress through Cardano Explorer for transactions and smart contract calls, and Pinata dashboards for IPFS storage. By setting a live example of using CIP-25 and CIP-30 for sensitive health data, EchoSafe will open the door for similar humanitarian projects across the ecosystem.

Measurement & Verification

We’ll measure EchoSafe’s impact in ways that matter — both in hard data and in real human stories.

What We’ll Track (On-Chain & Auditable)

• Number of blockchain metadata transactions

• Plutus smart contract calls

• Encrypted files pinned on IPFS

• Weekly and monthly active users

• NFTs issued for access control

What We’ll Hear (From the Community)

• At least 80% satisfaction in survivor and NGO surveys

• NGO case studies showing better continuity of care and stronger privacy

• Survivor testimonials on how EchoSafe built trust and encouraged adoption

How You Can Verify It

• All transactions and contracts visible on Cardano Explorer

• IPFS stats available through the Pinata dashboard

• Code commits and updates published on GitHub

• Monthly progress reports shared openly on Catalyst forums and social channels

This way, every number — and every story — can be traced, verified, and trusted.

Sharing Our Work & Creating Opportunities

We’re building EchoSafe to be more than just an app — it’s a blueprint others can use to create real impact. Everything we produce will be open, reusable, and easy to build on.

1. Open-Source Codebase – The full front-end, back-end, and Plutus scripts will be released under an MIT license on GitHub, with clear, practical documentation so others can use or adapt them.
2. Metadata Schema Library – A ready-to-use JSON schema for CIP-25 medical and journal records, making it simple for developers to plug EchoSafe’s structure into their own projects.
3. Guides & Tutorials – A “Zero-to-Hero” step-by-step guide showing exactly how to fork, deploy, and customize EchoSafe for other social-good purposes.
4. Community Spaces – Active Telegram and Discord channels for support, feedback, and feature ideas — connecting survivors, NGOs, and developers in one place.
5. Workshops & Webinars – Live sessions before testnet, after testnet, and after mainnet launch to help NGOs, health workers, and devs start using or building on EchoSafe.
6. Speaking & Showcasing – Sharing EchoSafe’s design and adoption model at the Cardano Summit and global blockchain for social good events to inspire wider adoption.

By making every part of EchoSafe open and accessible, we’re not just solving one problem — we’re creating a ripple effect of tools, knowledge, and opportunities for the entire Cardano community

Long-Term Ripple Effects

EchoSafe isn’t just another dApp it is proof that blockchain can protect people, not just assets. By achieving real adoption in one of the hardest and most meaningful spaces trauma recovery and we set a powerful example for how Cardano can be used in humanitarian work.

This project will show, in practice, that Cardanos technology is built for privacy-first, socially relevant applications, even in places where internet access and infrastructure are limited. It will also open doors to lasting partnerships with NGOs, healthcare providers, and global aid organizations, bringing new funding, credibility, and real-world deployments to the Cardano ecosystem.

Our success won’t be measured only in transactions or user counts, but in the survivors who regain control of their stories, the trust we build in vulnerable communities, and the precedent we set for Cardano as a platform that stands for dignity, resilience, and positive change.

[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 you can trust us to deliver

• Survivor-led + technical lead. The project is led by a survivor with strong, hands-on software skills, ensuring the product serves real needs and the build stays practical.
• Named roles with proof. Project Lead (Nasser), FE/BE dev (Salm), pre-engaged Plutus and Android specialists.
• Technical breadth. Plutus smart contracts, Cardano metadata, IPFS, AES-256, React/Node—covered in-house or by pre-engaged talent.

How we manage funds (trust and accountability)

• Multisig treasury + milestone gates. ADA sits in a multisig; two signatures required per completed deliverable. Payouts map 1:1 to accepted evidence.
• Public ledger. Monthly publication of hours × rate per role, receipts, and links to code/tx hashes.
• On-chain and GitHub proofs. Every deployment and key action leaves a verifiable trail (explorer links + commits).

Feasibility: how we will validate the approach

• Prototype plan (time-boxed):

1. Month 2: metadata ingestion script, IPFS pinning demo, AES-256 pipeline. Evidence: CIDs, code, run logs.
2. Month 4: Plutus contracts on testnet (escrow + moderation) with ≥100 automated calls. Evidence: tx hashes, CI reports.

• User testing: Closed beta with NGO partners; targets ≥80% task completion and ≥90% encrypt/decrypt success.
• Security checks: Third-party review of Plutus + API; open bug-bounty for critical findings.
• Public testnet: Open testing with workshops; collect ≥50 issues and 20 feature requests before mainnet.

Existing capabilities that fit this project

• Modules already specified: medical logs (CIP-25), encrypted journal, pseudonymous forum, doctor booking escrow—each with clear data flow and privacy controls.
• Cardano-native architecture: metadata for proofs, NFTs for role gating, smart contracts for interactions; IPFS for files.
• Acceptance criteria & evidence defined: testnet metadata visible, NFT-gated reads, APK + beta link, mainnet tx hashes, public repo, final report.

Processes that prove accountability (month over month)

• Plan → build → prove loop 1. Plan: spec + risk log + acceptance checklist.

•        2. Build: code + tests in CI; dev notes.
  

•        3. Prove: attach hashes, CI runs, screenshots, invoices to the monthly report.
  

•        4. Pay: multisig releases only after evidence is verified. 
  

• Community reporting: monthly posts, open workshops, Discord/Telegram support channels for transparent feedback.

Partnerships and domain fit

• NGO and clinical partners for recruitment, validation, and training ensure real users and realistic constraints (connectivity, privacy).
• Dev mentors + community to review contracts and architecture in public sessions.

Risks and mitigations (pre-agreed)

• Data sensitivity: end-to-end encryption; user-held keys; NFT-gated permissions; pseudonymous wallet access.
• Adoption: co-design with survivors; multilingual, offline-first Android; training events.
• Bugs/regressions: staged testnet > closed beta > public testnet with CI-backed coverage before mainnet.
• Budget variance: 10% contingency and deliverable-linked contracts.

How we will show feasibility, not just claim it

• Measured outputs: target counts for metadata txs, script calls, IPFS pins, forum activity, DAO proposals all public and checkable.
• User outcomes: pilots with survivors/NGOs and ≥80% satisfaction from structured surveys.
• Open-source release: full code + docs under permissive license so other builders can reuse immediately.
• Our Abstract is Already posted in researchgate: https://www.researchgate.net/publication/394356073_EchoSafe_A_Cardano-Based_dApp_for_Trauma_Recovery_Privacy_and_Decentralized_Health_Logging_Authors

Bottom line: we pair survivor-grounded product sense with a public, evidence-first delivery process: multisig releases, monthly ledgers, on-chain/GitHub proofs, third-party reviews, and testnet → mainnet validation. That’s high trust, high accountability, and technically feasible on Cardano today.

[Milestones] Project Milestones

Milestone Title

Architecture and UI Design

Milestone Outputs

• A web-based dApp allowing anonymous trauma entries
• Integration with IPFS for decentralized data storage
• Metadata embedding using Cardano testnet transactions
• Backend API built in Node.js or Java (depending on team stack)

Acceptance Criteria

• Users can submit trauma logs without login or KYC
• Logs are hashed and stored in IPFS
• Metadata for logs appears correctly in Cardano testnet explorer
• At least 10 successful end to end submissions (CID ↔ testnet hash) recorded for QA proof.
• Figma: https://docs.google.com/document/d/1wUtEfAyzdLsHw0Hca0VYC0Q52cWqFGekonfcdTRHsZI/edit?usp=sharing

Evidence of Completion

• GitHub repository with smart contract + dApp code
• Testnet transaction hash with visible metadata
• Video walkthrough showing IPFS + metadata process

Delivery Month

2

Cost

9350

Progress

30 %

Milestone Title

Smart Contract Deployment

Milestone Outputs

• Smart contracts for NFT-based role permissions (helpers,

counselors)

• NFTs minted with specific access rights (e.g., read-only, reply

rights)

• Frontend integration for verifying wallet roles

Acceptance Criteria

• Access attempts logged on testnet
• Role-NFT holders can access gated views; unauthorized wallets are blocked.
• ≥100 testnet calls across mint/verify/moderation paths (logs visible).
• All access attempts logged off-chain with signed logs; weekly on-chain checkpoint (hash only).

Evidence of Completion

• Plutus smart contract deployed to testnet
• GitHub repo with contract code and access logic
• Access logs recorded on blockchain

Delivery Month

4

Cost

9850

Progress

40 %

Milestone Title

Mobile UI, Localization and Pilot Testing

Milestone Outputs

• Android mobile app with basic trauma logging functions
• Multilingual interface (e.g., Tigrigna, Luganda, Amharic, English)
• Community pilot with at least 50 testers ( local NGO contacts, refugees and Trauma Surviors)

Acceptance Criteria

• App installs successfully and functions offline-first
• Testers can submit entries, receive tokens or responses
• Installs succeed on ≥90% of test devices; and 10% crash rate.
• ≥80% task-completion (create log, view history, submit journal) and ≥80% satisfaction in surveys.
• Pilot produces ≥150 medical logs and ≥200 encrypted journal entries (CIDs counted), ≥30 peer interactions.

Evidence of Completion

• APK file and Play Store beta link
• Survey or interview reports from testers
• Screenshots and crash logs for QA verification
• Photos of the Pilot Program

Delivery Month

7

Cost

9200

Progress

80 %

Milestone Title

Mainnet Deployment, Open Source Launch and Final Report

Milestone Outputs

• Full deployment to Cardano mainnet
• Full codebase open-sourced
• Community video or blog post explaining the project impact
• Final PDF report (on-chain metrics, security posture, lessons) + 1 explainer video + community blog.

Acceptance Criteria

• All code publicly available and documented
• All modules work on mainnet without critical bugs; repo public with README, LICENSE, schemas.
• Report includes verifiable mainnet tx hashes, forum/journal counts, and IPFS interactions.
• Post-launch trajectory aligns with network-impact ladder (e.g., path toward ≥5,000 metadata tx and ≥1,000 script calls after launch).
• Final report submitted to Catalyst tea

Evidence of Completion

• Mainnet transaction hashes
• GitHub repo (public) with documentation
• Final report PDF and video walkthrough

Delivery Month

8

Cost

8100

Progress

100 %

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Total = 36,500 ADA

Month 1 — 1,190 ADA

• Front End/Back End setup (₳740): design system, API skeleton, repo structure.
• Project Management and documentations (₳200): delivery plan, reporting template.
• Infra (₳150): domain, CI, staging environment.
• Research/localization (₳100): EN/Tigrigna terminology, consent copy.

Notes:

• Acceptance evidence: repo initialized, CI green, staging URL live, design tokens committed.

• Risks → mitigation: design sprawl → freeze core components end of M1.

• Third-party used: domain, CI runners (in Infra).

Month 2 — 1,189 ADA

• Front End/Back End setup (₳739): finalize UI kit, stable API endpoints.
• Project Management and documentatios (₳200): specs, delivery calendar.
• Infra (₳150): staging upgrades.
• Research/localization (₳100): privacy copy + UX strings.

Notes:

• Acceptance evidence: OpenAPI/Swagger doc, component library snapshot, staging endpoint list.

• Risks → mitigation: scope creep → change-control with cost/time impact.

• Third-party used: same Infra stack as M1.

Month 3 — 5,085 ADA

• Plutus part 1 (₳4,085): NFT role-gating policy, metadata writes, escrow design; unit tests start.
• QA (₳300): test harness in CI.
• Security (₳350): threat model draft + review.
• Project Management and documentation (₳200); Infra (₳150): testnet + IPFS pinning.

Notes:

• Acceptance evidence: policy script ID, test coverage report, threat model v1, testnet txn hashes.

• Risks → mitigation: wallet/SDK quirks → time-boxed spike and fallback path.

• Third-party used: IPFS pinning provider; testnet RPC (Infra).

Month 4 — 5,084 ADA

• Plutus part 2 (₳4,084): off-chain code, integration tests, docs.
• QA (₳300): contract coverage increase.
• Security (₳350): findings + fixes.
• Project Management and documentation (₳200); Infra (₳150).

Notes:

• Acceptance evidence: contract addresses on testnet, passing integration suite, mitigation log for security findings.

•Risks → mitigation: failing tests → code reviews + pair sessions.

• Third-party used: pinning, RPC (Infra).

Month 5 — 6,381 ADA

• Android part 1 (₳3,381): offline-first logging, IPFS wiring, wallet connect start.
• Accessories (₳2,000): shirts/banners/stationery for outreach.
• QA (₳500): pilot devices + test passes.
• Project Management and documentation (₳200); Infra (₳150); Research/localization (150).

Notes:

• Acceptance evidence: signed APK, offline write/read demo, device matrix, outreach materials ready.

• Risks → mitigation: device fragmentation → prioritized test device list.

• Third-party used: Google Play fee (Infra), IPFS, email service.

Month 6 — 6,480 ADA

• Android part 2 (₳3,380): wallet flows, beta build, bug fixes.
• Seminar 1 (₳2,100): venue/promo/refreshments → signups & installs.
• QA (₳500): beta testing rounds.
• Project Managemena and documentation (₳200); Infra (₳150); Research/localization (₳150).

Notes:

• Acceptance evidence: beta build link, crash-free rate report; seminar agenda, photos, attendee sheet, wallets/installs created.

• Risks → mitigation: turnout risk → early invites + local partners.

• Third-party used: venue/catering/promo vendors; Play Console.

Month 7 — 2,470 ADA

• Final dev part 1 (₳1,180): Front End/Back End polish, analytics, release prep.
• Security (₳500): pre-launch checklist.
• QA (₳300): regression pass.
• Project Management and documentation (₳150); Infra (₳150); Research/localization (₳190).

Notes:

• Acceptance evidence: release candidate, security checklist signed, regression report.

• Risks → mitigation: late-breaking bugs → freeze window + rollback plan.

• Third-party used: monitoring/logging (Infra).

Month 8 — 4,971 ADA

• Final dev part 2 (₳1,179): store assets, launch fixes.
• Workshop (₳2,500): partner training and deployments.
• Security (₳500): go-live signoff.
• QA (₳300): smoke tests.
• Project Management and documentation (₳150); Infra (₳150); Research/localization (₳192).

Notes:

• Acceptance evidence: app live, workshop materials, photos, trained partner list, on-chain activity from pilots.

• Risks → mitigation: partner scheduling → lock dates in M6.

• Third-party used: venue/training materials; store listing.

Contingency — 3,650 ADA

Only for verified overruns; requires change note + approval.

Notes:

• Use order: contingency → trim noncritical (accessories/event scale) → never cut security/QA first.

Role caps (reference; already distributed above)

• Plutus: 105h × $45/h → 6,655 ADA
• Android: 100h × $30/h → 4,225 ADA
• Front/Back-end: 160h × $35/h → 7,887 ADA

Third-party products and; services (what and where)

• IPFS pinning/gateway + bandwidth → Infra (M3–M8).
• Cloud/API hosting, domain, CI, email → Infra (M1–M8).
• Google App developer fee → Infra (M5–M6).
• Security review (independent) → Security (M3–M4, M7–M8).
• Accounting/reporting → Project Management and documentation (all months).
• Pilot devices → QA (M5–M6).
• Venues/catering/promo → Seminar (M6), Workshop (M8).
• Accessories → Month 5.

Fund stewardship

• Monthly public ledger (hours × rate per role) + receipts.
• Disbursements only after evidence for that month.
• Progress updates + final report published.

Keeps audit artifacts (code, tests, invoices, event proof) ready.

[Final Pitch] Value for Money

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

Value for the Cardano ecosystem

• New use case, real users. EchoSafe proves Cardano beyond finance—privacy-first trauma recovery. That’s credible, non-speculative utility that pulls in survivors, NGOs, and clinicians—not just crypto-natives.

• Cardano-native design. IPFS for data, NFTs for access, Cardano metadata for proofs → sustained on-chain activity (mints, role checks, log commits).

• Reusable building blocks. We open-source the NFT role-gating policy, metadata schemas, and “trauma-safe” UX patterns so other teams can fork and ship faster.

• Growth engine. Seminar + workshop convert outreach into wallets, pilots, and integrations—compounding value for the ecosystem.

Why the cost is reasonable (with evidence)

• Plutus – 6,655 ADA (105h @ $45/h): Below typical smart-contract ranges (≈$60–$120/h; median ~ $80/h) seen on major freelance markets (e.g., Upwork/TopTal).

• Android – 4,225 ADA (100h @ $30/h): Squarely within common mobile rates (~$15–$35/h) reported across marketplaces and salary trackers.

• Front/Back-end – 7,887 ADA (160h @ $35/h): Near the low end of general web-dev bands (~$15–$50/h).

• Regional efficiency: Uganda baselines are well below global blockchain rates; using local FE/Android plus a lean Plutus specialist keeps quality high and totals tight (PayScale/Glassdoor bands support this).

• Infra priced to reality: IPFS pinning/bandwidth matches published tiers from Pinata/Web3.Storage, leaving headroom for traffic spikes.

Why non-dev lines exist (and add value)

Security review (1,700 ADA): Independent pass on role/escrow paths; far cheaper than post-incident fixes.

QA & testing (2,200 ADA): Covers offline/low-bandwidth edge cases typical in our regions.

PM & documentation (1,500 ADA): Funds monthly public ledgers (hours×rate), milestone evidence, and final reports (per Catalyst guidance).

Seminar 1 (2,100 ADA) + Workshop (2,500 ADA) + Accessories (2,000 ADA): Converts outreach into wallets, installs, and partner pilots.

Unit-economics snapshot

• Cost per role-gated contract suite (minting + checks + escrow + tests): covered inside the Plutus cap 6,655 ADA → strong ROI as a reusable library.

Governance & fund stewardship

• Milestone-tied disbursements. We only draw when acceptance criteria are evidenced.

• Public ledger. Monthly publication of hours × rate per role and receipts.

• Compliance. We align with Catalyst Fund Rules on reporting; non-compliance risks suspension we budgeted PM/docs to avoid that.

Devil’s-advocate check (and our answer)

• “Why not cheaper?” Our smart-contract rate is already below market medians; cutting further risks security/velocity. Android/FE rates sit at the low end of industry bands.

• “Infra looks padded.” It maps to published IPFS tiers and includes egress; running out of bandwidth mid-pilot would cost more.

Bottom line

For 36,500 ADA, the ecosystem gets: audited contracts, a privacy-first Android MVP, real-world pilots, open-source components others can reuse, and net-new users who see Cardano as a platform for dignity not just speculation. That’s high leverage per ADA, with transparent reporting and deliverables designed to compound value.

[Required Acknowledgements] Consent & Confirmation

Terms and Conditions:

Yes