flare-fdc

Explain Flare Data Connector attestation types, request flows, and Merkle proofs.

1|1|Updated May 6, 2026
One-click install
npx skills add https://github.com/Thanasimos/Thanas-flare-builders-toolkit --skill flare-fdc-thanasimos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-fdc
Source: https://github.com/Thanasimos/Thanas-flare-builders-toolkit/tree/main/flare-fdc
Command: npx skills add https://github.com/Thanasimos/Thanas-flare-builders-toolkit --skill flare-fdc-thanasimos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides domain knowledge and guidance for the Flare Data Connector (FDC)—attestation types, request flow, Merkle proofs, verifier/DA Layer, and smart contract integration. Use when working with FDC, cross-chain attestations, EVMTransaction, Web2Json, Payment, AddressValidity, XRPPayment, XRPPaymentNonexistence, proof-of-reserves, weather insurance, or Flare Developer Hub FDC guides and starter repos.

Core Features & Use Cases

  • Conceptual guidance on FDC architecture, attestation flow, and verification patterns.
  • Reference material linking to Flare Developer Hub docs and starter repos.
  • Read-only guidance for building on FDC without executing transactions.

Quick Start

Review the Flare Developer Hub FDC guides and starter repos to begin designing read-only integrations.

Frequently Asked Questions about flare-fdc

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

FAQPage Schema
What is the Flare Data Connector and how do cross-chain attestations work?

The Flare Data Connector (FDC) is a protocol enabling cross-chain attestations by verifying external data on-chain. It uses request flows and Merkle proofs to validate data from sources like EVMTransaction or Web2Json before smart contract integration.

How do I verify Web2Json attestations in a smart contract using Flare?

To verify Web2Json attestations in a smart contract, you use the FDC's DA Layer and Merkle proofs. The process involves requesting the attestation, receiving the proof, and executing on-chain verification logic to safely validate the parsed Web2 data.

Does the Flare Data Connector support XRPPayment and AddressValidity attestation types?

Yes, the Flare Data Connector supports multiple attestation types including XRPPayment, XRPPaymentNonexistence, AddressValidity, EVMTransaction, and Payment, enabling diverse cross-chain data verification and proof-of-reserves use cases for dApps.

What are the best practices for integrating FDC Merkle proofs into EVM smart contracts?

Best practices for integrating FDC Merkle proofs involve using read-only reference patterns from Flare Developer Hub starter repos, ensuring proper DA Layer verification, and validating attestation types before executing smart contract logic to maintain safety.

Can I use Flare Data Connector for weather insurance dApps and proof-of-reserves?

Yes, the Flare Data Connector supports weather insurance and proof-of-reserves applications by leveraging Web2Json and Payment attestation types. It provides the necessary request flow and on-chain verification to securely process external data triggers.

What are the limitations when building read-only integrations with Flare attestations?

The primary limitation is that FDC integration guidance is strictly read-only and does not execute transactions. Developers must reference Flare Developer Hub guides for attestation flows and contract interaction patterns without relying on automated state changes.