ritual-dapp-scheduler

Scheduled Operations — Ritual dApp Patterns

Overview

The Scheduler contract (0x56e776BAE2DD60664b69Bd5F865F1180ffB7D58B) enables time-delayed and recurring execution of on-chain calls. Any contract call can be scheduled to run at a future block, repeat at fixed intervals, or execute as a one-shot delayed action. The Scheduler works with all precompiles — synchronous (ONNX, JQ, Ed25519, SECP256R1) and async (HTTP, LLM, Agent, Long-Running HTTP, Image, Audio, Video).

Only contracts can schedule — not EOAs. The Scheduler always calls back msg.sender, so your contract must call schedule() directly.

When a scheduled call triggers an async precompile, the system automatically detects it during simulation, creates a commitment, routes to an executor, and settles. Each recurrence independently triggers a new async lifecycle.

Scheduler: 0x56e776BAE2DD60664b69Bd5F865F1180ffB7D58B RitualWallet: 0x532F0dF0896F353d8C3DD8cc134e8129DA2a3948 Chain ID: 1979

---

Call States

enum CallState {
    SCHEDULED,   // 0 — registered, waiting for trigger block
    EXECUTING,   // 1 — trigger block reached, callback running
    COMPLETED,   // 2 — all executions finished (terminal)
    CANCELLED,   // 3 — user cancelled (terminal)
    EXPIRED      // 4 — overall deadline passed (terminal)
}

For recurring calls, the cycle is: SCHEDULED → EXECUTING → SCHEDULED → EXECUTING → ... → EXECUTING → COMPLETED. The call stays in the SCHEDULED ↔ EXECUTING loop until all numCalls are done, then transitions to COMPLETED.

Individual executions can be skipped (TTL drift exceeded, insufficient funds) without killing the whole schedule. The schedule only dies when it reaches COMPLETED, CANCELLED, or EXPIRED.

Fees are not deducted at schedule time — only at execution time. If a call is cancelled or expires, no fees were ever taken. The balance stays in RitualWallet.

---

Execution Index Injection

The Scheduler overwrites bytes 4-35 of your calldata with the real executionIndex at execution time. Your callback's first parameter (after the 4-byte selector) must be uint256 executionIndex. When encoding the schedule data, put a dummy 0 there:

bytes memory data = abi.encodeWithSelector(
    this.myCallback.selector,
    uint256(0),     // placeholder — Scheduler overwrites with real executionIndex
    myArg
);

---

Scheduler ABI

const SCHEDULER = '0x56e776BAE2DD60664b69Bd5F865F1180ffB7D58B' as const;

const schedulerAbi = [
  {
    name: 'schedule',
    type: 'function',
    stateMutability: 'nonpayable',
    inputs: [
      { name: 'data', type: 'bytes' },
      { name: 'gas', type: 'uint32' },
      { name: 'startBlock', type: 'uint32' },
      { name: 'numCalls', type: 'uint32' },
      { name: 'frequency', type: 'uint32' },
      { name: 'ttl', type: 'uint32' },
      { name: 'maxFeePerGas', type: 'uint256' },
      { name: 'maxPriorityFeePerGas', type: 'uint256' },
      { name: 'value', type: 'uint256' },
      { name: 'payer', type: 'address' },
    ],
    outputs: [{ type: 'uint256' }],
  },
  {
    name: 'schedule',
    type: 'function',
    stateMutability: 'nonpayable',
    inputs: [
      { name: 'data', type: 'bytes' },
      { name: 'gas', type: 'uint32' },
      { name: 'numCalls', type: 'uint32' },
      { name: 'frequency', type: 'uint32' },
    ],
    outputs: [{ type: 'uint256' }],
  },
  {
    name: 'cancel',
    type: 'function',
    stateMutability: 'nonpayable',
    inputs: [{ name: 'callId', type: 'uint256' }],
    outputs: [],
  },
  {
    name: 'approveScheduler',
    type: 'function',
    stateMutability: 'nonpayable',
    inputs: [{ name: 'schedulerContract', type: 'address' }],
    outputs: [],
  },
  {
    name: 'calls',
    type: 'function',
    stateMutability: 'view',
    inputs: [{ name: 'callId', type: 'uint256' }],
    outputs: [
      { name: 'to', type: 'address' },
      { name: 'caller', type: 'address' },
      { name: 'startBlock', type: 'uint32' },
      { name: 'numCalls', type: 'uint32' },
      { name: 'frequency', type: 'uint32' },
      { name: 'gas', type: 'uint32' },
      { name: 'ttl', type: 'uint32' },
      { name: 'state', type: 'uint8' },
      { name: 'maxFeePerGas', type: 'uint256' },
      { name: 'maxPriorityFeePerGas', type: 'uint256' },
      { name: 'value', type: 'uint256' },
      { name: 'data', type: 'bytes' },
    ],
  },
  {
    name: 'getCallState',
    type: 'function',
    stateMutability: 'view',
    inputs: [{ name: 'callId', type: 'uint256' }],
    outputs: [{ name: 'state', type: 'uint8' }],
  },
] as const;

