Polygon Salvador Hard Fork: Stolen POL Recovery Scheduled for 2 December. What Holders and Node Operators Should Know
Polygon's pending Salvador hard fork would sweep about 70.49 million POL from five blocked attacker addresses, with mainnet set for around 2 December 2026. Here is how it works, what node operators must do and why Upbit's 19 November pause is separate.
Crypto Support & Research Desk
Quick answer: Polygon developers have added a hard fork called "Salvador" to pending Bor client code. It is designed to recover about 70.49 million POL held in five blocked attacker addresses. Proposed activation is Amoy block 53,803,400 (around 25 November) and mainnet block 98,350,200 (around 2 December 2026). Separately, Upbit pauses POL transfers from 11:00 UTC on 19 November.
What is the Polygon Salvador hard fork?
Salvador is a proposed hard fork of Polygon PoS. Its goal is to recover native POL taken in two October 2026 incidents linked to Polymarket and Binance, which is now sitting in blocked attacker addresses.
The work appears in Bor pull request #2546, "add Salvador hardfork." The PR was opened on 13 November, marked ready for review on 16 November, when commits set the fork heights and confirmed the recovery addresses, and received one approval on 17 November. It was still open and unmerged at the time of writing, and needs two approvals.
Why Polygon is doing this
On 4 November 2026, a Polygon Improvement Proposal was posted on the Polygon forum proposing to recover funds held in blocked addresses after the Polymarket and Binance incidents. It covers:
- 23,862,736.07 POL in addresses linked to the Polymarket incident.
- 46,626,593.27 POL at an address linked to the Binance incident.
- About 70.49M POL in total, measured at reference blocks from 29 October 2026.
About 6.19 million USDT taken in the same Binance-related transfer is outside the proposal's scope; it was frozen separately by Tether. The proposal was on the agenda of the Polygon governance call on 5 November. The forum thread still lists the fork name, block and client release as "to be decided once approved," and no formal approval record has been published. The PIP itself calls the measure an extreme action that should not become common.
How the recovery works
Salvador does not directly edit account balances. Based on the PR:
1. At the fork block, every node installs a small "Sweeper" contract at each of the five blocked addresses (four Polymarket-linked, one Binance-linked). Balances and nonces are not changed by the install itself.
2. The attacker keys lose control. With contract code at those addresses, the keys can no longer send normal transactions or sign EIP-7702 authorizations from them.
3. Anyone can call sweep(), which moves the address's full native POL balance to a recovery address hard-coded in the client.
4. Incoming transfers revert. The Sweeper has no receive function, so POL sent to those five addresses after the fork will fail.
The two recovery addresses in the code are 0x3dcE0a29139A851Da1dFCa56Af8e8a6440b4D952 (Polymarket-linked funds) and 0xd9fD39103674CB061D64D9C3b73B878Dbe610b80 (Binance-linked funds). The PR does not list the five blocked addresses in full.
Who is affected
POL holders and wallet users
If you hold POL in your own wallet or on an exchange, your balance is not affected. You do not need to move, swap or "migrate" anything. Expect possible short deposit and withdrawal pauses on exchanges around the fork.
Node operators and validators
This is a consensus change. Any Bor node that has not upgraded to a Salvador-enabled release before block 98,350,200 will compute a different state root and fall off the canonical chain. The release version has not been announced yet.
Exchanges and custodians
Exchanges typically pause POL deposits and withdrawals around a hard fork. No exchange notices for the 2 December window have been published yet.
Developers
Amoy testnet is scheduled to activate first, at block 53,803,400. Teams running Amoy infrastructure should upgrade before then and use the testnet window to check tooling.
Upbit's 19 November POL pause is a separate event
According to TokenPost's report of Upbit's notice, Upbit will suspend deposits and withdrawals for POL, STEPN (GMT), JPYC and Polygon-based NFTs from 11:00 UTC (20:00 KST) on Thursday 19 November, citing a planned hard fork of the Polygon network. Trading continues, and resumption will be announced after stability checks. Other exchanges may publish similar notices; one report says HTX plans a pause from 12:00 UTC the same day, but we could not verify this from HTX directly.
Polygon has not publicly named a fork for 19 November. Its most recent Bor release, v2.11.1 on 16 November, was described as "not a hardfork," and the Uburu (Bor) and Karwar (Heimdall) forks already activated in early November. The 19 November pause is probably a separate upgrade, not Salvador. Plan around the dates each exchange announces.
Step-by-step checklist
For POL holders
1. Do nothing with your tokens. No swap or migration is needed.
2. Avoid exchange transfers around 19 November and 2 December. If you need to move POL to or from Upbit, finish before 11:00 UTC on 19 November or wait for the resumption notice.
3. Check your exchange's announcement page for exact pause windows.
4. Never send POL to an address you cannot verify. After Salvador, transfers to the five blocked addresses will revert.
For node operators
1. Watch the Bor repository and Polygon forum for the Salvador release.
2. Upgrade Amoy nodes before block 53,803,400.
3. Upgrade mainnet nodes before block 98,350,200, leaving a buffer for testing and restarts.
4. Make sure you are on Bor v2.11.1 now; Polygon advised operators on v2.11.0 to upgrade at their earliest convenience.
5. Monitor block progress and recalculate the estimated time as the fork approaches.
Similar node-upgrade deadlines are coming on other chains; see our guides to the BNB Chain Jenner hard fork and the Dash v24 hard fork.
Why this matters beyond Polygon
A fork that moves funds out of specific addresses is rare on a major EVM chain. Supporters see it as a way to return stolen funds without rolling back the chain. Critics in the forum thread raised concerns about the precedent it sets for intervening in balances. Similar governance-driven network changes, such as the Injective Veyra upgrade halt and the Cosmos Hub Gaia v29.1.0 upgrade, show how often users now need to track upgrade windows.
Frequently asked questions
What is the Polygon Salvador hard fork?
Salvador is a proposed Polygon PoS hard fork in pending Bor client code. It installs a Sweeper contract at five blocked attacker addresses so about 70.49 million POL can be moved to fixed recovery addresses.
When will Salvador activate?
The pending code sets Amoy testnet block 53,803,400 (estimated around 17:00 UTC on 25 November 2026) and mainnet block 98,350,200 (estimated around 17:00 UTC on 2 December 2026). These could change before release.
Do I need to do anything with my POL?
No. Ordinary POL balances are not changed. Exchanges may pause deposits and withdrawals around the fork, so plan transfers around their announced windows.
Is Upbit's 19 November pause for Salvador?
Probably not. Upbit cites a planned Polygon hard fork from 11:00 UTC on 19 November, but Polygon has not named a fork for that date and Salvador is set for 2 December on mainnet.
What happens to nodes that do not upgrade?
Bor nodes that are not running a Salvador-enabled release at the fork block will compute a different state and fall off the canonical chain.
Conclusion
Polygon's Salvador hard fork is still pending code, but it is concrete: proposed fork blocks are set for Amoy around 25 November and mainnet around 2 December 2026, with the aim of recovering about 70.49 million POL from blocked attacker addresses. POL holders do not need to act, apart from planning around exchange pauses such as Upbit's from 11:00 UTC on 19 November. Node operators should watch for the Salvador release and upgrade well before the fork block.
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 Polygon, Upbit or any exchange. We will never ask for your seed phrase, password 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.