القائمة
Block-time estimation and block-to-time conversion guidance for Ritual dApps. Use when setting TTL, lock durations, scheduler frequency, or polling windows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Persistent agent and sovereign agent patterns for Ritual dApps. Use when building dApps with long-lived AI services, sovereign agent jobs, or agent-native product flows on Ritual Chain.
Backend services for Ritual dApps. Use when building event indexers, APIs, job monitors, or webhook services for Ritual applications.
Ritual chain precompile addresses, system contracts, ABI encoding, and callback security. Use when writing Solidity contracts that call Ritual precompiles, handle async callbacks, or interact with the Scheduler and RitualWallet.
Data Availability (storage) patterns for Ritual dApps. Use when any precompile stores or retrieves external data — multimodal outputs, conversation history, agent state, FHE ciphertexts, or artifact files.
Deployment and chain configuration for Ritual dApps. Use when deploying contracts, configuring chain connection, or setting up development environment.
Ritual dApp design system — dark-mode-first color tokens, typography, Tailwind config, async lifecycle state visuals, precompile icons, and AI slop prevention. Use when styling a Ritual Chain frontend, building React/Next.js UI components, implementing async precompile status indicators, or reviewing dApp visual design for brand consistency.
| name | ritual-dapp-block-time |
| description | Block-time estimation and block-to-time conversion guidance for Ritual dApps. Use when setting TTL, lock durations, scheduler frequency, or polling windows. |
Use a conservative planning baseline of ~350ms per block when you do not have fresh measurements from your target deployment.
1 block ~= 0.35s100 blocks ~= 35s300 blocks ~= 105s (~1m45s)500 blocks ~= 175s (~2m55s)5,000 blocks ~= 1,750s (~29m10s)10,000 blocks ~= 3,500s (~58m20s)100,000 blocks ~= 35,000s (~9h43m)70,000 blocks ~= 24,500s (~6h48m)For one day:
blocksPerDay ~= ceil(86,400 / 0.35) = 246,858Before choosing production TTL/lock/scheduler values, estimate block time from recent chain data on your target RPC.
RPC_URL="${RPC_URL:-https://rpc.ritualfoundation.org}"
SAMPLE=60
LATEST=$(cast block-number --rpc-url "$RPC_URL")
OLDER=$((LATEST - SAMPLE))
LATEST_TS=$(cast block "$LATEST" --rpc-url "$RPC_URL" --json | jq -r '.timestamp')
OLDER_TS=$(cast block "$OLDER" --rpc-url "$RPC_URL" --json | jq -r '.timestamp')
uv run --quiet python3 - <<'PY' "$LATEST_TS" "$OLDER_TS" "$SAMPLE"
import sys
latest_ts = int(sys.argv[1], 0)
older_ts = int(sys.argv[2], 0)
sample = int(sys.argv[3])
avg_sec = (latest_ts - older_ts) / sample
print(f"Estimated block time: {avg_sec:.4f}s ({avg_sec*1000:.1f}ms)")
PY
If your measured value is materially different from 350ms, use the measured value in formulas below.
seconds = blocks * blockTimeSeconds
blocks = ceil(seconds / blockTimeSeconds)
Examples at blockTimeSeconds = 0.35:
ceil(3600 / 0.35) = 10,286 blocksceil(86400 / 0.35) = 246,858 blocksceil(900 / 0.35) = 2,572 blocksApply these conversions consistently in:
ttl / maxPollBlock windowsfrequency and interval tables