The 4-param minimal overload auto-sets: startBlock = block.number + frequency, ttl = 0, maxFeePerGas = block.basefee, maxPriorityFeePerGas = 0, value = 0, payer = msg.sender.

---

TypeScript: Schedule a Single Delayed Execution

import {
  createPublicClient, createWalletClient, defineChain, http,
  encodeFunctionData,
} from 'viem';
import { privateKeyToAccount } from 'viem/accounts';

const ritualChain = defineChain({
  id: 1979,
  name: 'Ritual Chain',
  nativeCurrency: { name: 'RITUAL', symbol: 'RITUAL', decimals: 18 },
  rpcUrls: { default: { http: [process.env.RITUAL_RPC_URL!] } },
});

const account = privateKeyToAccount(process.env.PRIVATE_KEY! as `0x${string}`);
const publicClient = createPublicClient({ chain: ritualChain, transport: http() });
const walletClient = createWalletClient({ account, chain: ritualChain, transport: http() });

const currentBlock = await publicClient.getBlockNumber();
const gasPrice = await publicClient.getGasPrice();

const callData = encodeFunctionData({
  abi: myContractAbi,
  functionName: 'myCallback',
  args: [0n, myArg], // 0 = dummy executionIndex, Scheduler overwrites it
});

const hash = await walletClient.writeContract({
  address: SCHEDULER,
  abi: schedulerAbi,
  functionName: 'schedule',
  args: [
    callData,
    300_000,                            // gas
    Number(currentBlock) + 150,         // startBlock
    1,                                  // numCalls
    1,                                  // frequency
    100,                                // ttl
    gasPrice,                           // maxFeePerGas
    0n,                                 // maxPriorityFeePerGas
    0n,                                 // value per call
    account.address,                    // payer
  ],
});

TypeScript: Schedule Recurring Execution

const hash = await walletClient.writeContract({
  address: SCHEDULER,
  abi: schedulerAbi,
  functionName: 'schedule',
  args: [
    callData,
    300_000,                            // gas
    Number(currentBlock) + 150,         // startBlock
    24,                                 // numCalls — 24 total
    50,                                 // frequency — every 50 blocks (~17.5s at ~350ms baseline)
    200,                                // ttl
    gasPrice,
    0n,
    0n,
    account.address,
  ],
});

TypeScript: Query and Monitor

const callInfo = await publicClient.readContract({
  address: SCHEDULER,
  abi: schedulerAbi,
  functionName: 'calls',
  args: [callId],
});

// State enum: 0=SCHEDULED, 1=EXECUTING, 2=COMPLETED, 3=CANCELLED, 4=EXPIRED
console.log('State:', callInfo.state);

const state = await publicClient.readContract({
  address: SCHEDULER,
  abi: schedulerAbi,
  functionName: 'getCallState',
  args: [callId],
});

// Terminal states: 2 (COMPLETED), 3 (CANCELLED), 4 (EXPIRED)
if (state >= 2) {
  console.log('Schedule is done');
}

---

Solidity: ScheduledConsumer Contract

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

interface IRitualWallet {
    function deposit(uint256 lockDuration) external payable;
}

interface IScheduler {
    function schedule(
        bytes calldata data,
        uint32 gas,
        uint32 startBlock,
        uint32 numCalls,
        uint32 frequency,
        uint32 ttl,
        uint256 maxFeePerGas,
        uint256 maxPriorityFeePerGas,
        uint256 value,
        address payer
    ) external returns (uint256 callId);

    function cancel(uint256 callId) external;
    function approveScheduler(address schedulerContract) external;
}

