Before You Start
- Connect a BCH wallet that can sign FlowGuard transactions
- Decide whether you are launching from a personal workflow or a treasury / vault workflow
- Choose the asset type: BCH or CashTokens
- Choose the schedule family you actually need
Supported Stream Families
| Family | Best for | Key inputs |
|---|---|---|
LINEAR | Simple continuous vesting | total amount, start, end, optional cliff |
HYBRID | Upfront unlock plus linear tail | total amount, start, end, unlock checkpoint, upfront percentage |
RECURRING | Payroll and retainers | total amount, cadence, duration, optional refillable runway |
STEP | Equal milestone unlocks | total amount, cadence, duration, optional cliff |
TRANCHE | Custom staged unlocks | total amount, custom checkpoint schedule |
Flow in the App
Open the builder
Navigate to Streams -> Create Stream for personal workflows, or launch from a vault or DAO treasury stream view for organization workflows.
Choose a template or family
Use the shape gallery if you want a guided starting point. Templates load real schedule parameters into the builder, including linear + cliff, hybrid, recurring runway, milestone cadence, and custom tranche plans.
Set the schedule
Configure the fields required by the chosen family:
- LINEAR: start, end, optional cliff
- HYBRID: start, end, unlock checkpoint, upfront percentage
- RECURRING: start, end, interval seconds, optional refillable toggle
- STEP: start, end, milestone cadence
- TRANCHE: custom unlock checkpoints and percentages
Review the preview
The builder shows a contract-truthful schedule preview. This preview changes when you change cadence, cliff, unlock timing, or tranche geometry.
Create the stream record
Click Create Stream. The app calls
POST /api/streams/create, stores the stream in PENDING, and returns the contract address and funding requirements.Example Request
Notes by Family
Recurring
intervalSecondsis required- the interval must divide the schedule duration evenly
refillableis only valid for recurring streams
Tranche
- the tranche schedule must be bounded and internally valid
- the app and backend normalize tranche schedules before deployment
- the first unlock checkpoint becomes the effective first claimable event
Hybrid
- the upfront unlock time must be after
startTimeand beforeendTime - the upfront percentage must be greater than
0and less than100
After Creation
Once active, the stream detail page becomes the operational surface for:- claim
- pause / resume
- refill for recurring runway streams
- transfer recipient rights for transferable non-recurring streams
- cancellation where allowed

