Kraken Accused by SEC of Operating Unregistered Platform, Improperly Mixing Customer Funds

CoinDeskPolicy發佈於 2023-11-19更新於 2023-11-20

文章摘要

The U.S. crypto exchange is the latest targeted by the Securities and Exchange Commission in a series of similar actions being fought in court by other companies.

Crypto exchange Kraken commingled customer and corporate funds while operating as an unregistered broker, clearing agency and dealer, the U.S. Securities and Exchange Commission (SEC) alleged in a new lawsuit Monday.

The federal regulator claimed that the San Francisco-based company violated federal securities laws in a repeat of its suits against other crypto trading platforms. Unique to Monday's lawsuit are claims that Kraken created a "significant risk" by commingling up to $33 billion in customer crypto with its own corporate assets, the regulator said, quoting Kraken's independent auditor.

10

"Similarly, Kraken has held at times more than $5 billion worth of its customers’ cash, and it also commingles some of its customers’ cash with some of its own," the suit said. "In fact, Kraken has at times paid operational expenses directly from bank accounts that hold customer cash."

Advertisement
Advertisement

The SEC claims that Kraken simultaneously operates an unregistered broker, clearinghouse and exchange echoes its complaints against Binance and Coinbase, two exchanges the agency sued earlier this year.

Those suits are continuing. The SEC previously settled similar allegations against Bittrex's now-shuttered U.S. wing.

The federal regulator, as it has with those previous suits, listed a number of tokens it deemed to be unregistered securities, including the Algorand token (ALGO), Polygon's MATIC and NEAR.

Edited by Jesse Hamilton.


你可能也喜歡

大神Karpathy用Claude的方式,原来是这样的?

AI大神安德烈·卡帕西(Andrej Karpathy)在加入Anthropic后,开源活动减少。近期,一份据称是他本人使用的`CLAUDE.md`文件在社区流传,旨在指导Claude AI进行更高效的编程协作。该文件强调了一系列核心原则,并非简单建议而是必须遵守的规则,以规避大语言模型写代码时的常见错误。 核心原则包括: 1. **写之前先读**:在编写新代码前,务必认真阅读现有代码库,理解项目风格、既有模式和工具,确保新代码与项目保持一致。 2. **写代码之前先想清楚**:明确任务需求、澄清假设、说明方案取舍,避免基于模糊理解生成错误代码。 3. **保持简单**:抵制过度设计,避免过早抽象、臆想式错误处理和不必要的配置,编写能解决当前问题的最少代码。 4. **外科手术式修改**:修改代码时力求改动范围最小,严格匹配项目现有风格,只清理自己引入的问题,避免无谓的重构和格式化。 5. **验证**:重视测试,修复bug前先写测试复现,确保改动不破坏现有功能。 6. **目标驱动执行**:将模糊任务转化为可验证的具体步骤,并在执行前说明计划。 7. **调试**:遇到问题先深入调查、复现,理解根因,避免盲目添加临时解决方案。 8. **谨慎管理依赖**:添加新依赖前,优先考虑使用现有工具或标准库,并评估其维护状态和成本。 9. **有效沟通**:清晰说明改动内容和原因,主动指出潜在隐患和不确定之处。 文章指出,尽管这份文件的真实性存疑,但其内容高度契合卡帕西本人关于AI编程助手的公开观点。社区已据此提炼出原则并制作了模板,有测试表明能显著降低Claude的代码错误率。这些准则被认为是提升AI辅助编程效率、保证代码质量的关键。

marsbit1 小時前

大神Karpathy用Claude的方式,原来是这样的?

marsbit1 小時前

交易

現貨
活动图片