Skip to content
Small red and white spheres form an eye shape
Flare Time Series Oracle
Back to All News

How do we ensure data integrity: FIP.10 & SIP.04 implementation plan

Flare Updates

At Flare, we uphold data integrity with our effective Minimal Conditions incentive structure, designed to promote consistent and high-quality participation from data providers across Flare Protocols. In doing so, we provide users and their dApps with confidence in the secure, reliable, and low-cost access to data that powers onchain finance.

UPDATE 4/14/25: The FIP.10 and SIP.04 proposals introduced Minimal Conditions for participation, which first took effect for data providers on February 4, 2025.

And starting on April 24, 2025, the Flare Data Connector (FDC) protocol will become part of the Minimal Conditions criteria on both Flare and Songbird. Rewards distributed on April 28, 2025 will be the first to reflect this change.

Tools to help you make informed delegation and staking choices

To assist delegators and stakers in making well-informed decisions, we’ve introduced tracking dashboards for both Flare and Songbird. With the FDC now live, it can be tracked in the Flare Systems Explorer.

FIP.10 Flare Songbird Tracking Dashboards

These dashboards display data providers that meet the following requirements (indicated with ‘Yes’):

FTSO anchor feeds: Providers must submit value estimates within a 0.5% band of the consensus median in at least 80% of voting rounds during a reward epoch.

FTSO block-latency feeds: Providers must submit at least 80% of expected updates per reward epoch, unless they have a very low weight (below 0.2% of the total active weight).

Staking: Providers need 80% uptime with a minimum of 1M FLR in active self-bond. To earn passes, they must hold at least 3M FLR in active self-bond and 15M in active stake. Providers with sufficient uptime but less stake do not gain or lose passes but still earn rewards.

For Songbird, the same requirements apply for FTSO anchor feeds and block-latency feeds as in Flare, while staking requirements are not applicable.

Additionally, the dashboard shows Passes: For each reward epoch where a data provider meets the minimal participation criteria across all protocols, they earn one pass. A provider with 3 passes demonstrates consistent compliance over the last three reward epochs.

Best Practices for delegating and staking

Data providers failing to meet minimal conditions on certain Flare protocols will not receive rewards in any protocol, and their rewards will be burned. This impacts the earnings of data providers, delegators, and stakers alike.

To maximize your rewards while supporting reliable data providers, follow these simple guidelines:

  1. Ensure the “Number of Passes” is at least 1.
  2. Confirm that the provider is marked as “Eligible for Rewards” (green) on the dashboards.

Additional Resources

For more details about the minimal conditions and incentive structure, read the published blog: https://flare.network/new-incentives-structure-for-protocol-participation/

For data providers, visit our forum for detailed historical data on providers’ performance over past reward epochs, specifying which conditions you meet and which you do not, and to join the discussion: https://forum.flare.network/t/anno