All-or-nothing crowdfunding.
Goal met, funds release in three stages that backers can veto; goal missed, every backer refunds in full.
Acting as
Wallets
- Rani9,400
- Bima10,000
- Sari10,000
Epoch
0 / deadline epoch 5
Campaigns
Create a campaign
History
Simulated history — demo hashes, no real chain. Select an entry to open its block.
About What this is · how it works
What this page is
This page runs a faithful in-browser simulation of the
CrowdfundCampaign Rust template — same rules, same rejection messages.
Nothing here touches a network or a wallet.
How it works
- One campaign = one component.
new(title, promise, goal, deadline_epoch, bond)opens it; the caller becomes the creator and locks a bond ofmax(goal / 10, 100)in its own vault. - Promise on the record. The creator's promise — what backers get — is stored on-chain and shown on the card, labeled as the creator's promise. The template does not enforce it; the bond and the veto are the enforcement.
- Escrow vault.
pledge(bucket)deposits TARI into the campaign vault and records the backer in a ledger. Pledges accumulate; overfunding is allowed. - Epoch deadline. Pledges are accepted while
current_epoch < deadline_epoch. Atcurrent_epoch >= deadline_epochthe campaign settles — the boundary is tested both ways. Funding stays all-or-nothing: goal missed → every backer refunds in full, once. - Staged release. Goal met →
claim()pays one tranche per call: three equal thirds of the total pledged, at gatesdeadline + 0, 72, 144epochs. No single release dominates. - Backer veto. From the deadline until each release, any backer may
veto(). Votes are pledge-weighted; strictly more than half freezes the rest, and refunds pay pro-rata shares of what remains plus shares of the forfeited bond. The tally resets on each release. - Abandonment. If the creator claims nothing for 72 epochs past a gate, anyone may call
abandon()— same refund path as a veto, bond included. - Events.
CampaignCreated,Pledged,Funded(once, when the goal is first reached),TrancheReleased,CampaignCompleted,VetoCast,VetoSucceeded,Abandoned,BondForfeited,BondReturned,Refunded— indexable by explorers. - Access rules. Methods are callable by anyone; authorization is enforced in code by comparing the transaction signer to the recorded creator/pledge keys. The template creates no resource, so there are no owner-bypassable resource rules.
Live mode
What live mode would need: a published template address on Esmeralda/mainnet, the
window.tari provider (Sapient extension or Tari Universe web wallet), and indexer reads for
campaign discovery. None of that is configured here, so this demo stays in simulation. The stub code
in live.js only detects a wallet and reports status — it never prompts, never signs, and
never submits a transaction.
Build and test commands, stretch ideas, and the full honest-limits list live in the README.
Proof
52 / 52
engine tests
Real Ootle engine, in-process
46 / 46
parity checks
Simulation matches the template
160,863 bytes
WASM template
15.3% of the 1 MiB cap
Run it yourself
cargo test
node --test app/sim.test.mjs
cargo clippy --all-targets
Guided walkthrough — about 4 minutes 0 / 16 steps complete
Sixteen steps. Each ticks itself off as you do it — including the rejections.
- Pledge 400 as Bima on Community radio.
- Switch to Sari and pledge 600 on Community radio — the goal fills and the
Fundedevent fires. - Pledge 300 as Bima on Neighborhood mural. Do this before advancing time: pledges close at the deadline. This campaign will miss its goal — that is what makes the refund steps below possible.
- Switch to Rani and try Claim before the deadline — it must be rejected (too early).
- As Rani, create Rooftop garden: goal 900, promise “Backers get a name on the garden gate + first harvest share.”, deadline 5 epochs. Note the 100 TARI bond — it leaves Rani's wallet at creation.
- Fund Rooftop garden: pledge 600 as Bima, then 300 as Sari.
- Advance the epoch to 5 (the deadline).
- Claim Community radio as Rani — tranche 1 of 3 pays out (333 of 1,000).
- As Bima, Veto Community radio — 400 of 1,000 is under half, so the veto fails. The tally stays visible; the campaign continues.
- Jump +72 to epoch 77, then claim tranche 2 as Rani. The veto tally resets on release.
- Veto as Bima, then as Sari — together over half, so the veto succeeds and the rest freezes.
- As Bima, Refund Community radio — a pro-rata share of what remains, plus a share of the forfeited bond.
- Switch to Bima and Refund Neighborhood mural — full repayment.
- Refund the same pledge again — it must be rejected (double refund).
- Finish Rooftop garden as Rani: claim tranche 1, jump +72, claim tranche 2, jump +72, claim tranche 3 — then Claim bond.
- Try refunding Rooftop garden — it must be rejected (refunds closed after completion).
Read before judging Honest limits
- This page is a simulation. No template has been published to Esmeralda or mainnet, and no on-chain state exists. The simulation mirrors the template rules and is parity-tested (
node --test app/sim.test.mjs); the template rules are proven against the real engine (cargo test, 52 tests). - The promise is not enforced. The promise text is the creator's words, stored on-chain and labeled as such. The template cannot check whether a radio station was built. Backers judge the promise; the veto is their enforcement tool.
- Released funds cannot be recovered. No code can force a human to work or claw back a released tranche. A creator who takes tranche 1 and vanishes keeps tranche 1. What the mechanism guarantees is bounded loss: unreleased funds stay under backer control, and the bond compensates backers on veto or abandonment.
- Majority apathy rules. A veto needs strictly more than 50% of pledged value. If most backers never act, releases proceed. Apathy is consent — that is the stated rule, not a hidden flaw.
- The bond prices dishonesty; it does not prevent it. A wealthy bad actor can afford to lose bonds. The bond raises the cost of every attempt and makes mass scam campaigns unprofitable at small scales; it is not a guarantee of good behavior.
- Parameters are protocol constants — 3 tranches, 72-epoch windows, 10% bond with a 100 floor — chosen and justified in the spec, not tuned to live TARI prices or real campaign data. A production deployment would revisit them with real usage data.
- Pledge amounts are public. Vault-based accounting means anyone can read who pledged how much. That is a deliberate design choice, not an oversight. Hiding amounts would need a confidential/stealth design and is out of scope.
- Live mode is not wired up. The section below detects a Tari wallet but cannot transact: no template address is published, so there is nothing to call. It will honestly say so. Never trust a demo that claims a live path it cannot show.
- Epochs are coarse on real networks (~20 min mainnet, ~1 h Esmeralda), so real veto windows last a day or more. The demo's epoch control exists only to make the story judgeable in minutes.
Live mode — stub, detection only. Checking for a Tari wallet…