Campaign Lifecycle
From builder idea to public accountability
One map for the whole system. Cardano Builders Fund is currently a prototype-safe public MVP — every stage below is a preview that links to its surface, and none of it is live.
The lifecycle map
The planned path a campaign would follow end to end. Each stage shows its current preview status and links to the relevant surface. No stage performs a real action today.
Builder profile
A builder establishes identity and focus. Demo profiles exist today; there is no real verification or auth.
View a demo builder→Campaign draft
A campaign is drafted with goal, story, and milestones. Demo campaigns only — nothing is submitted or published for real.
View a demo campaign→Contribution intent
A contributor previews what they would back and on what terms. No wallet, no signing, no ADA moves.
See contribution preview→Contributor transparency
After contributing, a backer would see status, milestone progress, and settlement state. No real contribution is looked up.
See transparency preview→Milestone evidence
Builders would submit proof of delivery against milestones. No real upload, storage, or database write.
See milestone evidence→Review workflow
Reviewers would check campaigns and milestone evidence before approval. No review action runs today.
See review workflow→Admin oversight
An operator surface would manage the review queue, verification, and settlement readiness. Every action is disabled.
See admin preview→Oracle / settlement readiness
ADA/USD reference comes from a mock oracle today. A live read remains gated and not enabled in production.
See oracle readiness→Future settlement or return decision
Milestone state would inform a later settlement or return decision. No settlement, payout, refund, or return is triggered.
See settlement direction→Preview only — nothing here is live
- No live funds and no custody of any kind.
- No wallet is connected and no transaction is signed.
- No database write happens; Prisma is not used in any app route.
- No KYC is collected and no identity documents are stored.
- No settlement, payout, refund, or return is triggered.
What becomes real later
Each item below is a future production gate. None of it is built today, and each would be a separate, deliberate step.
Authentication
Accounts and sign-in for builders, reviewers, and contributors. Not implemented.
Wallet connection
Proof-of-control by signing a message — never custody. Not implemented.
Contribution records
Real contributions persisted and tied to campaigns. Not implemented.
Milestone evidence storage
Uploaded evidence stored and referenced off the request path. Not implemented.
Reviewer / admin permissions
Role-gated review and operator actions. Not implemented.
Oracle live-read approval
A separately approved switch from mock to a live preprod/mainnet read. Not enabled.
Settlement / return rules
Rules that decide settlement or return from milestone state. Not implemented.
This is the first stop on the guided walkthrough. This page describes intended process only. Builders can preview the onboarding path, explore the demo campaigns, or see status & roadmap for what is planned next. Nothing here is legal, tax, or financial advice.