contract ScheduledJQConsumer {
    address constant JQ_PRECOMPILE = 0x0000000000000000000000000000000000000803;
    address constant RITUAL_WALLET = 0x532F0dF0896F353d8C3DD8cc134e8129DA2a3948;
    IScheduler public immutable scheduler;

    address public owner;
    uint256 public activeScheduleId;
    uint256 public executionCount;
    bytes public lastResult;

    event Scheduled(uint256 indexed callId, uint256 frequency, uint256 numCalls);
    event Executed(uint256 indexed executionIndex, bytes result);

    modifier onlyOwner() {
        require(msg.sender == owner, "Not owner");
        _;
    }

    modifier onlyScheduler() {
        require(msg.sender == address(scheduler), "unauthorized");
        _;
    }

    constructor(address _scheduler) {
        owner = msg.sender;
        scheduler = IScheduler(_scheduler);
    }

    function depositForFees() external payable {
        IRitualWallet(RITUAL_WALLET).deposit{value: msg.value}(50000);
    }

    function scheduleRecurringTransform(
        string calldata jqFilter,
        bytes calldata inputJson,
        uint32 frequency,
        uint32 numCalls,
        uint32 gasLimit,
        uint256 maxFeePerGas
    ) external onlyOwner {
        bytes memory data = abi.encodeWithSelector(
            this.executeTransform.selector,
            uint256(0),     // dummy executionIndex — Scheduler overwrites
            jqFilter,
            inputJson
        );

        activeScheduleId = scheduler.schedule(
            data,
            gasLimit,
            uint32(block.number) + frequency,
            numCalls,
            frequency,
            100,
            maxFeePerGas,
            0,
            0,
            address(this)
        );

        emit Scheduled(activeScheduleId, frequency, numCalls);
    }

    function executeTransform(
        uint256 executionIndex,
        string calldata jqFilter,
        bytes calldata inputJson
    ) external onlyScheduler {
        bytes memory input = abi.encode(jqFilter, inputJson);
        (bool success, bytes memory result) = JQ_PRECOMPILE.call(input);
        require(success, "JQ precompile call failed");

        lastResult = result;
        executionCount++;
        emit Executed(executionIndex, result);
    }

    function cancelSchedule() external onlyOwner {
        require(activeScheduleId != 0, "No active schedule");
        scheduler.cancel(activeScheduleId);
        activeScheduleId = 0;
    }

    receive() external payable {}
}

---

Scheduler + Async Precompiles

When a scheduled call triggers an async precompile (HTTP 0x0801, LLM 0x0802, etc.), both lifecycles run:

1. Trigger block → TxScheduled (0x10) from 0xfa7e
2. Builder simulates → detects async precompile inside the callback
3. TxAsyncCommitment (0x11) with origin_tx = scheduled_tx_hash
4. Executor processes in TEE
5. Scheduled tx re-executed with async result injected
6. TxAsyncSettlement (0x12) distributes fees
7. If more executions remain, loops back to step 1

Scheduled HTTP Consumer

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

contract ScheduledHTTPConsumer {
    address constant HTTP_PRECOMPILE = 0x0000000000000000000000000000000000000801;
    address constant RITUAL_WALLET = 0x532F0dF0896F353d8C3DD8cc134e8129DA2a3948;
    IScheduler public immutable scheduler;

    address public owner;
    uint256 public activeScheduleId;
    uint256 public executionCount;

    event HTTPCallSubmitted(uint256 indexed executionIndex);

    modifier onlyOwner() { require(msg.sender == owner, "Not owner"); _; }
    modifier onlyScheduler() { require(msg.sender == address(scheduler), "unauthorized"); _; }

    constructor(address _scheduler) {
        owner = msg.sender;
        scheduler = IScheduler(_scheduler);
    }

    function depositForFees() external payable {
        IRitualWallet(RITUAL_WALLET).deposit{value: msg.value}(50000);
    }

    function scheduleRecurringHTTPCall(
        address executor,
        string calldata url,
        uint32 frequency,
        uint32 numCalls,
        uint32 gasLimit,
        uint256 maxFeePerGas
    ) external onlyOwner {
        bytes memory data = abi.encodeWithSelector(
            this.executeHTTPCall.selector,
            uint256(0),     // dummy executionIndex
            executor,
            url
        );

        activeScheduleId = scheduler.schedule(
            data, gasLimit,
            uint32(block.number) + frequency,
            numCalls, frequency, 100,
            maxFeePerGas, 0, 0, address(this)
        );
    }

    function executeHTTPCall(
        uint256 executionIndex,
        address executor,
        string calldata url
    ) external onlyScheduler {
        bytes memory encoded = abi.encode(
            executor,
            new bytes[](0),     // encryptedSecrets
            uint256(50),        // ttl
            new bytes[](0),     // secretSignatures
            bytes(""),          // userPublicKey
            url,
            uint8(1),           // GET
            new string[](0), new string[](0),
            bytes(""),          // body
            uint256(0),         // dkmsKeyIndex
            uint8(0),           // dkmsKeyFormat
            false               // piiEnabled
        );

        (bool ok,) = HTTP_PRECOMPILE.call(encoded);
        require(ok, "HTTP precompile failed");

        executionCount++;
        emit HTTPCallSubmitted(executionIndex);
    }

    function cancelSchedule() external onlyOwner {
        require(activeScheduleId != 0, "No active schedule");
        scheduler.cancel(activeScheduleId);
        activeScheduleId = 0;
    }

    receive() external payable {}
}

