Automation/The workflows
The workflows
Every KeeperHub workflow that runs Cadence, one by one.
Core circle lifecycle#
| Workflow | Trigger | What it does |
|---|---|---|
| Cadence Payout Execution | Schedule | Reads round state across every circle; the moment a round is fully funded and its deadline has passed, executes the payout to that round's recipient. |
| Cadence Default Detection + Deposit Draw | Schedule | Walks every circle, then every member of each circle, checking for missed contributions past deadline. Auto-covers what it can from the member's own deposit; flags what it can't. |
| Cadence Completion → Reputation Update | Event (CircleCompleted) | Writes each member's outcome to the ERC-8004 reputation registry the moment a circle completes, then posts the milestone to Discord. |
Member-initiated actions#
| Workflow | Trigger | What it does |
|---|---|---|
| Cadence Meta-Transaction Relay | Webhook | Re-verifies an already-signed EIP-712 request onchain via CadenceForwarder.verify(), then submits execute() — paying gas so the member never has to. Details in Gasless meta-transactions. |
| Cadence New Member Gas Drip | Webhook | Sends a small, fixed amount of Base Sepolia ETH to a wallet the first time it connects — enough for the one step sponsorship can't cover. Details in Starter gas for new members. |
Monitoring & notifications#
| Workflow | Trigger | What it does |
|---|---|---|
| Cadence New Circle Announcement | Event | Posts to Discord whenever a new circle is created. |
| Cadence Stuck Circle Watchdog | Schedule (daily) | Flags circles still Forming past a reasonable window, so a stalled circle doesn't just sit silently. |
| Cadence Contribution Reminders | Schedule (every 30 min) | Posts upcoming contribution deadlines to Discord — see the note in Activity & notifications. |
| Cadence Relayer Wallet Balance Monitor | Schedule (every 6h) | Watches the shared KeeperHub wallet's ETH balance and alerts before it runs low — the same wallet funds both the relay and the gas drip. |
The pattern behind all of them#
Each workflow does exactly one job. Reading round state is separate from executing a payout; detecting a default is separate from covering it; verifying a signature is separate from submitting it onchain. Nothing runs inside a monolithic script — every step is its own node, in a workflow with a name, so a failure or a fix is traceable to one specific, inspectable place.