Pinned Tweet
Flare gives developers built-in access to two things applications usually have to source elsewhere: prices and proofs of external events.
FTSO handles decentralized price data, while FDC verifies supported events outside Flare, including activity on other chains.
Flare tends this further. Sensitive or heavy logic can run in hardware-secured environments and return a result that contracts can verify onchain.
That means a developer can start from verified data, run logic that does not belong in public execution, and use the result inside an application without stitching together a separate oracle, verification and confidential compute stack.
XRPFi is already one example of what this architecture enables.
Data first. Compute next. Then the applications neither could support alone.
FTSO handles decentralized price data, while FDC verifies supported events outside Flare, including activity on other chains.
Flare tends this further. Sensitive or heavy logic can run in hardware-secured environments and return a result that contracts can verify onchain.
That means a developer can start from verified data, run logic that does not belong in public execution, and use the result inside an application without stitching together a separate oracle, verification and confidential compute stack.
XRPFi is already one example of what this architecture enables.
Data first. Compute next. Then the applications neither could support alone.
0
10
42
6,914
Thanks to the node operators who upgraded ahead of activation. ☀️
If yours hasn’t been upgraded, please do it now.
Release notes and upgrade instructions: github.com/flare-foundati…
If yours hasn’t been upgraded, please do it now.
Release notes and upgrade instructions: github.com/flare-foundati…
The hard fork activated successfully, and the network continues to process transactions normally. Confirmations may take slightly longer than usual while the remaining validators upgrade.
Big thanks to all validators and node operators for their quick response and coordination in making this happen.
1
7
26
531
Update: Corrected go-flare v1.15.1 build is now available.
The updated release addresses an issue affecting the network upgrade on Songbird and Coston.
Important for node operators:
• Songbird and Coston nodes must upgrade again, even if already running v1.15.1.
• The corrected build is now available, including updated Docker images.
• No resync or database changes are required. Restart your node after updating.
Flare mainnet and Coston2 are unaffected by this specific issue.
Please follow the official release instructions and verify you’re running the corrected build.
🔗 github.com/flare-foundati…
The updated release addresses an issue affecting the network upgrade on Songbird and Coston.
Important for node operators:
• Songbird and Coston nodes must upgrade again, even if already running v1.15.1.
• The corrected build is now available, including updated Docker images.
• No resync or database changes are required. Restart your node after updating.
Flare mainnet and Coston2 are unaffected by this specific issue.
Please follow the official release instructions and verify you’re running the corrected build.
🔗 github.com/flare-foundati…
Important network update for Songbird and Coston.
An additional node update is required as part of the ongoing network upgrade.
Here’s what to expect:
• Validator nodes have already been upgraded, so block production is not affected.
• RPC and observation nodes may experience connectivity issues until upgraded.
• FAssets minting and redemptions on Songbird will be temporarily paused until the required infrastructure updates are completed.
Flare mainnet is unaffected by this issue.
The additional node update is being prepared, and we’ll share the release and upgrade instructions as soon as they’re available.
We’ll provide further updates as the transition progresses.
5
7
33
1,514
For additional technical details and ongoing updates, follow the discussion on the Flare Forum:
forum.flare.network/t/announcement…
Node operators should also carefully review the configuration changes in the official v1.15.1 release notes.
forum.flare.network/t/announcement…
Node operators should also carefully review the configuration changes in the official v1.15.1 release notes.
0
0
4
145
Important network update for Songbird and Coston.
An additional node update is required as part of the ongoing network upgrade.
Here’s what to expect:
• Validator nodes have already been upgraded, so block production is not affected.
• RPC and observation nodes may experience connectivity issues until upgraded.
• FAssets minting and redemptions on Songbird will be temporarily paused until the required infrastructure updates are completed.
Flare mainnet is unaffected by this issue.
The additional node update is being prepared, and we’ll share the release and upgrade instructions as soon as they’re available.
We’ll provide further updates as the transition progresses.
An additional node update is required as part of the ongoing network upgrade.
Here’s what to expect:
• Validator nodes have already been upgraded, so block production is not affected.
• RPC and observation nodes may experience connectivity issues until upgraded.
• FAssets minting and redemptions on Songbird will be temporarily paused until the required infrastructure updates are completed.
Flare mainnet is unaffected by this issue.
The additional node update is being prepared, and we’ll share the release and upgrade instructions as soon as they’re available.
We’ll provide further updates as the transition progresses.
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
2
9
28
1,220
Flare Devs retweeted
All our validators and observer node where updated.
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
0
2
13
341
Flare Devs retweeted
Updating both nodes and our SGB node as we speak.
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
1
4
27
559
Flare Devs retweeted
HP/Mana updated critical backend upstream vulnerabilities prior to this release that may or may not be related to this particular situation.
All backend has been updated to the latest release within minutes
All backend has been updated to the latest release within minutes
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
1
5
19
384
Flare Devs retweeted
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
0
3
17
582
Flare Devs retweeted
Please reshare with anyone running infrastructure on Flare.
A few important things to know before upgrading:
• Some existing C-chain settings might no longer be compatible. Check your configuration carefully, or your node may fail to start.
• The upgrade introduces a new directory for storing C-chain data. This data needs to be kept on persistent storage, so it isn't lost when your node restarts. Otherwise, you may need to sync your node from scratch.
• Check your available disk space. Nodes running very low on storage may refuse to start.
Please read the release notes carefully before upgrading.
We need everyone ready before the fork.
A few important things to know before upgrading:
• Some existing C-chain settings might no longer be compatible. Check your configuration carefully, or your node may fail to start.
• The upgrade introduces a new directory for storing C-chain data. This data needs to be kept on persistent storage, so it isn't lost when your node restarts. Otherwise, you may need to sync your node from scratch.
• Check your available disk space. Nodes running very low on storage may refuse to start.
Please read the release notes carefully before upgrading.
We need everyone ready before the fork.
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
2
13
65
1,670
Flare Devs retweeted
Observe the network migrate to the latest version on FM.
Currently 10.9B FLR (55.4%) of 688B FLR (44.6%) stake has migrated to latest node version.
Link in post below.
Currently 10.9B FLR (55.4%) of 688B FLR (44.6%) stake has migrated to latest node version.
Link in post below.
2
2
13
2,109
Flare Devs retweeted
Flare is rolling out go-flare v1.15.1, a network upgrade that patches a vulnerability in the upstream code used by Flare nodes. The fix has already been tested. The hard fork activates on Nov 11 at 14:00 UTC. Validators and node operators: please upgrade as soon as possible.
Why now: the fix was already scheduled for later this month. We’re bringing it forward after our monitoring flagged an attempt to exploit the vulnerability. Engineering and validators are coordinating on the rollout.
For users: no action needed. Once validators upgrade, the network carries on as normal. The vulnerability does not affect user funds or keys.
Why now: the fix was already scheduled for later this month. We’re bringing it forward after our monitoring flagged an attempt to exploit the vulnerability. Engineering and validators are coordinating on the rollout.
For users: no action needed. Once validators upgrade, the network carries on as normal. The vulnerability does not affect user funds or keys.
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
10
37
189
16,014
CRITICAL: Mandatory Flare node upgrade (go-flare v1.15.1)
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
An active exploit attempt is targeting a vulnerability in the upstream code used by Flare nodes. An emergency hard fork activates on November 11, 2026 at 14:00 UTC. All validators and node operators must upgrade to go-flare v1.15.1 as soon as possible.
IMPORTANT:
• This release includes configuration and data storage changes. Review and follow the full migration instructions before upgrading.
• Official go-flare v1.15.1 release notes and upgrade instructions: github.com/flare-foundati…
• Confirm your upgrade status in the existing communication channels.
Nodes that are not correctly upgraded before activation will be unable to follow the upgraded network. Network continuity depends on enough stake upgrading in time. Please treat this as your top priority.
5
43
108
14,724
FIP.16 cut annual FLR inflation from 5% to 3%, a 40% reduction.
Fees from FDC and FAssets now flow into FIRE, with more network services to follow. The goal is to replace inflation-funded rewards with network revenue and reduce FLR supply.
More network usage now generates revenue to support the infrastructure securing it.
The July upgrade raised the base gas fee 20x, so every transaction now burns 20x more FLR.
Fees from FDC and FAssets now flow into FIRE, with more network services to follow. The goal is to replace inflation-funded rewards with network revenue and reduce FLR supply.
More network usage now generates revenue to support the infrastructure securing it.
The July upgrade raised the base gas fee 20x, so every transaction now burns 20x more FLR.
🔥 $FLR Inflation offset by ~13.2% (rolling 30d) 🔥
Once it reached 100%+ FLR is officially deflationary.
I built this tool for the @FlareNetworks community, specifically to monitor this metric.
Are you paying attention?
👉 flareburnmonitor.com
4
13
55
1,645
Flare Devs retweeted
A new FLR-denominated venue is live on Flare.
More FLR deployed. More network activity . More base fee burned.
EarnFLR Vault from @SparkDexAI and @upshift_fi is live: deposit WFLR, and curated strategies put it to work across Flare DeFi.
More FLR deployed. More network activity . More base fee burned.
EarnFLR Vault from @SparkDexAI and @upshift_fi is live: deposit WFLR, and curated strategies put it to work across Flare DeFi.
The wait is over.
One WFLR deposit. Several FLR-native earning sources, all working for you at once.
Introducing the new EarnFLR Vault, curated by SparkDEX in collaboration with @upshift_fi
A new home for your WFLR on @FlareNetworks
6
46
188
12,029
A good reminder from our DevRel for anyone building with FAssets or integrating FXRP into their apps.
Flare AI Skills are regularly updated with the latest protocol information and developer best practices.
Make sure your agents are working with the latest documentation, including FAsset pause status:
dev.flare.network/fassets/emerge…
Flare AI Skills are regularly updated with the latest protocol information and developer best practices.
Make sure your agents are working with the latest documentation, including FAsset pause status:
dev.flare.network/fassets/emerge…
Before you mint or redeem FXRP, check the FAssets pause status on AssetManager.
📑 Docs: dev.flare.network/fassets/emerge…
Keep the Flare AI skills updated; we update them regularly.
5
11
31
1,173
Build on Flare, use XRP and @FlareNetworks data infrastructure underneath, and serve markets far beyond Flare itself. ☀️
Customer-facing platforms spent the past year selling DeFi yield through Earn products, and curated vault TVL grew 26% to ~$10B while lending fell 39%.
One problem persists: when a protocol or vault gets hacked, depositors absorb the loss.
@Firelightfi, incubated by @SentoraHQ, lets XRP holders stake on @FlareNetworks to back cover for vaults, paying out if a protocol a vault deposits into is exploited. It now covers vaults at Kraken, Lido, and Sentora.
Our new report on why Total Value Covered belongs next to TVL: defillama.com/research/repor…
3
11
45
2,513
Flare Devs retweeted
Still checking your FTSO rewards manually?👀
You don't have to keep tabs on everything yourself.
FlareGPT's Gas Sniper monitors gas conditions and claim timing, helping automate your FTSO reward claims when the timing is right.
One less thing to keep checking. One more reason work.
Explore FlareGPT: flaregpt.io
You don't have to keep tabs on everything yourself.
FlareGPT's Gas Sniper monitors gas conditions and claim timing, helping automate your FTSO reward claims when the timing is right.
One less thing to keep checking. One more reason work.
Explore FlareGPT: flaregpt.io
1
7
19
342
Flare Devs retweeted
And all of this while targeting a 3% APY and being accessible in one click from your favorite XRPL wallet: fsa.flare.network/vaults/1
I think the bigger picture here is wild.
XRP becoming underwriting capital for DeFi is one of the most interesting things happening and very few are paying attention to this.
Around 40M FXRP is already backing over $50M in cover, and this is still very small relative to where this could go.
But if this market scales, we're talking about XRP becoming part of the balance sheet behind DeFi itself.
And Flare is what makes this possible.
2
6
37
943
Flare Devs retweeted
📊 FXRP Daily Report - Nov 09, 2026
𝗠𝗶𝗻𝘁𝘀:
235,836 FXRP ($259,083)
Avg: 1,062 ($1,167) | Max: 39,966 ($43,906) | 222 txs
𝗥𝗲𝗱𝗲𝗺𝗽𝘁𝗶𝗼𝗻𝘀:
89,239 FXRP ($98,035)
Avg: 1,785 ($1,961) | Max: 20,000 ($21,971) | 50 txs
Net: +146,597 FXRP 📈
Total FXRP: 144,637,861
𝗠𝗶𝗻𝘁𝘀:
235,836 FXRP ($259,083)
Avg: 1,062 ($1,167) | Max: 39,966 ($43,906) | 222 txs
𝗥𝗲𝗱𝗲𝗺𝗽𝘁𝗶𝗼𝗻𝘀:
89,239 FXRP ($98,035)
Avg: 1,785 ($1,961) | Max: 20,000 ($21,971) | 50 txs
Net: +146,597 FXRP 📈
Total FXRP: 144,637,861
2
2
19
429
Flare Devs retweeted
Feed accuracy matters. We cross-check FTSO price submissions against consensus before flagging drift -- it is one of the quieter parts of how FlareWatch monitors validator health.
flarewatch.io/validators
#FLR #flarewatch
flarewatch.io/validators
#FLR #flarewatch
0
2
15
351