ritual-dapp-longrunning

Submit long-running HTTP requests via precompile 0x0805 with taskId-based delivery.

62|56|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/ritual-foundation/ritual-dapp-skills --skill ritual-dapp-longrunning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ritual-dapp-longrunning
Source: https://github.com/ritual-foundation/ritual-dapp-skills/tree/main/skills/ritual-dapp-longrunning
Command: npx skills add https://github.com/ritual-foundation/ritual-dapp-skills --skill ritual-dapp-longrunning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running HTTP precompile enables on-chain dApps to initiate external API calls that take minutes or hours by using a two-phase pattern: Phase 1 submits the request and returns a taskId, Phase 2 delivers the result after off-chain processing.

Core Features & Use Cases

  • Two-phase HTTP precompile (0x0805) for on-chain submissions with off-chain polling and final delivery.
  • Configurable polling and delivery parameters, including taskId extraction with JQ, and support for DKMS and PII options.
  • Use Case: Execute long-running data analysis or AI-driven results for on-chain contracts while maintaining trustless delivery.

Quick Start

Submit a long-running HTTP configuration to precompile 0x0805 from your dApp and implement the onLongRunningResult callback to handle the delivered result.

Frequently Asked Questions about ritual-dapp-longrunning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I call long-running HTTP APIs from an on-chain dApp?

Long-running HTTP precompiles use a two-phase submit-poll-deliver workflow. Your dApp submits an HTTP request configuration to precompile 0x0805, receives a taskId, and off-chain processors poll the external API until results are delivered back on-chain.

How does on-chain polling work for external API requests that take hours?

On-chain polling for external API requests uses a taskId-based coordination mechanism with configurable polling parameters and block-based deadlines. The precompile enforces wallet funding and supports JQ-based data extraction to filter and format the delivered HTTP results.

Can I execute AI-driven data analysis and deliver results to smart contracts?

Yes, you can execute AI-driven data analysis and deliver results to smart contracts by submitting the analysis request through the long-running HTTP precompile. The trustless delivery mechanism ensures external API results are finalized on-chain via your implemented callback.

Does the long-running HTTP precompile support data extraction and privacy controls?

The long-running HTTP precompile supports JQ-based data extraction for filtering API responses and includes configurable DKMS and PII options. These controls allow you to manage sensitive data delivery directly within the on-chain submission parameters.

What are the limitations of using block-based deadlines for async HTTP calls?

Block-based deadlines for async HTTP calls require sufficient wallet funding and valid polling configurations to prevent task expiration. If the external API processing exceeds the block deadline, the two-phase precompile will not deliver the off-chain result on-chain.