Please be noted that the $aBNBc pool is now paused due to its recent exploit. Further updates will be posted on Twitter.

02 Dec 2022, 01:55
Please be noted that the $aBNBc pool is now paused due to its recent exploit. Further updates will be posted on Twitter.

Same news in other sources

5
02 Dec 2022, 12:42
Hey everyone, after the recent incident, many of you have asked about their staked assets on BNB-related pools, and we wanted to make a statement about the current state. 1- The hacker minted trillions of aBNBc tokens and dumped them indiscriminately across all DeFi platforms like Wombat, PCS, ApeSwap, etc. To be clear, this is an issue that affects multiple DeFi platforms on BNB Chain and not only Wombat. 2. As many of you realized, the Coverage Ratio of the pools dropped 1.1%. This was because the hacker swapped the aBNBc into WBNB, BNBx, and stkBNB. Per the documents, the Coverage Ratio = Asset / Liability Asset: the current token amount in the pool Liability: the token amount that has been staked by users So, in our case, only 1.1% of the total deposited funds to the BNB pool remain in the pool, and the rest are drained by hackers. While we have halted the swaps, deposit and withdrawals to contain further damage, the speed at which the hacker acted leaves us with a low coverage ratio. 3. Currently, Ankr team is working on compensating the users affected by the incident, and our team is communicating with all parties to help with the solution. Given how widely used aBNBc was in BNB Chain DeFi, this involves coordinating with lots of stakeholders. I know many of you are concerned about your funds; finding a way forward is a top priority for Wombat. I'm sure many other projects feel the same. Please stay tuned for the further updates ! For more details :
Hey everyone, after the recent incident, many of you have asked about their staked assets on BNB-related pools, and we wanted to
Hey everyone, after the recent incident, many of you have asked about their staked assets on BNB-related pools, and we wanted to make a statement about the current state. 1- The hacker minted trillions of aBNBc tokens and dumped them indiscriminately across all DeFi platforms like Wombat, PCS, ApeSwap, etc. To be clear, this is an issue that affects multiple DeFi platforms on BNB Chain and not only Wombat. 2. As many of you realized, the Coverage Ratio of the pools dropped 1.1%. This was because the hacker swapped the aBNBc into WBNB, BNBx, and stkBNB. Per the documents, the Coverage Ratio = Asset / Liability Asset: the current token amount in the pool Liability: the token amount that has been staked by users So, in our case, only 1.1% of the total deposited funds to the BNB pool remain in the pool, and the rest are drained by hackers. While we have halted the swaps, deposit and withdrawals to contain further damage, the speed at which the hacker acted leaves us with a low coverage ratio. 3. Currently, Ankr team is working on compensating the users affected by the incident, and our team is communicating with all parties to help with the solution. Given how widely used aBNBc was in BNB Chain DeFi, this involves coordinating with lots of stakeholders. I know many of you are concerned about your funds; finding a way forward is a top priority for Wombat. I'm sure many other projects feel the same. Please stay tuned for the further updates ! For more details : https://t.me/WombatExchange/110850
02 Dec 2022, 05:56
Update: BNB pool is now paused, swaps, deposits and withdrawls of $BNB, $BNBx, $stkBNB and $aBNBc are halted.
Update: BNB pool is now paused, swaps, deposits and withdrawls of $BNB, $BNBx, $stkBNB and $aBNBc are halted.
02 Dec 2022, 04:50
Due to the recent exploits with aBNBc, Side pool and BNB pool are now paused. FAQs below: What does it mean by pausing the pool? Users are not able to swap HAY, BUSD, BNB, stkBNB, BNBx or aBNBc to other assets as a prevention for the hacker for further draining the pool liquidity. Deposits for both Side and BNB pools are disabled, only withdrawals of Side Pool tokens (HAY & BUSD) are allowed. Pool emissions for the HAY & aBNBc are halted. What happened with aBNBc? The Ankr aBNBc contract is exploited and the hacker has minted an additional of 10 trillion aBNBc. He then dumped aBNBc and drained the DEX pools. The hacker minted trillions of aBNBc tokens and dumped them indiscriminately across all DeFi platforms like Wombat, PCS, ApeSwap, etc. To be clear, this is an issue that affects multiple DeFi platforms on BNB Chain and not only Wombat. Why HAY is affected in this exploit? aBNBc can be used as collateral on Helio to borrow HAY. In short, an exploiter borrowed HAY with the depegged aBNBC, and dumped HAY hence DEX pools are drained. What exactly happened on Wombat? As many of you realized, the Coverage Ratio of the pools dropped to 1.1%. This was because the hacker swapped the aBNBc into WBNB, BNBx, and stkBNB. Per the documents, the Coverage Ratio = Asset / Liability Asset: the current token amount in the pool Liability: the token amount that has been staked by users So, in our case, only 1.1% of the total deposited funds to the BNB pool remain in the pool, and the rest are drained by hackers. While we have halted the swaps, deposit and withdrawals to contain further damage, the speed at which the hacker acted leaves us with a low coverage ratio. What can you do if you wish to withdraw? *Updated as of 6AM UTC 2/12 You can choose to exit your HAY liquidity by withdrawing the assets. However, because of the extreme coverage ratio, there will be a withdrawal penalty charged which serves as a protection mechanism for the overall pool health, details can be read here: Please note that only withdrawals in the same token is allowed, i.e. a user can withdraw BUSD only if they have BUSD LP assets. Are there any recovery & compensation plans? We’re working with multiple protocols and the BNB Chain to come up with the best solution we can. Please be patient with us and we promise to give our community an update as soon as we have an update. Currently, Ankr team is working on compensating the users affected by the incident, and our team is communicating with all parties to help with the solution. Given how widely used aBNBc was in BNB Chain DeFi, this involves coordinating with lots of stakeholders. I know many of you are concerned about your funds; finding a way forward is a top priority for Wombat. I'm sure many other projects feel the same.
Due to the recent exploits with aBNBc, Side pool and BNB pool are now paused. FAQs below:.
Due to the recent exploits with aBNBc, Side pool and BNB pool are now paused. FAQs below: What does it mean by pausing the pool? Users are not able to swap HAY, BUSD, BNB, stkBNB, BNBx or aBNBc to other assets as a prevention for the hacker for further draining the pool liquidity. Deposits for both Side and BNB pools are disabled, only withdrawals of Side Pool tokens (HAY & BUSD) are allowed. Pool emissions for the HAY & aBNBc are halted. What happened with aBNBc? The Ankr aBNBc contract is exploited and the hacker has minted an additional of 10 trillion aBNBc. He then dumped aBNBc and drained the DEX pools. The hacker minted trillions of aBNBc tokens and dumped them indiscriminately across all DeFi platforms like Wombat, PCS, ApeSwap, etc. To be clear, this is an issue that affects multiple DeFi platforms on BNB Chain and not only Wombat. Why HAY is affected in this exploit? aBNBc can be used as collateral on Helio to borrow HAY. In short, an exploiter borrowed HAY with the depegged aBNBC, and dumped HAY hence DEX pools are drained. What exactly happened on Wombat? As many of you realized, the Coverage Ratio of the pools dropped to 1.1%. This was because the hacker swapped the aBNBc into WBNB, BNBx, and stkBNB. Per the documents, the Coverage Ratio = Asset / Liability Asset: the current token amount in the pool Liability: the token amount that has been staked by users So, in our case, only 1.1% of the total deposited funds to the BNB pool remain in the pool, and the rest are drained by hackers. While we have halted the swaps, deposit and withdrawals to contain further damage, the speed at which the hacker acted leaves us with a low coverage ratio. What can you do if you wish to withdraw? *Updated as of 6AM UTC 2/12 You can choose to exit your HAY liquidity by withdrawing the assets. However, because of the extreme coverage ratio, there will be a withdrawal penalty charged which serves as a protection mechanism for the overall pool health, details can be read here: https://docs.wombat.exchange/docs/concepts/fees/deposit-gain-and-withdrawal-fee Please note that only withdrawals in the same token is allowed, i.e. a user can withdraw BUSD only if they have BUSD LP assets. Are there any recovery & compensation plans? We’re working with multiple protocols and the BNB Chain to come up with the best solution we can. Please be patient with us and we promise to give our community an update as soon as we have an update. Currently, Ankr team is working on compensating the users affected by the incident, and our team is communicating with all parties to help with the solution. Given how widely used aBNBc was in BNB Chain DeFi, this involves coordinating with lots of stakeholders. I know many of you are concerned about your funds; finding a way forward is a top priority for Wombat. I'm sure many other projects feel the same.
02 Dec 2022, 03:45
Please note the withdrawal penalty if you wish to withdraw your assets from Wombat
Please note the withdrawal penalty if you wish to withdraw your assets from Wombat.
https://docs.wombat.exchange/docs/concepts/fees/deposit-gain-and-withdrawal-fee Please note the withdrawal penalty if you wish to withdraw your assets from Wombat
02 Dec 2022, 03:24
Update: $HAY pool has been paused due to the exploit. We will update the community as soon as we have more information.
Update: $HAY pool has been paused due to the exploit. We will update the community as soon as we have more information.
Update: $HAY pool has been paused due to the exploit. We will update the community as soon as we have more information.