Skip to main content
Some FlowGuard contract paths are permissionless, which means anyone can submit the valid transaction once the timing condition is satisfied. The executor layer is the optional infrastructure that watches for those moments and broadcasts the transaction.

​
Why an Executor Exists

Bitcoin Cash uses a UTXO model. Contracts do not wake up on their own. A valid transaction still needs to be constructed and broadcast by some external actor. That is where an executor helps:
  • watch for due recurring payout windows
  • watch for expired proposal windows
  • submit valid permissionless transitions

​
Current Status

FlowGuard does not run a shared executor service today. Recipients of recurring payments and vesting schedules claim manually through the UI. All covenant paths that support permissionless execution are reachable directly from the app or by constructing the transaction yourself.

​
Trust Boundary

An executor cannot redirect funds or change the contract rules. It can only submit transactions the covenant already allows. If the executor service is absent or broken, claims still happen through manual UI flows or direct contract calls.

​
Self-Hosting

If you want automated triggering for your own schedules, you can run your own executor. The covenants on chain do not require permission from FlowGuard to interact with them. Any software that can construct a valid BCH transaction and broadcast it to mainnet can serve as an executor. Executor development for the hosted FlowGuard stack is on the v1.1 roadmap.