Polygon's Strategy to Recover 70 Million POL Tokens Without Consent of Wallet Owners

Polygon's Recovery Plan for Stolen POL Tokens

In an ambitious plan aimed at recovering approximately 70 million POL tokens, Polygon seeks to transfer coins from five wallets linked to hacking incidents, all without requiring the consent of the wallet owners. This strategy involves leveraging network governance and validators to execute the recovery of stolen funds according to preset rules.

Details of the Proposal

The November 4 proposal specifically identifies five wallet addresses connected to stolen assets from breaches concerning the prediction market platform Polymarket and the cryptocurrency exchange Binance. The historical reference points within the proposal suggest that around 24 million POL belong to four addresses tied to Polymarket, while another 47 million POL is associated with a single address from Binance. However, it’s crucial to note that the actual recovery proceeds will depend on account balances at the moment of system activation rather than these historical figures.

As of November 9, details surrounding the activation block and the name of the recovery fork remained unresolved, according to the proposal’s publishing. Initial agendas from the governance meeting on November 5 included discussions about this recovery plan but no final approval has yet been recorded. Additionally, a separate software release, Bor v2.11.0, has implemented modifications from Uburu's StateReceiver, which does not pertain to the recovery initiative at hand.

Implementation of the Recovery Mechanism

Implementing the proposed recovery mechanism entails the updated software resetting the balance of each identified address to zero right before activation, simultaneously crediting the equivalent amount to a designated recovery address. This is designed to occur ahead of any transaction processing within the same activation block. Crucially, the overall supply of POL tokens would remain unchanged, and previous chain histories would not be affected. The proposal emphasizes the need for Bor engineering to verify this design before proceeding.

The governance framework will determine recovery authority, relying on the list of specific addresses identified, and software rules adopted by validators. The affected organizations will play a role in designating appropriate recipients, and Polygon Labs will verify proof of control for receivers. Notably, the proposal outlines that recovery efforts will not necessitate signatures from the original wallet holders.

Challenges and Considerations

Tracing stolen coins forms a key aspect of the recovery rationale, but the proposal sounds a note of caution: misidentification of hacker-controlled addresses might inadvertently result in the distribution of legitimate balances. To qualify as recipients, addresses must provide proof of ownership, such as a signed message or a minor test transfer authenticated by Polygon Labs, along with written confirmation associating the address with the intended recipient. Furthermore, the recovery plan is limited to native POL tokens and does not encompass other cryptocurrencies or different categories of addresses that are blocked.

Another consideration arises from the full-balance recovery protocol, as future deposits to these wallets would also be affected by the design. Increased scrutiny on balances before activation and the requirement for public disclosures on any balance adjustments are stipulated.

For exchanges and custodians, the proposed protocol results in discrepancies between the balances displayed by updated nodes and those inferred from standard transaction history. This potential inconsistency has been acknowledged within the proposal as problematic for explorers, indexers, and accounting mechanisms. A thorough reconciliation process would be necessary to link every impacted source address, its pre-activation balance, the chosen recipient, and their corresponding allocation at the activation block.

Next Steps and Customer Reimbursement

To tackle these complexities, the plan includes testing that ensures stability in total supply and that unrelated accounts are not altered, ultimately leading to a mainnet-fork replay. After activation, there will also be a commitment to release a verification script alongside published records detailing the transaction-free balance adjustments, enabling operators to assess the changes made against the approved framework.

The process of reimbursing customers remains distinct from the recovery effort. Following an incident on October 30, Polymarket reported that it had fully reimbursed 95% of the affected wallets within the same day, returning around $4 million, which included funds lost during the pause period. The current recovery proposal aims to return assets specifically to designated recovery addresses chosen by the companies involved.

In summary, moving forward, the next significant steps hinge on governance decisions, finalizing software specifications, confirming recipient addresses, and determining the activation block.