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
The following crypto asset pair has been added to the FTSO system on both Songbird and Flare -
TRUMP/USD
It will be available beginning Monday 20 January at the start of the new rewards epoch, 7:00 AM UTC, for anchor feeds and shortly thereafter after (within approximately fifteen minutes) for block latency feeds including incentive offers
Inflation rewarding will commence the following week on Monday 27 January at the beginning of epoch 263
$TRUMP has also been added to the example provider and the data can be reviewed here -
The new feed ID for $TRUMP is - 0x015452554d502f5553440000000000000000000000
We have just released an update and more stable version of both the flare-systems-deployment and fdc-suite-deployment
You simply need to regenerate configs and pull new images for both
This also means that you can now begin setting up your FDC clients and FDC suites on Flare (for those who haven’t yet Songbird)
Those who have already deployed FSP/FDC on Songbird are encouraged to update on Songbird as well
We have enabled FDC features on the Flare systems explorer and will be doing some test rounds beginning next week
The following crypto asset pairs have been approved by the Management Group and subsequently added to the FTSO system on Songbird:
Additionally, the following crypto asset pairs have been approved by the Management Group and subsequently added to the FTSO system on Flare:
Inflation rewarding for all of the above will commence this coming Monday at the start of the new rewards epoch on 10-February-2025 (epoch 267)
The new feeds have also been added to the example provider and the data can be reviewed here -
The following crypto asset pair has met auto-inclusion conditions of FIP.08/STP.08 and subsequently added to the FTSO system on both Flare and Songbird:
Inflation rewarding for $BERA will commence this coming Monday for anchor feeds, at the start of the new rewards epoch, on 17-February-2025 (epoch 269) and on 24-February-2025 (epoch 271) for fast updates
The new feed has also been added to the example provider and the data can be reviewed here -
The following crypto assets have undergone a rebranding / ticker change and have subsequently been updated to the FTSO system on both Flare and Songbird:
These changes will take effect on Monday 10-March-2025 for both scaling and fast updates
Updates to the example provider can be reviewed here -
Upcoming Network Update to v1.10.0
Initial upgrades will be deployed first to both testnets, Coston and Coston2 only. Future deployment to canary-net and/or mainnet would be announced at a later time…
Please update all testnet nodes to Avalanche version v1.10.0 prior to -
Coston (Songbird testnet): March 27, 2025, at 13:00 UTC
Coston 2 (Flare testnet): April 8, 2025, at 12:00 UTC
Thank you!