Scheduled Long-Running HTTP Consumer

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

contract ScheduledLongRunningConsumer {
    address constant LONG_HTTP = address(0x0805);
    address constant ASYNC_DELIVERY = 0x5A16214fF555848411544b005f7Ac063742f39F6;

    bytes public encodedRequest;
    string public latestResult;

    event JobSubmitted(uint256 blockNumber);
    event JobCompleted(bytes32 indexed jobId, string result);

    function setRequest(bytes calldata _encodedRequest) external {
        encodedRequest = _encodedRequest;
    }

    function executeScheduledJob(uint256 executionIndex) external {
        (bool ok,) = LONG_HTTP.call(encodedRequest);
        require(ok, "Long-running HTTP failed");
        emit JobSubmitted(block.number);
    }

    function onLongRunningResult(bytes32 jobId, bytes calldata result) external {
        require(msg.sender == ASYNC_DELIVERY, "unauthorized callback");
        (bool success, bytes memory data) = abi.decode(result, (bool, bytes));
        if (success) {
            latestResult = abi.decode(data, (string));
            emit JobCompleted(jobId, latestResult);
        }
    }
}

The deliveryTarget and deliverySelector in your long-running HTTP request must point to this contract's onLongRunningResult function. msg.sender in the callback is always ASYNC_DELIVERY (0x5A16214fF555848411544b005f7Ac063742f39F6).

---

Payer Semantics

The payer parameter specifies whose RitualWallet balance is debited at execution time. The payer must be msg.sender or must have approved msg.sender via approveScheduler().

• Contract pays for itself: pass address(this) in Solidity
• EOA pays: pass the wallet address in TypeScript
• Sponsored: a third party calls approveScheduler(yourContract) then you pass their address as payer

---

Fee Management

Cost per execution = (gasLimit × maxFeePerGas) + value
Total deposit needed = cost per execution × numCalls

Fees are deducted from the payer's RitualWallet at execution time, not at schedule time. Unused gas is refunded after each execution. If balance is insufficient at execution time, the execution is skipped (not cancelled) — future executions can still proceed if balance is topped up.

const RITUAL_WALLET = '0x532F0dF0896F353d8C3DD8cc134e8129DA2a3948' as const;

const walletAbi = [
  { name: 'deposit', type: 'function', stateMutability: 'payable',
    inputs: [{ name: 'lockDuration', type: 'uint256' }], outputs: [] },
  { name: 'balanceOf', type: 'function', stateMutability: 'view',
    inputs: [{ name: 'account', type: 'address' }], outputs: [{ type: 'uint256' }] },
] as const;

const maxCostPerExec = gasPrice * 300_000n;
const totalCost = maxCostPerExec * BigInt(numCalls);

const balance = await publicClient.readContract({
  address: RITUAL_WALLET, abi: walletAbi, functionName: 'balanceOf', args: [account.address],
});

if (balance < totalCost) {
  await walletClient.writeContract({
    address: RITUAL_WALLET, abi: walletAbi, functionName: 'deposit',
    args: [50000n], value: totalCost - balance,
  });
}

---

Block Interval Reference

Interval	Blocks (at ~350ms/block, conservative baseline)
1 minute	172
5 minutes	858
15 minutes	2,572
1 hour	10,286
6 hours	61,715
12 hours	123,429
1 day	246,858
1 week	1,728,000

