Ledger CEO Confronts Mt. Gox Former CEO Over Alleged Disclosure Failures

iconKuCoinFlash
Share
AI summary iconSummary
Former Mt. Gox CEO Mark Karpelès accused Ledger of failing to disclose issues in a timely manner, claiming it may have resulted in over $90 million in losses. He also expressed concerns about Ledger’s handling of advanced embedded devices. Ledger CEO Pascal Gauthier pushed back, stating that the company has always prioritized user protection and urged Karpelès to stick to the facts. On-chain data continues to show mixed signals for altcoins to watch amid the ongoing dispute.

Odaily Planet Daily reports: Mark Karpelès, former CEO of Mt. Gox, posted on X accusing Ledger that if it had disclosed the related issues more promptly and effectively—rather than merely publishing an inconspicuous article on Ledger Academy—it might have prevented losses exceeding $90 million. He also questioned why Ledger did not maintain sufficient vigilance regarding the mass-produced advanced implant devices.

In response, Ledger CEO Pascal Gauthier questioned Mark Karpelès’s stance, stating that Ledger has always done everything possible to protect users. He acknowledged the extreme challenges of security work and recognized Karpelès’s concern over the matter, but urged him to base his statements on known facts rather than speculation, adding sarcastically, “Come on, you’re not a white knight—get real.”

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.