fixed schedule transactions

Author: kaustubh76

scheduledtransactions-scaffold/.DS_Store

@@ -0,0 +1,102 @@
+---
+alwaysApply: true
+---
+
+# Cursor Agent Rules
+
+These rules guide AI agents to generate correct, safe Cadence transactions using Scheduled Transactions.
+
+## Required flow-cli version
+
+Required: flow-cli 2.7.2 (scheduled transactions support)
+
+- Verify:
+
+```bash
+flow version
+```
+
+- If your version is older than 2.7.2, update before proceeding:
+
+```bash
+# macOS (Homebrew)
+brew update && brew upgrade flow-cli
+
+# Or reinstall per docs
+# https://developers.flow.com/tools/flow-cli/install
+```
+
+Proceed only when `flow version` reports 2.7.2.
+
+## Imports
+
+Always use string imports:
+
+```cadence
+import "FungibleToken"
+import "FlowTransactionScheduler"
+```
+
+## Required Params (Scheduled Transactions)
+
+- `timestamp: UFix64` (0 for immediate execution)
+- `priority: UInt8` (0=High, 1=Medium, 2=Low)
+- `executionEffort: UInt64` (minimum 10)
+- `handlerStoragePath: StoragePath`
+- `transactionData: AnyStruct?` (max 100 bytes)
+
+## Transaction Skeleton (Scheduled Transactions)
+
+- Prepare:
+  - Convert priority number to `FlowTransactionScheduler.Priority` enum.
+  - Validate timestamp (future or 0 for immediate).
+  - Estimate fees with `FlowTransactionScheduler.estimate()`.
+  - Withdraw fees from user's FlowToken vault.
+- Issue handler capability: `Capability<auth(FlowTransactionScheduler.Execute) &{FlowTransactionScheduler.TransactionHandler}>`.
+- Execute:
+  - Call `FlowTransactionScheduler.schedule()` with all parameters.
+  - Optionally save `ScheduledTransaction` receipt for future reference/cancellation.
+- Post:
+  - Verify transaction scheduled successfully (check events or receipt ID).
+
+## Prompt-to-Params Examples
+
+- "Schedule transaction to execute in 1 hour with high priority" →
+
+  - `timestamp = getCurrentBlock().timestamp + 3600.0`
+  - `priority = 0` (High)
+  - `executionEffort = 1000` (moderate effort)
+  - `handlerStoragePath` from user specification
+  - `transactionData = nil` unless user provides specific data.
+
+- "Schedule recurring payments every day for a week" →
+  - Multiple transaction transactions with `timestamp` incremented by 86400.0 (1 day)
+  - `priority = 1` (Medium) for cost efficiency
+  - `transactionData` containing payment details.
+
+## Code Style
+
+- Use named arguments.
+- Prefer early returns and minimal nesting inside connector implementations (transactions use assertions instead).
+
+## Sanity Checklist
+
+- Imports present and string-based.
+- Capability issuance and borrows succeed or `panic` with context.
+- For scheduled transactions: fee estimation before scheduling, timestamp validation, handler capability verification.
+- For recurring transactions: consider fee accumulation and batch scheduling efficiency.
+
+## Development Guidelines
+
+- Use string imports: `import "FlowTransactionScheduler"`, `import "FlowToken"`, `import "FungibleToken"`
+- Emulator only; start with: `flow emulator`
+- Estimate before schedule: `FlowTransactionScheduler.estimate(...)`
+- Issue handler capability with correct entitlement: `auth(FlowTransactionScheduler.Execute) &{FlowTransactionScheduler.TransactionHandler}`
+- Save `ScheduledTransaction` if you will need to cancel later; call `FlowTransactionScheduler.cancel(transaction: receipt)` to cancel
+
+## Key Documentation
+
+- **Index**: [`index.md`](./index.md) – Navigation and core contracts reference
+- **Agent Rules**: [`agent-rules.mdc`](./agent-rules.mdc) – Cursor agent guidance for generating transactions
+- **Quick Checklist**: [`quick-checklist.md`](./quick-checklist.md) – Essential implementation checklist
+- **FLIP 330**: [`flip.md`](./flip.md) – Scheduled Transactions specification and details

scheduledtransactions-scaffold/.cursor/rules/scheduledtransactions/agent-rules.mdc

@@ -0,0 +1,18 @@
+# 📘 ScheduledTransactions Documentation Index
+
+> **AI Agent Navigation**: This documentation is structured for optimal crawling and indexing. Each file has a clear purpose and defined scope. Cross-references use consistent anchor linking patterns.
+
+## ⚡ Quick Links
+
+- Scheduled Transactions FLIP: [`flip.md`](./flip.md)
+- Agent Guidance: [`agent-rules.mdc`](./agent-rules.mdc)
+- Checklist: [`quick-checklist.md`](./quick-checklist.md)
+
+## 🛡️ Safety & Implementation
+
+- [`quick-checklist.md`](./quick-checklist.md) – Essential implementation checklist & AI scaffold
+- [`agent-rules.md`](./agent-rules.md) – Cursor agent guidance for generating transactions
+
+## 🛠️ Development Resources
+
+- [`flip.md`](./flip.md) – FLIP 330: Scheduled Transactions specification and implementation details

