flare-fdc

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers integrating the Flare Data Connector (FDC) 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 domain knowledge into one reference. ## 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 Hardhat and Foundry scripts. - Contract Integration Patterns: Shows how to resolve FdcVerification via ContractRegistry and verify proofs before decoding data. - Use Case: When building a cross-chain payment dApp that must prove an XRPL payment occurred, use this Skill to construct the XRPPayment attestation request, retrieve the DA Layer proof, and verify it in a Solidity contract. ## Quick Start Ask how to verify an XRPL payment on Flare using an FDC attestation and get the full request, proof retrieval, and contract verification flow.

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 before decoding and using the response data.

How to request an FDC attestation on Flare testnet?

POST to a verifier endpoint like /verifier/eth/EVMTransaction/prepareRequest to get the abiEncodedRequest, then call FdcHub.requestAttestation with the required fee. Compute the round ID from the block timestamp and wait for Relay finalization before fetching the proof.

What is the difference between XRPPayment and Payment attestation types?

XRPPayment exposes XRPL-native fields such as r-addresses, MemoData, and DestinationTag that the chain-agnostic Payment type does not. Use XRPPayment (type 0x08) when your dApp needs memo or destination tag data from XRPL transactions.

Does FDC support fetching Web2 API data on-chain?

Yes, the Web2Json attestation type fetches public Web2 data, applies a JQ transform, and returns ABI-encoded output verifiable on-chain. You must define a matching struct and ABI signature in both the verifier request and the contract.

How long does FDC round finalization take?

Round finalization typically takes 90 to 180 seconds. Poll the Relay contract with isFinalized(200, roundId), where 200 is the FDC protocol ID, before requesting the proof from the DA Layer.

What are the limitations of FDC proof data age?

Most chain-data attestation types like EVMTransaction and Payment allow proofs only for data up to 14 days old. AddressValidity and Web2Json have no practical age limit, and once constructed a proof remains available indefinitely.