Flare Emergency Hard Fork: go-flare v1.15.1 and FLR Deposit Delays Explained
Flare activated an emergency go-flare v1.15.1 hard fork on November 11, 2026 after detecting an exploit attempt. Holders need not act, but Kraken FLR deposits and withdrawals are delayed.
Crypto Support & Research Desk
Quick answer: Flare activated an emergency go-flare v1.15.1 hard fork on Flare and Songbird at 14:00 UTC on November 11, 2026, after its monitoring caught an attempt to exploit a bug in upstream node code. Flare says user funds and keys are safe and holders need not act. Kraken has reported FLR deposit and withdrawal delays since November 11, still open on November 14.
What happened to the Flare network
On November 10, 2026, Flare's monitoring flagged an attempt to exploit a bug in upstream code that Flare nodes run, according to a bsc.news report syndicated by Cryptonews.net. Flare responded by bringing forward a planned upgrade, go-flare v1.15.1, which had been scheduled for later in the month.
The hard fork activated at 14:00 UTC on Wednesday, November 11, 2026. It applies to both networks that the go-flare client runs: the Flare mainnet and its canary network, Songbird. Flare stated that the fix had been tested before release, that user funds and keys were not affected, and that ordinary users did not need to take action.
Flare has not published technical details or a CVE for the underlying bug, and it has not said whether the exploit attempt achieved anything beyond being detected. Reports describe no chain halt or missed blocks after the fork.
Why a hard fork was needed
A hard fork changes the network's rules from a specific activation point. Every node that validates the chain must run the new software by that time. Nodes that stay on the old version can fall out of sync with the rest of the network, because they no longer agree on which blocks are valid.
According to the go-flare v1.15.1-rc.1 pre-release on GitHub, published on October 29, version 1.15.1 moves Flare and Songbird onto AvalancheGo v1.15.1, known as the "Helicon" upgrade. The release candidate activated on the Coston2 testnet at 12:00 UTC on November 3, and that build was set to refuse to start on mainnet. The release notes also warned operators to check their C-chain config.json, which may need changes to stay valid after activation.
The emergency part was the timing: the upgrade already existed and had been tested, and the exploit attempt moved its mainnet activation forward.
Who is affected
FLR and SGB holders in self-custody
If you hold FLR or SGB in your own wallet, Flare's guidance is that no action is required. Your tokens remain on-chain and your keys are not affected by the fork.
Validators and node operators
Anyone running a Flare or Songbird node had to install v1.15.1 before 14:00 UTC on November 11. If you run infrastructure and missed the window, upgrade immediately, review your C-chain configuration and resync your node.
Exchange users
Exchanges run their own nodes and usually pause or slow deposits and withdrawals around forks. Kraken's status page shows a "Flare (FLR) Funding Delays" incident opened at about 15:37 UTC on November 11, roughly 1.5 hours after activation. Its status was still "Investigating" as of about 12:20 UTC on November 14, with the FLR component listed as "Degraded Performance" and a note that deposits and withdrawals may be delayed. Kraken has not said whether the delay is caused by the fork.
We found no comparable notices from Binance, OKX, Upbit or Bithumb for this fork at the time of writing.
How to check whether your FLR transfer is safe
If you sent FLR to or from an exchange and it has not arrived, work through these steps.
Step 1: Find your transaction hash
Look in your wallet's activity list or your exchange's withdrawal history for the transaction hash (TxID). Copy it exactly.
Step 2: Check the transaction on a Flare explorer
Paste the hash into a reputable Flare block explorer. Look for:
- Success status: the transaction is confirmed on-chain.
- Correct recipient address: it matches the deposit address shown in your exchange account.
- Correct network: you sent native FLR on the Flare network, not a wrapped or bridged version on another chain.
Step 3: Check the exchange's status page
If the transaction is confirmed on-chain but not credited, check the exchange's official status page. For Kraken, the open FLR incident explains why credits may be slow.
Step 4: Wait instead of resending
Do not send the same deposit again. Once the exchange restores normal processing, confirmed deposits are normally credited. Resending only creates a second pending transfer to track.
Step 5: Contact support with evidence
If the incident is resolved and your deposit still is not credited, open a ticket through the exchange's official app or website. Include the transaction hash, amount, time sent and the deposit address you used.
What to avoid during network incidents
- Do not use "recovery" services that contact you on social media offering to release stuck FLR.
- Do not connect your wallet to sites claiming to "migrate" or "upgrade" your FLR. Flare says holders do not need to do anything for this fork.
- Do not share your seed phrase, private keys, passwords or 2FA codes with anyone, including people claiming to be exchange or Flare staff.
How this compares with other recent network incidents
Network upgrades and halts have been frequent this month. The Injective mainnet halt on November 9 paused INJ transfers on several exchanges, and the Osmosis chain halt led Upbit and Bithumb to suspend OSMO funding. Scheduled upgrades follow a calmer pattern, as in our guide to the Hedera v0.79 mainnet upgrade on November 18. For a general checklist on moving funds around upgrades, see our Scroll network upgrade transfer checklist.
The Flare case sits between these: a planned, tested upgrade that was pulled forward for security reasons, followed by lingering exchange funding delays.
What is still unknown
- The technical details of the upstream bug and whether the exploit attempt caused any on-chain effect.
- Whether Kraken's FLR delays are caused by the fork or by a separate gateway issue.
- When Kraken will restore normal FLR funding.
- Whether any other exchange paused FLR or SGB transfers.
Frequently asked questions
What is the Flare go-flare v1.15.1 hard fork?
It is a mandatory node upgrade for Flare and Songbird that activated at 14:00 UTC on November 11, 2026. It was brought forward after Flare detected an attempt to exploit a bug in upstream node code.
Do FLR holders need to do anything?
No. Flare says user funds and keys are not affected and ordinary holders do not need to take action. Only validators and node operators had to upgrade their software.
Why is my FLR deposit to Kraken delayed?
Kraken has had an open FLR funding delays incident since November 11. If your transaction is confirmed on a Flare explorer, wait for Kraken to resolve the incident rather than resending.
Was Songbird affected by the fork too?
Yes. The go-flare client runs both Flare and Songbird, and the v1.15.1 hard fork covers both networks.
Were any funds lost in the Flare exploit attempt?
Flare says user funds and keys were not affected. It has not published technical details of the bug or the attempt.
Conclusion
Flare's emergency v1.15.1 hard fork was a precautionary upgrade, not a fund-loss event. If you hold FLR or SGB yourself, nothing needs to change. If you are waiting on an exchange transfer, especially on Kraken, confirm your transaction on-chain, keep the hash and wait for the incident to close before contacting support. Ignore anyone telling you to "migrate" your tokens.
This article is for general information only and is not financial or technical advice. Blockchain Support USA is an independent publication and is not affiliated with Flare, Kraken or any exchange. We will never ask for your seed phrase, private keys, passwords or 2FA codes.
Regulatory & Financial Risk Disclosure
The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.
About the Author
Crypto Support & Research Desk
Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.