flare-ftso

Provides integration guidance for consuming Flare Time Series Oracle price feeds onchain and offchain.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-ftso-zireaelst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-ftso
Source: https://github.com/Zireaelst/Flare-Hackaton/tree/main/.agents/skills/flare-ftso
Command: npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-ftso-zireaelst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires web3, @flarenetwork/flare-periphery-contract-artifacts, @flarenetwork/flare-periphery-contracts, @flarenetwork/flare-wagmi-periphery-package, and includes scripts (resource) and references (resource) components.

What problem does it solve? Developers building on Flare need accurate, decentralized price data but face a learning curve around FTSO's feed IDs, contract resolution via ContractRegistry, fee calculation, and Merkle-proof verification of anchor feeds. This Skill consolidates that domain knowledge into one reference. ## Core Features & Use Cases - Onchain Feed Consumption: Explains how to read block-latency feeds in Solidity via FtsoV2Interface, resolve contracts through ContractRegistry, and calculate fees with IFeeCalculator. - Offchain and Frontend Integration: Covers reading feeds with web3/ethers and building React frontends using wagmi with the official Flare periphery packages. - Anchor Feed Verification and Volatility Incentives: Documents Merkle-proof verification of Scaling feeds and the offerIncentive flow for faster price convergence. - Use Case: A developer building a DeFi vault on Coston2 needs XRP/USD prices; this Skill shows how to resolve FtsoV2, call getFeedsByIdInWei, and convert the result to a displayable price. ## Quick Start Ask the assistant to show how to read the FLR/USD price feed from FTSO on the Coston2 testnet using Solidity or JavaScript.

Frequently Asked Questions about flare-ftso

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

FAQPage Schema
How do I read FTSO price feeds in a Solidity contract?

Resolve the FtsoV2 contract through ContractRegistry rather than hardcoding an address, then call getFeedById or getFeedsById with the bytes21 feed ID. On Coston2 testnet the interface is all view calls with no fees; on mainnet some calls are payable and require a fee from IFeeCalculator.

How to read Flare FTSO feeds offchain with JavaScript?

Use web3 or ethers with the @flarenetwork/flare-periphery-contract-artifacts package to get the FtsoV2 ABI, resolve the contract address via ContractRegistry's getContractAddressByName, and call getFeedsById over the Flare RPC endpoint. The response returns values, decimals, and a timestamp.

What is the difference between block-latency feeds and Scaling anchor feeds?

Block-latency feeds update every block (about 1.8 seconds) via incremental delta updates from VRF-selected providers and are free to query onchain. Scaling anchor feeds use a full commit-reveal process across all providers every 90 seconds and can be verified onchain against a Merkle root with verifyFeedData.

Can I use FTSO feeds in a React frontend with wagmi?

Yes, use the @flarenetwork/flare-wagmi-periphery-package which exports chain configs, ABIs, and the ContractRegistry address. Resolve FtsoV2 with useReadContract on getContractAddressByName, then call getFeedByIdInWei and format the 18-decimal result with viem's formatUnits.

How do I get a feed pair that does not exist, like BTC/ETH?

Fetch both BTC/USD and ETH/USD feeds and divide them to compute the cross pair. Scale the base feed decimals to twice the quote decimals before dividing to retain precision, following the FtsoV2ChangeQuoteFeed pattern in the Flare Developer Hub.

Does this skill execute transactions or manage private keys?

No, it is documentation and reference material only and does not sign, broadcast, or initiate any transactions. All fee payments, volatility incentives, and key management must occur in developer-controlled environments with explicit user confirmation.