ALERT: ICON (ICX) is facing a lawsuit and they've been censoring people asking about it and exposing questionable action on their network

Back in August, Icon claimed a hacker was able to mint 20 million ICX tokens exploiting some vulnerability in ICX's code. More recently, a lawsuit's been filed against them, which they've been censoring on social media. They blocked me on Telegram for posting a link and asking questions about it while also removing any traces of it so others can't see.For example, one of their own developers/mods even chimed in comparing the recent bug as worse than the eth dao hack and suggested Icon's not decentralized as it seems:https://ift.tt/3jJXn20 people made similar comments and one of the mods promptly removed their posts. When someone noted that this bug is pretty serious even for crypto standards (multiple users freely minting 20 million ICX tokens which is $6 million today, $250 million at ATH), the mod brushed it off as "it's software, happens no matter what".People also asked if the Icon foundation did manage to get back the stolen funds as promised and the mod deflected the question yet again. If they retrieved the funds, why are there no transactions from the wallet in question since or the promised token burn? Not a single person from Icon has been able to tell me "I can assure you funds are safe". Others have asked about it and most questions were left unanswered.No one's been able to give me a clear answer so that tells me either a) they're hiding something or b) they lied about retrieving all the funds back and now they're trying to figure out a way to hush it all up. It's very unsettling when they're faced with a lawsuit and censoring fair questions about it, yet alone when even one of your own developers and mod agree these are serious concerns (the other mod censored him too lol). If y'all ICX folks are clean as you say, then provide some proof and prove me wrong. Otherwise, it's looking extremely sketch and we can only assume otherwise.

Submitted October 31, 2020 at 04:48AM

No comments:

Post a Comment