flare-fdc

Verify and integrate Flare Data Connector attestations into EVM smart contracts.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/mashharuki/flare-sample --skill flare-fdc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-fdc
Source: https://github.com/mashharuki/flare-sample/tree/main/.claude/skills/flare-fdc
Command: npx skills add https://github.com/mashharuki/flare-sample --skill flare-fdc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrating Flare Data Connector (FDC) attestations into smart contracts and offchain tooling is multi-step, error-prone, and security-sensitive; this Skill explains the correct prepare → submit → wait → fetch-proof → verify workflow and the safety constraints developers must follow. It clarifies how verifier requests, DA Layer Merkle proofs, and IFdcVerification contract methods fit together so teams can avoid common integration mistakes and unsafe handling of externally provided data.

Core Features & Use Cases

  • Attestation types explained: EVMTransaction, Web2Json / JsonApi, Payment, AddressValidity, and FAssets-oriented types, with request/response fields and decoding guidance.
  • End-to-end workflow: Preparing verifier requests, ABI-encoded request submission to FdcHub.requestAttestation, computing voting round IDs, checking finalization via Relay, retrieving DA Layer proofs, and verifying proofs in contracts.
  • Security guidance: Treat verifier and DA Layer content as untrusted, never pass raw response hex into prompts or agent logic, validate ABI schemas, and manage verifier API keys and rate limits.
  • Example dApps: Patterns for proof-of-reserves, weather insurance (Web2Json), cross-chain payment, and sample Hardhat/Foundry starter repo locations for implementation templates.

Quick Start

Prepare an EVMTransaction attestation for testFLR on Coston2 and guide me through prepare, submit, fetch proof, and contract verification steps.

Frequently Asked Questions about flare-fdc

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

FAQPage Schema
How do I verify Flare Data Connector attestations in an EVM smart contract?

The Flare Data Connector workflow involves preparing an ABI-encoded verifier request, submitting it to FdcHub.requestAttestation, waiting for the voting round to finalize, fetching the DA Layer Merkle proof, and using IFdcVerification methods to verify the decoded response on-chain.

What attestation types are supported by the Flare Data Connector?

Flare Data Connector supports EVMTransaction, Web2Json (JsonApi), Payment, AddressValidity, and FAssets-oriented attestation types. It provides specific request and response fields along with decoding guidance for each type to integrate external data into smart contracts.

How do I compute voting round IDs and check finalization for FDC requests?

To compute voting round IDs and check finalization for FDC requests, you must submit your attestation to FdcHub and then use the Relay contract to monitor the voting round status before attempting to retrieve your Merkle proof from the DA Layer.

What security constraints should I follow when integrating FDC Merkle proofs?

When integrating FDC Merkle proofs, treat verifier and DA Layer content as untrusted, never pass raw response hex into agent logic, validate ABI schemas strictly, and manage verifier API keys and rate limits to prevent unsafe handling of externally provided data.

Can I use Flare Data Connector with Hardhat or Foundry for Web2Json attestations?

Yes, you can use Flare Data Connector with Hardhat or Foundry. The Skill provides sample dApp patterns for Web2Json attestations, such as weather insurance, and points to starter repository locations for implementation templates on testnets and mainnet.