Use ritual-dapp-block-time to recompute these intervals from recent blocks on your target deployment.

---

Predicates

Frequency is a degenerate predicate

Without predicates, frequency = N is itself a predicate — it's equivalent to (block.number - startBlock) % N == 0. A fixed modular arithmetic condition. You know exactly when every call fires.

Predicates generalize this. Instead of a fixed temporal pattern, a predicate can encode any boolean condition: price thresholds, state-dependent logic, cross-contract checks, time-of-day patterns. The schedule becomes event-driven rather than time-driven.

To unlock this: set frequency = 1 and use numCalls as a budget. With frequency = 1, the schedule is eligible every block. The predicate is the sole gatekeeper. numCalls controls how many times the predicate is allowed to trigger before the schedule is exhausted.

frequency = N, no predicate  → fixed temporal pattern (fire every N blocks, N times)
frequency = 1, predicate     → arbitrary condition checked every block, numCalls = budget
frequency = N, predicate     → arbitrary condition sampled every N blocks (cheaper but slower)

Interface

interface IScheduledPredicate {
    function shouldExecute(
        address caller,
        uint256 callId,
        uint256 executionIndex
    ) external view returns (bool);
}

Predicates are called via staticcall — they cannot modify state. The block builder allocates up to 100,000 gas per predicate evaluation and 10,000,000 gas total per block for all predicate evaluations.

If a predicate reverts or runs out of gas, the scheduled transaction is skipped for that block (same as returning false).

Where Predicates Apply in the Lifecycle

For synchronous scheduled calls (ONNX, JQ, Ed25519): the predicate gates whether the entire execution happens.

For async scheduled calls (HTTP, LLM, Agent): the predicate gates whether Phase 1 (the commitment) happens. Once triggered, the commitment → executor → settlement lifecycle is autonomous. The predicate is NOT re-evaluated during settlement or Phase 2 delivery.

Example 1: One-shot sync at exact block

Fire a JQ transform at exactly block 1000 (current block is 0). With frequency = 1, execution index i is expected at startBlock + i. numCalls must cover the gap to the target block.

contract BlockTargetPredicate is IScheduledPredicate {
    uint256 public immutable targetBlock;

    constructor(uint256 _targetBlock) {
        targetBlock = _targetBlock;
    }

    function shouldExecute(address, uint256, uint256) external view returns (bool) {
        return block.number == targetBlock;
    }
}

uint256 callId = scheduler.schedule(
    abi.encodeWithSelector(this.runTransform.selector, uint256(0), filter, input),
    200_000,                    // gas
    uint32(block.number) + 1,   // startBlock = 1
    1000,                       // numCalls — budget covers blocks 1 through 1000
    1,                          // frequency (eligible every block)
    50,                         // ttl
    1 gwei, 0, 0,
    address(this),
    address(blockPredicate)     // fires at block 1000
);

With numCalls = 1, the only execution slot is index 0 at startBlock. If the target block is outside startBlock + scheduler_ttl, the predicate never fires and the schedule expires. numCalls must be large enough to keep the schedule alive until the target.

Block 1 to 999:  predicate returns false each block → nothing happens
Block 1000:      predicate returns true → JQ runs → execution consumed

Example 2: One-shot async at exact block

Same predicate, but callback calls the HTTP precompile. The predicate only gates the trigger — async settlement is autonomous:

uint256 callId = scheduler.schedule(
    abi.encodeWithSelector(this.fetchPrice.selector, uint256(0), executor, url),
    300_000,
    uint32(block.number) + 1,
    1000,                       // numCalls — budget covers blocks 1 through 1000
    1,                          // frequency
    50,                         // scheduler_ttl (must cover async settlement too)
    1 gwei, 0, 0,
    address(this),
    address(blockPredicate)     // fires at block 1000
);

Block 999:  predicate returns false → nothing
Block 1000: predicate returns true  → TxScheduled → callback → HTTP precompile
            → TxAsyncCommitment (predicate NOT re-evaluated)
Block 1002: Executor settles → TxAsyncSettlement (predicate NOT re-evaluated)

Example 3: Recurring conditional — price oracle

Fire an HTTP call every time an oracle reports a price above a threshold. Use frequency = 1 so the predicate is checked every block. Use a large numCalls as the budget.

