One rule: teams set milestones freely, and cannot change the outcome once locked.
No manual shortcuts. No discretionary approvals. No cross-branch flows. The whole protocol is built around that single rule.
Anatomy of a branch
A vault is a set of independent branches. Each branch is fully described by four parameters, written on-chain and immutable after the deposit window closes.
{{ p.desc }}
Lifecycle of a vault
{{ it }}
Two outcomes. Nothing in between.
The resolution source confirms the milestone. Anyone — literally any address — can call the disbursement function. The branch's full locked amount moves to the declared team address; the success fee is taken on the disbursed portion; the transaction appears on the public status board.
No approval needed, no vote, no committee. The branch flips to refundable automatically. Each contributor calls withdraw and receives exactly their pro-rata share as recorded in the contribution ledger at deposit time. No success fee is taken on refunded capital.
The mechanism, drawn
Contributions enter the vault; the door closes and the brass seal is set. Parameters freeze on-chain.
The market's resolved answer acts on exactly one gate's lock. Other branches don't move.
A missed deadline routes the still-sealed capital back to contributing wallets, pro-rata.
Capability roadmap
Ordered by technical dependency, not by dates. P0 must be complete — and independently audited — before any real vault opens.
MILESTONE VAULT