UK Publishes Regulations for a Digital Securities Sandbox

CoinDeskPolicy发布于2023-12-17更新于2023-12-18

文章摘要

The sandbox will let regulators and companies test solutions, including distributed ledger technology, to tokenize securities.

The U.K. has introduced a new regulation that will allow the country’s financial watchdogs to run a sandbox for tokenized securities, according to a Monday publication.

Sandboxes let companies test new solutions and products under regulatory supervision. With the new regulation – which will take effect on Jan. 8 – the Financial Conduct Authority (FCA) and the Bank of England will be able to operate the Digital Securities Sandbox (DSS), announced earlier this year.

6.6K

Businesses will also get to test distributed ledger technology that powers crypto to digitize or tokenize traditional securities.

Advertisement
Advertisement

Tokenization of real assets is all the rage among financial institutions worldwide, and U.K. regulators are trying to figure out how best to regulate them. Participating in the DSS will subject companies to modified rules in case current ones act as barriers, a document explaining the law said. The regulators themselves will be able to test out things and make rule changes to accommodate developing technologies.

The U.K. is not wasting time using its new powers under the recently passed Financial Services and Markets Act 2023 to establish how it wants to regulate the crypto sector. The DSS regulation is a by-product of the Act.

Edited by Sandali Handagama.

你可能也喜欢

大神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小时前

交易

现货
活动图片