contract PriceThresholdPredicate is IScheduledPredicate {
    address public immutable oracle;
    uint256 public immutable threshold;

    constructor(address _oracle, uint256 _threshold) {
        oracle = _oracle;
        threshold = _threshold;
    }

    function shouldExecute(address, uint256, uint256) external view returns (bool) {
        (, int256 price,,,) = IAggregator(oracle).latestRoundData();
        return uint256(price) > threshold;
    }
}

uint256 callId = scheduler.schedule(
    abi.encodeWithSelector(this.fetchAndProcess.selector, uint256(0), executor, url),
    300_000,
    uint32(block.number) + 1,
    10000,                      // numCalls (budget: up to 10,000 triggers)
    1,                          // frequency = 1 (check every block)
    50,                         // ttl
    1 gwei, 0, 0,
    address(this),
    address(pricePredicate)
);

Why frequency = 1 and not frequency = 300?

• frequency = 1, numCalls = 10000: predicate checked every block. If the price crosses at block N, the call fires at block N. Maximum responsiveness.
• frequency = 300, numCalls = 33: predicate only checked every 300 blocks, and the budget is much smaller because frequency × numCalls must stay under MAX_LIFESPAN. If the price crosses at block N, the call won't fire until the next multiple of 300. Up to ~1.75 minutes delay at the ~350ms baseline.

The tradeoff is builder overhead: frequency = 1 means the builder evaluates the predicate every block (up to 100K gas per evaluation, subsidized by the proposer). For high-frequency conditions, frequency = 1 is the right choice. For expensive predicates or when latency tolerance is acceptable, a higher frequency reduces builder cost.

Why numCalls must be large for predicates

With numCalls = 1, the schedule is COMPLETED after the first trigger. If your predicate fires at block 500,000, you're done — no more triggers even if the condition is met again at block 500,100.

With numCalls = 10000, the predicate can trigger up to 10,000 times across the schedule's lifetime. Each trigger consumes one unit of budget. When the budget is exhausted, the schedule transitions to COMPLETED.

numCalls with a predicate is a budget cap, not a scheduling parameter. Set it high enough to cover your expected trigger frequency over the schedule's lifetime while keeping frequency × numCalls <= 10,000.

---

Scheduled Async: The Scheduler TTL Is the Binding Constraint

When a scheduled callback calls an async precompile, there are two TTLs — but the scheduler TTL is the one that kills you.

When the async result comes back, the builder replays the original TxScheduled. This runs Scheduler.execute() on-chain. Inside execute(), the TTL check runs:

uint32 executionExpiryBlock = expectedBlock + call.ttl;
if (uint32(block.number) > executionExpiryBlock) {
    emit CallSkippedTTLExpired(...);
    return; // callback never runs, precompile never called, async result never consumed
}

If the scheduler TTL has passed by the time the settlement replay happens, the callback never fires, the async result is never consumed, and the settlement is invalid. The builder won't include it.

This means: the scheduler TTL must cover the ENTIRE async lifecycle — from trigger to settlement replay. It's not just "drift tolerance for when the callback first fires." The replayed TxScheduled must also pass the TTL check.

The two TTLs

• Scheduler TTL — expectedBlock + scheduler_ttl is the deadline for the replayed TxScheduled to execute. Both the initial trigger AND the settlement replay must happen within this window.
• Async TTL — commit_block + async_ttl is the deadline for the executor to submit results. If this expires, the async job is cleaned up.

The effective deadline is: min(expectedBlock + scheduler_ttl, commit_block + async_ttl)

Since commit_block ≈ expectedBlock (commitment happens in the same block or shortly after the trigger), the binding constraint is usually whichever TTL is smaller.

Why scheduler_ttl = 3 with a 9-block operation fails

Block 1: Expected execution block. scheduler_ttl=3, async_ttl=10.
Block 1: Scheduler fires. Commitment created. Async expiry = 1 + 10 = 11.
          Scheduler deadline = 1 + 3 = 4.
Block 10: Executor ready to settle (operation took 9 blocks).
           Builder tries to replay TxScheduled at block 10.
           Scheduler.execute() checks: block.number (10) > expectedBlock + ttl (1 + 3 = 4).
           → CallSkippedTTLExpired. Callback never runs. Settlement invalid.
❌ The async TTL (11) hasn't expired, but the scheduler TTL (4) has.
   The scheduler TTL is the binding constraint.

