flare-fdc

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers integrating the Flare Data Connector must understand attestation types, verifier request flows, Merkle proof retrieval, and on-chain verification, which are spread across many docs and starter repos. This Skill consolidates that knowledge into one reference for building FDC-powered contracts and scripts. ## Core Features & Use Cases - Attestation Type Guidance: Covers EVMTransaction, Web2Json, Payment, AddressValidity, XRPPayment, XRPPaymentNonexistence, and FAssets-oriented types with request/response field references. - End-to-End Workflow Patterns: Documents the prepare → submit → wait for finalization → fetch proof → verify in contract flow for both Hardhat and Foundry setups. - Contract Integration Patterns: Shows how to resolve FdcVerification via ContractRegistry, verify proofs, and decode response data with Solidity structs. - Use Case: A developer building a proof-of-reserves dApp can follow the documented Web2Json plus EVMTransaction patterns and starter repo pointers to implement verification without searching scattered documentation. ## Quick Start Ask how to verify an XRPL payment proof in a Solidity contract on Flare using FDC.

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 contract?

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

What is the FDC attestation request workflow on Flare?

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

Which FDC attestation type should I use for XRPL payments?

Use XRPPayment (type 0x08) to confirm an XRPL Payment with native fields like r-address, MemoData, and DestinationTag, or XRPPaymentNonexistence (0x09) to prove no matching payment occurred in a ledger range. The generic Payment type lacks XRPL-native fields.

Does FDC support fetching data from Web2 APIs?

Yes, the Web2Json attestation type fetches public Web2 data, applies a JQ post-process transform, and returns ABI-encoded output verifiable on-chain. It is available on Coston and Coston2 via the PublicWeb2 source.

Why is my FDC proof not available yet after submitting a request?

Proofs are only available after the voting round finalizes, typically 90 to 180 seconds. Poll Relay.isFinalized(200, roundId) before querying the DA Layer, and note data age limits of up to 14 days for most chain-data types.

What are the limitations of the flare-fdc skill?

The skill is documentation and guidance only. It does not execute transactions, manage keys, call contracts, or handle funds; all signing and on-chain execution must happen in developer-controlled environments.