The thread has covered one-shot jobs thoroughly. One pattern that seems underexplored: recurring agentic services.
Many real agent workflows aren’t single deliverables - they’re ongoing: weekly reports, continuous monitoring, periodic data feeds. Modeling these as repeated manual job creations puts the renewal burden on the client and breaks automation.
We’re proposing ERC-8191 - Onchain Recurring Payments - which addresses exactly this. It defines a SubscriptionManager (create/cancel/expire lifecycle) and a KeeperRegistry (any permissioned keeper collects payments at each interval, pull-based). No oracles, no custody.
The natural integration with ERC-8183 is the hook system. A hook on fund could automatically open an ERC-8191 subscription - so a recurring agentic relationship becomes a recurring billing relationship by default, without client-side renewal logic.
The inverse is also interesting: an ERC-8191 subscription expiry could trigger an ERC-8183 job rejection, keeping both lifecycle states in sync.
Please check:
- ERC-8191 PR: Add ERC: Onchain Recurring Payments by chasseurmic · Pull Request #1595 · ethereum/ERCs · GitHub
- Discussion: ERC-8191: Onchain Recurring Payments
Happy to sketch a concrete hook interface if useful.