Contributor Transparency

What you'll see after you contribute

Support should not end in silence. This page previews the planned post-contribution view — contribution status, milestone progress, evidence, and settlement state — none of which is live.

Contributor transparency preview only. No real contributions, no wallet custody, and no payment processing. The live database view below is read-only and count-only; every timeline and status value is static demo content.

Live database view

Contributions: 0 · Wallets: 0 · Audit log: 0

Read directly from the production database in read-only mode. Counts only — no wallet addresses, transaction hashes, or amounts are read or shown.

Database schema is live, but no contribution records have been created yet. Contribution writes remain disabled.

Read-only database view. Contribution writes not enabled. No real funds, no custody, no settlement, no wallet custody, and no payment processing. Contribution submission remains disabled pending review.

Note: a campaign may offer a private “register interest for later” form. Those are expressions of interest only — stored separately, with no wallet address and no amount — and are not counted as contributions. They never appear in the contribution count above, which stays at 0 until real contributions are enabled in a future, separately-approved gate.

Why transparency matters

Transparency keeps accountability running both ways after a contribution. None of this is operational today.

Contributors see where their support stands

After contributing, a backer will be able to see the status of their contribution and the campaign's progress — not just a thank-you and silence.

Builders see what must be delivered

The same view makes a builder's remaining milestones and evidence obligations clear, so accountability runs both ways.

Reviewers see milestone and evidence state

Reviewers will be able to see which milestones have evidence submitted and which are still pending review.

Settlement and return decisions are visible later

Settlement and return outcomes are intended to be shown here in a later layer. No settlement or return is triggered today.

Milestone progress

Preview example — not a database record

A preview example, not a database record. The planned path a contributor would follow after backing a campaign. No step reflects a real milestone, review, or return.

1
Milestone planned
Planned
A campaign's milestone is defined with its target and intended evidence. Demo content only.
2
Evidence submitted
Preview
The builder would submit proof of delivery. See the milestone evidence preview for how this will work. No real evidence is submitted.
3
Review pending
Pending preview
A reviewer would check the evidence against the milestone's claims. No review action runs today.
4
Approval or return
Later
Based on review, a milestone would be approved or a return considered in a later settlement layer. No approval, refund, or return is triggered here.

Contributor status

Preview only

Campaign: Demo campaign — Afrobeats on Chain (demo-1)
Contribution amount: ₳ 250 (demo)
Contribution status: Intent preview only / not live
Oracle snapshot: Mock ADA/USD reference — demo, not a live oracle read
Settlement state: Not live

Evidence

Milestone evidence is where proof of delivery lives. A contributor would follow these to inspect what was delivered and how it is reviewed.

Milestone evidence preview

How builders will submit proof of delivery and how it is inspected. Not live.

Learn more →

Review workflow

How campaigns and milestones are reviewed before approval. Not live.