The fix: scheduler_ttl >= expected_async_settlement_time. If the HTTP call takes up to 9 blocks, set scheduler_ttl to at least 15-20 to be safe.

Sender lock behavior

Scheduled transactions bypass the sender lock entirely. The async pool code explicitly exempts them from is_sender_locked() and does not insert them into sender_index. Multiple scheduled async jobs from the same caller CAN be in-flight simultaneously. The only constraint is per-block deduplication (seen_senders) — one async commitment per caller per block building cycle.

Scenario 1: Happy path

scheduler_ttl=50, async_ttl=100. Operation takes 3 blocks.

Block 1000: Expected. Scheduler fires. Commitment created.
Block 1003: Executor settles. Builder replays TxScheduled.
            Scheduler.execute(): block 1003 <= 1000 + 50 ✅
            Async: block 1003 <= 1000 + 100 ✅
✅ Both TTLs satisfied. Result delivered.

Scenario 2: Scheduler TTL expires before settlement

scheduler_ttl=10, async_ttl=100. Operation takes 15 blocks.

Block 1000: Scheduler fires. Commitment created.
Block 1015: Executor ready. Builder tries to replay TxScheduled.
            Scheduler.execute(): block 1015 > 1000 + 10 = 1010 ❌
            → CallSkippedTTLExpired. Settlement invalid.
❌ Async TTL (1100) is fine, but scheduler TTL (1010) is blown.
   Fix: increase scheduler_ttl to cover the async settlement time.

Scenario 3: Async TTL expires (scheduler is fine)

scheduler_ttl=100, async_ttl=5. Operation takes 10 blocks.

Block 1000: Scheduler fires. Commitment created. Async expiry = 1005.
Block 1010: Executor ready, but async TTL expired at block 1005.
            Job cleaned up by AsyncJobTracker. No result to settle.
❌ Scheduler TTL (1100) is fine, but async job expired.
   Fix: increase async_ttl in your abi.encode.

Scenario 4: Scheduler fires late, tight window

scheduler_ttl=50, async_ttl=100. Operation takes 3 blocks.

Block 1000: Expected execution block.
Block 1048: Scheduler fires (late, within TTL). Commitment created.
            Scheduler deadline still = 1000 + 50 = 1050.
            Only 2 blocks left for settlement!
Block 1051: Executor settles. Block 1051 > 1050. ❌ Too late.
❌ The scheduler fired late, leaving no room for async settlement.
   Fix: scheduler_ttl must cover BOTH drift AND settlement time.

This is the critical insight: scheduler_ttl isn't just drift tolerance. It's max_drift + max_settlement_time.

Scenario 5: Wallet insufficient

Block 1000: Builder simulates, detects async precompile.
            Wallet balance check (at parent state) → insufficient.
            Marked InvalidAsync. TxScheduled silently dropped by builder.
            Execution index NOT marked as executed. Retries next eligible block.
❌ No fees charged. Scheduler keeps trying until per-execution TTL expires.

Scenario 6: Recurring — no cascade blocking

frequency=100, scheduler_ttl=50, async_ttl=100.

Block 1000: Execution 0 fires. Commitment. (Caller NOT locked — exempt)
Block 1003: Execution 0 settles within scheduler TTL. ✅
Block 1100: Execution 1 fires. Independent commitment.
Block 1103: Execution 1 settles. ✅

Even if execution 0 hasn't settled when execution 1 fires, both can have in-flight commitments because scheduled txs bypass the sender lock.

Scenario 7: Long-running (2-phase) — scheduler TTL only constrains Phase 1

For long-running (2-phase) precompiles, the TxScheduled is replayed during Phase 1 settlement, not Phase 2 delivery. Phase 2 delivery is a separate system tx (AsyncDelivery.deliver()) that doesn't go through Scheduler.execute().

scheduler_ttl=50, async_ttl=100, max_poll_block=5000.

Block 1000: Scheduler fires. Phase 1 commitment.
Block 1003: Phase 1 settlement. Builder replays TxScheduled.
            Scheduler.execute(): 1003 <= 1000 + 50 ✅ (scheduler TTL OK)
            Phase 1 settles. Sender lock released.
Block 6003: Phase 2 delivery arrives (within max_poll_block).
            AsyncDelivery.deliver() calls your callback.
            This does NOT go through Scheduler.execute() — no scheduler TTL check.
