flare-fdc

Explains Flare Data Connector attestation types, proof workflows, and smart contract verification patterns.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/isreal916/pistis --skill flare-fdc-isreal916
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-fdc
Source: https://github.com/isreal916/pistis/tree/main/.agents/skills/flare-fdc
Command: npx skills add https://github.com/isreal916/pistis --skill flare-fdc-isreal916

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers integrating the Flare Data Connector (FDC) must understand attestation types, verifier and DA Layer APIs, Merkle proof retrieval, and on-chain verification, which are spread across many docs and starter repos. This Skill consolidates that protocol knowledge into one guidance reference. ## Core Features & Use Cases - Attestation Type Reference: Covers EVMTransaction, Web2Json, Payment, AddressValidity, XRPPayment, XRPPaymentNonexistence, and FAssets-oriented types with request/response field details. - End-to-End Workflow Guidance: Documents the prepare → submit → wait for finalization → fetch proof → verify in contract flow, including FdcHub, Relay, and IFdcVerification usage. - Starter Repo Pointers: Maps to canonical Hardhat and Foundry examples such as proof-of-reserves and weather insurance dApps. - Use Case: When writing a Solidity contract that consumes a Web2Json proof, use this Skill to get the correct verification pattern, ABI decoding approach, and security guidance for handling external attestation data. ## Quick Start Ask how to verify an EVMTransaction proof in a Flare smart contract and follow the documented prepare, submit, and verify workflow.

Frequently Asked Questions about flare-fdc

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

FAQPage Schema
How do I verify an FDC attestation proof in a Solidity smart contract?

Resolve IFdcVerification via ContractRegistry.getFdcVerification() and call the type-specific method such as verifyEVMTransaction or verifyWeb2Json with the proof. Always verify first, then decode and use proof.data in your contract logic.

What is the FDC attestation request workflow on Flare?

Prepare the request via a verifier API to get abiEncodedRequest, submit it to FdcHub.requestAttestation with the fee, compute the roundId from the block timestamp, wait for Relay finalization of protocol ID 200, then fetch the Merkle proof from the DA Layer.

Which FDC attestation types support XRPL payments?

XRPPayment (type 0x08) confirms an XRPL Payment with native fields like r-address, MemoData, and DestinationTag, while XRPPaymentNonexistence (0x09) proves no matching payment occurred in a ledger range. Both use XRP or testXRP source IDs.

Does Web2Json support fetching data from any Web2 API?

Web2Json fetches arbitrary public Web2 content with a JQ post-process and ABI signature, using the PublicWeb2 source on Coston and Coston2. The response is externally provided data and must be decoded only against your expected ABI struct, never treated as trusted input.

How long is an FDC proof valid after the attestation round?

Proofs can only be constructed for sufficiently recent data: most chain-data types allow up to 14 days, while AddressValidity and Web2Json have no practical limit. Once constructed, a proof remains available indefinitely from the DA Layer.

What are the limitations of this FDC guidance skill?

The skill is documentation-only and does not execute transactions, manage private keys, call contracts, or handle funds. All signing and on-chain execution must occur in developer-controlled environments outside the skill.