The purpose of this proposal is to address a potential issue that could cause problems with the existing NZDS/USDC LP via Ethereum and Polygon.
After the exploitation, many of the tokens were able to be frozen and or recovered. However, NZDS was the only one that was unable to be frozen because the 'attacker' had already sent them to Polygons bridge. Since those tokens are on a separate contract, they are unable to be frozen like they could have been if they would have just stayed ETH native.
Some may be asking, I thought it was only going to be for Polygon? 🤔
The original forum proposal was only going to include Polygon. However, it was brought up that the Polygon bridge contract is not on the black list. This means that the attacker could bridge back the exploited NZDS and try to use it through the DFX protocol. So for the safety/security of our users, until the issue of the 'wild' NZDS is resolved, rewards to both chains (Ethereum & Polygon) should be halted. (for the time being).
The attackers wallet holds 820,042.86 NZDS and can be found at this link -> https://polygonscan.com/token/0xeafe31cd9e8e01c8f0073a2c974f728fb80e9dce?a=0x14c19962e4a899f29b3dd9ff52ebfb5e4cb9a067
At the current moment, no rewards are being issued out from the protocol. However, the relaunch is coming up at the tail end of January. So, the protocol needs to iron this issue out before then in order to not only properly distribute the LP emissions/rewards for normal operations but most importantly for taking every step possible to make sure the users in the liquidity pools are safe and secure. 🔒
Pause emission of DFX rewards to Polygon NZDS pools using bridged contract address 0xeaFE31Cd9e8E01C8f0073A2C974f728Fb80e9DcE
Pause emission of DFX rewards to Ethereum NZDS pools if Polygon bridge contract 0xDa446fAd08277B4D2591536F204E018f32B6831c is not on the blacklist.