✅ Scheduler TTL only constrains Phase 1. Phase 2 has its own deadline.

So for long-running precompiles:

• Phase 1 deadline: expectedBlock + scheduler_ttl (scheduler is binding)
• Phase 2 deadline: phase1_settlement_block + max_poll_block (independent of scheduler)

Summary

Scenario	Binding Constraint	Outcome
scheduler_ttl > settlement time	Async TTL	Works if async_ttl is also sufficient
scheduler_ttl < settlement time	Scheduler TTL	Settlement fails — CallSkippedTTLExpired
Late trigger + tight scheduler_ttl	Scheduler TTL	Drift eats into settlement window
Wallet insufficient	Builder filter	Silent drop, retries until TTL
Recurring	Per-execution independent	No cascade (sender lock exempt)
Long-running Phase 1	Scheduler TTL	Phase 1 must settle within scheduler TTL
Long-running Phase 2	max_poll_block	Independent of scheduler TTL

How to size your TTLs

scheduler_ttl >= max_expected_drift + max_expected_settlement_blocks

async_ttl >= max_expected_settlement_blocks

For safety:
  scheduler_ttl = 2 × (max_expected_drift + max_expected_settlement_blocks)
  async_ttl = 2 × max_expected_settlement_blocks

For long-running precompiles, the scheduler TTL only needs to cover Phase 1 settlement (typically fast — a few blocks). Phase 2 is governed by max_poll_block independently.

Deposit sizing

You don't need to lock up funds for all executions upfront. Fees are deducted per-execution at execution time. You can top up your RitualWallet balance between executions with just-in-time deposits — as long as the balance is sufficient when each execution fires.

---

Deterministic TxScheduled Hash Derivation (RPC-Only)

When users ask "what are the transaction hashes for the scheduled executions?", they usually mean the downstream TxScheduled hashes (type=0x10) generated from the schedule-submission transaction.

For one schedule flow, there are multiple related hashes:

• Schedule-submission tx hash — the original user transaction that called Scheduler.schedule(...)
• Scheduled tx hash — deterministic hash for each execution index (executionIndex = 0..numCalls-1)
• Commitment tx hash — async commitment transaction (type=0x11) when the scheduled callback triggers an async precompile
• Settlement tx hash — async settlement transaction (type=0x12) after executor processing

Use the embedded utility from: agents/debugger-reference/scheduled-async-rpc-runbook.md (see "Embedded Utility A").

python3 /tmp/scheduled_txs.py \
  --hash <SCHEDULE_SUBMISSION_TX_HASH> \
  --rpc-url https://rpc.ritualfoundation.org

Example output:

source_tx=0x...
events_found=1

call[0] id=7 caller=0x... start=123456 num_calls=3 frequency=20 ttl=100
  index=  0 block=    123456 scheduled_hash=0x...
  index=  1 block=    123476 scheduled_hash=0x...
  index=  2 block=    123496 scheduled_hash=0x...

Notes:

• The embedded utility decodes Scheduler CallScheduled events from the origin receipt.
• It reconstructs each TxScheduled hash using canonical scheduled-transaction signing fields.
• This gives deterministic expected hashes before you search for commitment/settlement transactions.
• It uses cast keccak for hashing, so Foundry cast must be installed.

---

Quick Reference

Item	Value
Scheduler	0x56e776BAE2DD60664b69Bd5F865F1180ffB7D58B
RitualWallet	0x532F0dF0896F353d8C3DD8cc134e8129DA2a3948
System account	0xfa7e — triggers execution during block building
Chain ID	1979
CallState enum	0=SCHEDULED, 1=EXECUTING, 2=COMPLETED, 3=CANCELLED, 4=EXPIRED
Terminal states	COMPLETED (2), CANCELLED (3), EXPIRED (4)
Fee model	(gasLimit × maxFeePerGas) + value per execution × numCalls
Recurring	numCalls > 1, frequency >= 1
Single-shot	numCalls = 1, frequency = 1
Execution index	Scheduler overwrites bytes 4-35 of calldata with real index
Only contracts	EOAs cannot call schedule()
Max async calls	One async precompile call per scheduled execution
MAX_TTL	500 (deployment-immutable)
MAX_LIFESPAN	10,000 blocks — frequency × numCalls must not exceed this. Reverts ScheduleLifespanExceeded().