flare-ftso

What problem does it solve?

Flare FTSO integration can be subtle and error-prone: developers need clear guidance to read block-latency feeds, verify scaling (anchor) Merkle proofs, calculate and supply any required fees, and implement secure offchain/onchain consumption without exposing keys or misinterpreting raw RPC data. This skill collects architecture explanation, contract interfaces, example scripts, and security guidance to reduce integration mistakes and ensure correct, auditable feed consumption.

Core Features & Use Cases

• Architectural Overview: Explains FTSO components (block-latency feeds, scaling anchor feeds, VRF selection, incremental delta updates, volatility incentives).
• Onchain Integration: Guidance for Solidity consumers including resolving FtsoV2 via ContractRegistry, calling getFeedByIdInWei/getFeedsById, fee calculation via IFeeCalculator, and verifyFeedData for anchor proofs.
• Offchain & Frontend: Examples for JavaScript/TypeScript and wagmi/viem frontends that dynamically resolve contract addresses, poll feeds, and format wei-scaled values for display.
• Security & Data Handling: Rules for treating feed values as typed ABI outputs, never exposing private keys to AI, and ensuring human-in-the-loop for payable operations.
• Use Case: Read FLR/USD and BTC/USD block-latency feeds offchain, derive a BTC/ETH cross-quote, or verify a scaling anchor proof onchain before storing a proven value.

Quick Start

Ask the skill to explain how to read FLR/USD and BTC/USD using ContractRegistry and FtsoV2, convert wei-scaled values to human-readable prices, and verify a scaling anchor Merkle proof with verifyFeedData while keeping all signing in your local environment.