Roadmap

FlowGuard already ships real BCH-native treasury, stream, distribution, and governance flows. The roadmap below focuses on deepening those products, closing current operating gaps, and making the system easier for organizations to run at scale.

​

Near-Term Priorities

​

Treasury operations

• complete treasury policy enforcement across vault, proposal, and stream workflows
• strengthen treasury activity review, exports, and operational reporting
• improve organization workspace handoff into shared create and execution flows

​

Streams and payroll

• expand stream history, batch history, and audit views
• improve recurring payroll controls and treasury-linked operating views
• document and expose the full supported stream family set clearly across product and docs

​

Governance operations

• improve proposal templates for treasury payouts, grants, and budget motions
• connect proposal review to downstream treasury execution and audit traces
• strengthen role-aware governance workflows in the organization workspace

​

Protocol Expansion

​

Additional schedule families

• broader contract-backed schedule families beyond the current linear, hybrid, recurring, milestone, and bounded tranche set
• richer treasury-controlled stream operations where they improve the BCH covenant model without hiding state transitions

​

Distribution and treasury scale

• larger and more operationally friendly distribution sets
• better batch execution paths across treasury-linked covenant families
• stronger multi-asset treasury handling for BCH and CashTokens

​

Contract verification and tooling

• continue expanding current artifact-based contract verification
• add more scripted live-smoke coverage for networked test environments
• improve developer-facing tooling around deployment, auditability, and integration

​

Product Infrastructure

​

API and indexing

• stronger server-side filtering and pagination across high-volume treasury and stream feeds
• better organization-scoped history surfaces and exportable audit views
• more stable developer-facing interfaces for integrations and internal tooling

​

Operator tooling

• richer alerts for treasury movements, stream changes, and proposal state transitions
• cleaner operator dashboards for roles, activity, and execution readiness
• more complete operational views for batch history and stream lifecycle monitoring

​

Longer-Term Research

These items remain research-heavy and should only move forward when the BCH covenant model and product need are both clear:

• privacy-preserving treasury and payroll disclosures
• oracle-aware accounting or denomination layers where they materially improve treasury operations
• more advanced custom schedule modeling beyond the current bounded-tranche approach