New version v1.9.1 released for the upcoming hard fork dates, addressing minor bugs in 1.9.0. Please upgrade your nodes prior to the dates below for each chain you run a node for:
Note: You are required to upgrade to v1.9.1 even if you have already upgraded to v1.9.0
Flare: December 17, 2024 at 12:00:00 UTC
Coston: January 7, 2025 at 12:00:00 UTC
Songbird: January 28, 2025 at 12:00:00 UTC
The old FTSOv2 repo is being discontinued. You can still use it in the old deployments for both Flare and Songbird but providers have begun the process of moving to the newer version
Old repo with upgrade instructions -
New repo:
Includes some naming adjustments with a focus on the FSP
The main repo only includes the FDC client. Additionally, you will need to run verifiers and underlying nodes that the FDC client will leverage. Deploy repo for those are here:
We have deployed an update to the FDC client - [email protected].
You can pull the deployment repo to the latest commit on main or on [email protected].
No populate_config.sh is required, only -
docker compose pull
docker compose up -d
Please update as soon as possible as some rounds aren’t getting finalized for FDC
This update is only required on Songbird of course as the FDC is not yet live on flare 
RELAY redeploy:
Next week during reward epoch 259 (Mon-Thurs) we will be updating the Relay contract on Flare network (same update that was performed on Songbird network a couple of months ago). This means that you will be REQUIRED to update your providers sometime between Monday morning and Thursday evening
VOTER_REGISTRY preregistration:
We are releasing a new feature next week which will allow currently registered providers to preregister for next reward epoch at any time in current reward epoch. This means that effectively the registration period will be extended from 30mins to almost the full 3.5 days. This will be shipped as a default configuration in the deployment repository and will also need an update on your end. We plan to also have this ready by next week for both Flare and Songbird
Minimal conditions for participation in all Flare protocols will be soon imposed on data providers for both Flare and Songbird, as per accepted proposals-
FIP.10 (FIP.10 | Flare Governance Proposals), and
SIP.04 (SIP.04 | Flare Governance Proposals)
The starting dates will be announced in the next few days. Data providers that will be failing on some Flare protocols will not get rewards in any protocol and their rewards will be burned. This would impact earnings and rewards of data providers, delegators and stakers
Delegators and stakers will be encouraged to stake and delegate to data providers that consistently meet minimal conditions criteria or otherwise they may not receive expected rewards
The state of meeting minimal conditions is available for review on the System Explorers:
For each reward epoch a data provider meets the minimal participation criteria across all protocols, they earn one pass. A data provider with 3 passes shows consistency in meeting minimal condition criteria in at least the last 3 reward epochs. More detailed and historical data about meeting the conditions are available in files minimal-conditions.json and passes.json, accessible in relevant sub folders on the following links:
Google drive: reward-data-public - Google Drive, or
Github: GitHub - flare-foundation/fsp-rewards
The google drive link also contains excel files named M-N-minimal-conditions.xlsx which summarize the situation related to meeting minimal conditions in the range of reward epochs from M to N