Recurring Crypto Workflow Prompt
Specifies a safe recurring on-chain automation with spend caps, idempotency, failure handling and a kill switch.
/ quick answer
Use before automating anything that signs transactions on a schedule, such as DCA or reward claiming. Specifies a safe recurring on-chain automation with spend caps, idempotency, failure handling and a kill switch.
Specify a recurring on-chain automation. Safety limits are mandatory outputs, not optional. TASK: [what should happen repeatedly] Frequency: [SCHEDULE] Value per run: [AMOUNT] Chain + contracts involved: [DATA] Wallet type available: [EOA / smart account / session key] Produce: 1. Step-by-step execution sequence for one run. 2. Preconditions checked before signing (balance, gas, price sanity, allowlist). 3. Hard limits: per-run cap, daily cap, max runs, allowlisted contracts and tokens. 4. Idempotency design so a retry cannot double-spend. 5. Failure handling per step, including partial failure and stuck transactions. 6. Funding model: how much sits in the executing wallet and for how many runs. 7. Monitoring: what is logged, what triggers an operator alert. 8. Kill switch: exactly how the automation is stopped and authority revoked. 9. The three most likely ways this automation loses money. Assume the automation will fail at some point and design for that.
Run: check gas → check stablecoin balance → quote swap → verify impact under 1% → sign → verify receipt → log. Limits: $200/run, $200/day, 12 runs then halt, one allowlisted router and two tokens. Idempotency: run_id keyed by week; a retry with an existing run_id is a no-op. Funding: 4 runs at a time. Kill switch: revoke the session key and pause the scheduler. Loss paths: bad quote accepted, retry loop, wrong token address in config.
What does the Recurring Crypto Workflow Prompt prompt do?
Use before automating anything that signs transactions on a schedule, such as DCA or reward claiming.
Which AI models work with this prompt?
It is model-agnostic: it works with any capable general model. Replace the bracketed variables with your own context before running it.
What output should I expect?
Run: check gas → check stablecoin balance → quote swap → verify impact under 1% → sign → verify receipt → log. Limits: $200/run, $200/day, 12 runs then halt, one allowlisted router and two tokens. Idempotency: run_id keyed by week; a retry with an existing run_id is a no-op. Funding: 4 runs at a tim.
/ continue exploring
Related concepts
The vocabulary this page depends on.
- →Crypto Automation
Crypto automation is rule-based execution of monitoring, alerting and recurring on-chain actions, so decisions are made once and applied consistently.
- →Web3 Wallet
A Web3 wallet stores your keys and signs transactions, letting you hold assets and connect to on-chain applications without an intermediary.
- →Private Key
A private key is the secret number that authorises transactions from an address; the public address is derived from it, never the reverse.
- →Self-Custody
Self-custody means you control the private keys to your assets, so no company can freeze, lend out or lose them on your behalf.
Related workflows
Turn this into a repeatable process.
- →Automated DCA Workflow
Set a recurring buy schedule that runs without your attention, with sizing and frequency chosen so fees stay negligible.
- →Automated Crypto Alerts
Define the conditions that would change a decision, monitor them automatically, and receive one clean notification instead of watching charts.
- →AI Agent + Web3 Execution
Give an AI agent on-chain capability safely: read freely, propose openly, and sign only inside hard-coded limits.
- →Build a Research Automation Pipeline
Question in, sourced structured brief out — on a schedule.
Related tool stacks
The tools that run it in production.
- →Crypto Automation Stack
Automation platform, data APIs, alerting and optional wallet execution — the operational layer for monitoring and recurring actions.
- →AI Agent + Web3 Stack
Agent framework, MCP/API tools, blockchain data access and a limited signing layer — with policy enforced in code.
Related prompts
Reusable prompts for this job.
- →Build An Alert Workflow Prompt
Designs a complete alerting pipeline — events, sources, thresholds, deduplication and delivery — from a plain description.
- →Portfolio Monitoring Workflow Prompt
Designs a read-only monitoring system across wallets and chains, with exposure limits and drift alerts.
- →Crypto Agent Design Prompt
Specifies an AI crypto agent's tools, permissions, guardrails and evaluation before a single line is written.
- →Browser Automation Task Spec Prompt
Converts a manual click-path into a reliable automation spec.
Related use cases
How people apply it, and what came out.
- →Monitor A Crypto Portfolio
Aggregating six addresses across three chains revealed that a portfolio believed to hold 14 positions actually held one concentrated bet.
- →Automate Repetitive Web3 Actions
Automating reward claims and gas top-ups with session keys and spend caps saved about 5 hours per month with no unbounded authority.
Comparisons & alternatives
Pick between the options.
- →Web2 Apps vs Web3 Apps
Web2 apps authenticate with accounts and store state on private servers; Web3 apps authenticate with a wallet signature and keep state on a public chain.
- →Best AI Workflow Automation Tools: n8n vs Zapier vs Make
The three tools most operators consider for AI workflow automation — compared on pricing, AI integration and technical flexibility.