threshold. CROWDFUNDING ON OOTLE
Bounties ↗
THRESHOLD / EXPERIMENTAL PROTOCOL

Fund work together.
Pay in stages.

Threshold is a crowdfunding protocol on Ootle. A community and a sponsor fund a shared goal, with payment rules agreed before anyone pledges.

The full budget must be committed before payments begin. Work can be paid in milestones, with named reviewers approving delivery. If things fall through, contributors can recover eligible unpaid funds after the deadline.

Simulation · no wallet neededBounties powered by Threshold ↗
What the protocol does—and does not—guarantee

The contract enforces funding and payment rules; reviewers judge the work. Released payments cannot be reclaimed. Contributions use confidential outputs, but participation remains visible and a coordinator may learn shared amounts. Recovery needs your backup, fee funds, and network access. This implementation is testnet-only and unaudited.

What could your community fund?

The five additional Ootle templates are proofs of concept: compiled and checked for basic terms, but not deployed or tested end to end.

DEMO FUNDS Community 60 / 60 Sponsor Paid SUCCESS PATH
THRESHOLD / INTERACTIVE DEMO

Try a developer bounty

A community and a sponsor raise 100 tTARI for a new software feature. The developer gets 10 to start once the goal is funded, and 90 after approval.

Turn on the switches to reveal the next step. Go back and change any decision to see what happens.

Payment steps If something goes wrong Current step

This is a simulation. No funds move. You can undo decisions here; real payments and refunds cannot be undone, and campaign terms are fixed before funding.

CAMPAIGN SANDBOX

What would you fund?

Design the campaign around your idea. Explore today's funding rules and possibilities for future templates. Everything here is hypothetical and independent of the bounty map.

01 Shape the funding

Deadlines are offsets from creation, not calendar dates. Every stage is funded together. Larger numbers are design inputs, not demonstrated capacity.

02 Define the work

Name each deliverable and recipient. Relative weights divide the reviewed budget. Each stage has its own review group.

Names are labels, not wallet addresses. Real campaigns bind recipients and reviewers to keys before funding. Different keys do not prove independent people.

03 Explore the outcome

    COMMUNITY
    SPONSORS
    FIRST PAYMENT
    Try funding each side
    What if work stops?

    Assume the displayed stages were paid in order after valid approval. Explore what remains when the next stage misses its deadline.

    Your payment schedule

    No deployment or transactions. Real payments require valid proofs, recipient checks and signatures. Recovery needs each owner's backup, fee funds and network access. Released money cannot be recovered.
    USE CASES

    What can you fund?

    Choose an example to see who pays, when work gets paid, and what the limits are.

    Fits v1 with a sponsor

    A new software feature

    Users and a sponsor pay a developer to build a feature they need.

    1. Full community + sponsor match
    2. Agreed start payment
    3. Reviewers accept the delivery

    No delivery? Contributors can reclaim unpaid funds after the deadline. Money already paid cannot be recovered.

    The additional templates are proofs of concept. Compilation and basic term checks passed; transaction, recovery, and testnet testing are still needed.

    Privacy and refunds

    Contribution amounts are encrypted. Participating wallets and campaign totals remain public.

    To claim an eligible refund yourself, you need your saved recovery file and unlock key, funds for transaction fees, and network access.