scheduledtransactions-scaffold/.cursor/rules/scheduledtransactions/flip.md

@@ -0,0 +1,28 @@
+# Quick Checklist
+
+## Imports
+
+- Use `import "ContractName"` format only.
+- Include all required contract imports.
+
+## Preconditions/Postconditions
+
+- Single boolean expression per pre/post block.
+- Use `assert()` for multi-step validation in execute.
+
+## Capabilities & Addresses
+
+- Validate capabilities before use.
+- Pass addresses as parameters only when you must resolve third-party capabilities directly.
+- For scheduled transactions: verify handler capability exists and is properly authorized.
+
+## Test
+
+- Zero amounts and `UFix64.max`
+- Invalid capabilities
+- For scheduled transactions: invalid timestamps (past), insufficient fees, missing handlers
+
+## Links
+
+- Agent Rules: [`agent-rules.mdc`](./agent-rules.mdc)
+- Scheduled Transactions FLIP: [`flip.md`](./flip.md)

scheduledtransactions-scaffold/.cursor/rules/scheduledtransactions/index.md

@@ -0,0 +1,6 @@
+# flow
+emulator-account.pkey
+.env
+
+# Pay attention to imports directory
+!imports/**

scheduledtransactions-scaffold/.cursor/rules/scheduledtransactions/quick-checklist.md

@@ -0,0 +1,4 @@
+# flow
+imports
+.env
+*.pkey

scheduledtransactions-scaffold/.cursorignore

@@ -0,0 +1,3 @@
+{
+    "cadence.customConfigPath": "./flow.json"
+}

scheduledtransactions-scaffold/.gitignore

@@ -0,0 +1,102 @@
+# Scheduled Transactions Demo: Increment the Counter
+
+This example shows how to schedule a transaction that increments the `Counter` in the near future and verify it on the Flow Emulator using the scheduler manager.
+
+## Files used
+
+- `cadence/contracts/Counter.cdc`
+- `cadence/contracts/CounterTransactionHandler.cdc`
+- `cadence/transactions/InitSchedulerManager.cdc`
+- `cadence/transactions/InitCounterTransactionHandler.cdc`
+- `cadence/transactions/ScheduleIncrementIn.cdc`
+- `cadence/scripts/GetCounter.cdc`
+
+## Prerequisites
+
+```bash
+flow deps install
+```
+
+## 1) Start the emulator with Scheduled Transactions
+
+```bash
+flow emulator --block-time 1s
+```
+
+Keep this running. Open a new terminal for the next steps.
+
+## 2) Deploy contracts
+
+```bash
+flow project deploy --network emulator
+```
+
+This deploys `Counter` and `CounterTransactionHandler` (see `flow.json`).
+
+## 3) Initialize the scheduler manager (if not already done)
+
+The scheduler manager is now integrated into the scheduling transactions, so this step is optional. The manager will be created automatically when you schedule your first transaction.
+
+If you want to initialize it separately:
+
+```bash
+flow transactions send cadence/transactions/InitSchedulerManager.cdc \
+  --network emulator \
+  --signer emulator-account
+```
+
+## 4) Initialize the handler capability
+
+Saves a handler resource at `/storage/CounterTransactionHandler` and issues the correct capability for the scheduler.
+
+```bash
+flow transactions send cadence/transactions/InitCounterTransactionHandler.cdc \
+  --network emulator \
+  --signer emulator-account
+```
+
+## 5) Check the initial counter
+
+```bash
+flow scripts execute cadence/scripts/GetCounter.cdc --network emulator
+```
+
+Expected: `Result: 0`
+
+## 6) Schedule an increment in ~2 seconds
+
+Uses `ScheduleIncrementIn.cdc` to compute a future timestamp relative to the current block. This transaction will automatically create the scheduler manager if it doesn't exist.
+
+```bash
+flow transactions send cadence/transactions/ScheduleIncrementIn.cdc \
+  --network emulator \
+  --signer emulator-account \
+  --args-json '[
+    {"type":"UFix64","value":"2.0"},
+    {"type":"UInt8","value":"1"},
+    {"type":"UInt64","value":"1000"},
+    {"type":"Optional","value":null}
+  ]'
+```
+
+Notes:
+
+- Priority `1` = Medium. You can use `0` = High or `2` = Low.
+- `executionEffort` must be >= 10 (1000 is a safe example value).
+- With `--block-time 1s`, blocks seal automatically; after ~3 seconds your scheduled transaction should execute.
+- The transaction uses the scheduler manager to track and manage the scheduled transaction.
+
+## 7) Verify the counter incremented
+
+```bash
+flow scripts execute cadence/scripts/GetCounter.cdc --network emulator
+```
+
+Expected: `Result: 1`
+
+## Troubleshooting
+
+- Invalid timestamp error: use `ScheduleIncrementIn.cdc` with a small delay (e.g., 2.0) so the timestamp is in the future.
+- Missing FlowToken vault: on emulator the default account has a vault; if you use a custom account, initialize it accordingly.
+- Manager not found: The scheduler manager is automatically created in the scheduling transactions. If you see this error, ensure you're using the latest transaction files.
+- More docs: see `/.cursor/rules/scheduledtransactions/index.md`, `agent-rules.mdc`, and `flip.md` in this repo.