OpenSea’s UI exploit saga is gradually settling down as the company reportedly compensated the victims. However, several users are complaining that they are yet to hear from OpenSea and have not received any compensation for their losses. Apparently, OpenSea stopped responding to the victims of the delisting bug.
A Twitter user is still waiting for OpenSea to compensate him for a missing Mutant Ape, while another user is missing a Bored Ape. Both users have contacted the NFT marketplace and have waited for more than a week without any response. Imagine the agony.
OpenSea’s fix
OpenSea started to refund victims towards the end of January 2022. The company reportedly refunded a total of 750 ETH to the affected parties, in addition to rolling out a UI fix to prevent future occurrence. OpenSea Support announced these updates on Twitter as they were being implemented on the marketplace.
In a continuous effort to improve the system, OpenSea is transitioning to a new smart contract on 18 February 2022. This new update will ensure that old listings will expire and consequently prevent the exploit from happening again. However, users with old listings are encouraged to manually remove any listings to be on the safe side.
The compensation made waves around the NFT community and seemed to have calmed the waves, until the public outcries of those left behind. Currently, the team has not responded to any of the tweets above. One user attributed this to his low social media influence, causing him to be treated as low priority.
Are you tired of missing important NFT drops?
Just check out our NFT Calendar !
Subscribe to our hot social media and don’t miss anything else
If you’re old school :
All investment/financial opinions expressed by NFTevening.com are not recommendations.
This article is educational material.
As always, make your own research prior to making any kind of investments.
Owners, holders, fans, community members, whales… Want to boost this article by featuring it on top of the Homepage? ==> Contact us!
Comments (No)