Skip to main content

​
Current Status

FlowGuard does not run a shared executor service today. The executor scaffold from the early codebase has been removed. Permissionless covenant actions (recurring payment claims, proposal expiry) are triggered manually through the UI or by direct contract call.

​
What Permissionless Means

Covenants like RecurringPaymentCovenant and ProposalCovenant have paths that anyone can call once the timing condition is satisfied. The covenant enforces the rules. FlowGuard does not need to be the one to submit the transaction. This means:
  • Recipients can always claim from the app UI
  • Third-party bots or self-hosted scripts can also trigger permissionless paths
  • FlowGuard servers going offline does not block valid claims

​
Self-Hosted Execution

If you want automated triggering for your own deployment, any software that can construct and broadcast a valid BCH transaction works as an executor. The covenants have no FlowGuard-specific access control.

​
Production Guidance

  • Do not assume autonomous payout execution from a shared FlowGuard service. Manual claim paths are always available.
  • Preserve manual claim and execute paths in your own ops playbooks.
  • A hosted executor network is on the v1.1 roadmap.