flare-fdc

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.