Automation/Why KeeperHub
Why KeeperHub
Every autonomous action in Cadence traces to a nameable, independently inspectable KeeperHub workflow.
The thesis#
Rotating savings circles have always needed someone trusted to hold the pot and enforce the rotation. Cadence's answer isn't a backend agent making silent decisions — it's a set of KeeperHub workflows, each with a name, a trigger you can read, and a transaction trail you can verify. There is no code running Cadence's automation that isn't also a workflow you could open in KeeperHub right now and inspect.
One managed wallet, every autonomous action#
Every workflow that moves funds or submits a transaction signs from the same KeeperHub-managed wallet — 0x48Ee7A940c3b08A23D1d5c2BE9236d67f5b7Ba21 — backed by Turnkey's hardware secure enclaves. Payouts, default coverage, reputation writes, the meta-transaction relay, and the new-member gas drip all trace to the same address, watched by its own balance-monitor workflow.