🚀 BIS And Central Banks Discuss Legal Issues And CBDC System Design
#BIS #CentralBanks #CBDC #DigitalCurrency #LegalIssues #SystemDesign #Privacy #Cybersecurity #ModularDesign #Innovation
According to Odaily, the Bank for International Settlements (BIS) and several central banks have recently published a paper addressing legal issues and the design of Central Bank Digital Currency (CBDC) systems. The participating central banks include the Bank of Canada, the Bank of England, the Bank of Japan, the European Central Bank, the Federal Reserve Board, the Swedish Riksbank, and the Swiss National Bank.
One of the key debates highlighted in the paper is whether CBDC systems should adopt a centralized or decentralized model. In a two-tier system, one option is the hub-and-spoke model, where updates are controlled by the central bank, but data ownership is decentralized. Alternatively, a peer-to-peer design could be implemented, allowing shared update permissions. The paper notes that centralized systems tend to have weaker resilience due to single points of failure, which could become bottlenecks. However, the authors do not consider it appropriate to decentralize the core settlement authority of CBDC systems. In a modular design, core settlement can remain centralized, while other aspects, such as identity, can be decentralized.
Privacy is another significant issue facing CBDCs. While existing technologies can achieve privacy, newer privacy-enhancing technologies (PETs), such as Secure Multi-Party Computation (SMPC) or Zero-Knowledge Proofs (ZKP), offer greater flexibility. However, based on the experiences of two central banks and the BIS Innovation Hub, there is skepticism about whether PETs are ready for real-time execution, given concerns about their complexity and reliability.
The paper also explores other topics, including cybersecurity, offline CBDC functionality, and compatibility with existing point-of-sale systems. These discussions are crucial as central banks worldwide continue to explore the potential implementation of CBDCs, balancing innovation with security and privacy considerations.#BIS #CentralBanks #CBDC #DigitalCurrency #LegalIssues #SystemDesign #Privacy #Cybersecurity #ModularDesign #Innovation
🚀 Anthropic Introduces Official AI Certification: Claude Certified Architect
#Anthropic #AI #ClaudeCertifiedArchitect #Certification #AIarchitecture #SystemDesign #ProductionApplications #TechCredential #CFA
PANews posted on X (formerly Twitter). Anthropic has launched its first official AI certification, the Claude Certified Architect (CCA). This certification focuses on system architecture design and assesses the ability to build production-level applications. The examination process is closely monitored, ensuring a rigorous evaluation of candidates' skills. The CCA certification is designed to be a notable credential, comparable to the CFA, and can be prominently featured on resumes.#Anthropic #AI #ClaudeCertifiedArchitect #Certification #AIarchitecture #SystemDesign #ProductionApplications #TechCredential #CFA
🚀 Monad Co-Founder Releases Security Checklist for Protocols
#Monad #SecurityChecklist #Protocols #AdministratorPermissions #FundSecurity #MultiSignature #ColdDevices #MalwareDetection #TransactionHashes #ExtremeScenarios #SystemDesign #TimeLocks #RealTimeMonitoring
Monad co-founder Keone Hon has shared a security self-checklist for protocols on the X platform. According to Odaily, the checklist focuses on key issues such as management permissions, fund security, and multi-signature mechanism design. It includes ten main points:
1. Identify which administrator functions could lead to fund loss.
2. Ensure all related operations have time locks.
3. Establish a real-time monitoring mechanism.
4. Provide timely alerts when administrator functions are called.
5. Review all privileged accounts and adopt a multi-signature (k-of-n) structure where possible.
6. Define signature threshold parameters clearly.
7. Multi-signature signers should use independent cold devices solely for signing operations and follow best practices, such as independently verifying transaction hashes.
8. Set withdrawal rate limits and avoid control by the same multi-signature.
9. Ensure employee devices have malware detection and management capabilities.
10. Prepare for extreme scenarios where multi-signature signers are compromised, reverse-engineer potential attack paths from an attacker's perspective, and optimize system design to increase attack cost and complexity.#Monad #SecurityChecklist #Protocols #AdministratorPermissions #FundSecurity #MultiSignature #ColdDevices #MalwareDetection #TransactionHashes #ExtremeScenarios #SystemDesign #TimeLocks #RealTimeMonitoring