flare-ftso

Explain read-only Flare FTSO data integration for Solidity and wagmi apps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides domain knowledge and guidance for the Flare Time Series Oracle (FTSO)—covering block-latency feeds, scaling anchor feeds, feed IDs, onchain and offchain consumption patterns, fee calculations, and smart contract integration. It helps developers, auditors, and security-conscious teams understand architecture, interfaces, and safe usage without performing actions on-chain.

Core Features & Use Cases

  • Explains FTSO architecture, feed types (block-latency and scaling), feed IDs, and common contract patterns.
  • Provides read-only reference material and starter-repo pointers for building consumer apps or verification tooling.
  • Offers safety-first guidance around key operations (delegation, volatility incentives) and how to verify off-chain data with Merkle proofs.

Quick Start

Describe a read-only integration plan to consume FTSO feeds in a frontend or smart-contract verifier without executing any transactions.

Frequently Asked Questions about flare-ftso

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

FAQPage Schema
How do I integrate Flare Time Series Oracle feeds into a frontend app?

Integrating Flare Time Series Oracle feeds into a frontend app requires using wagmi to perform read-only calls to the FtsoV2Interface. You must map feed IDs and apply scaling factors correctly while ensuring no on-chain transactions are executed.

What is the difference between block-latency and scaling feeds in FTSO?

Block-latency feeds in the Flare Time Series Oracle provide rapid price updates aligned with block production, while scaling anchor feeds adjust values to specific decimals, ensuring consistent on-chain and off-chain consumption across smart contracts.

How do I verify off-chain FTSO data with Merkle proofs?

To verify off-chain Flare Time Series Oracle data with Merkle proofs, you validate the cryptographic proof against the committed root hash. This ensures the price feed data securely matches the on-chain state without requiring direct contract interaction.

Does the flare-ftso Skill support executing on-chain delegation transactions?

The flare-ftso Skill does not support executing on-chain delegation transactions. It provides safety-first guidance and architectural documentation for delegation patterns and volatility incentives while strictly enforcing read-only usage.

Can I use web3 and flare-periphery-contract-artifacts to read FTSO feed IDs?

Yes, you can use web3 with the flare-periphery-contract-artifacts package to read FTSO feed IDs. The Skill documents how to interact with the FtsoV2Interface and IFeeCalculator to query active feeds safely in a read-only manner.

What are the limitations of using read-only FTSO integration patterns?

The main limitation of read-only Flare Time Series Oracle integration patterns is the inability to participate in delegation or volatility incentives. You must rely on off-chain verification via Merkle proofs and safe-key handling rather than executing direct state changes.