Canadian Regulator Seeks Feedback on Disclosure Rules for Bank Crypto Exposures

CoinDeskPolicy2023-11-20 tarihinde yayınlandı2023-11-21 tarihinde güncellendi

Özet

The country hopes to align local requirements with those proposed by international banking regulators.

Canada's Office of the Superintendent of Financial Institutions (OSFI) is seeking feedback on disclosure requirements for local banks and insurers exposed to crypto, according to a Monday notice.

The consultation complements another on the same subject underway by international standard-setter, the Basel Committee on Banking Supervision (BCBS).

3K

"We are running our consultation in parallel. We intend to combine your feedback with developments coming out of the BCBS. This will help us articulate public disclosure expectations appropriate for banks and insurers in Canada," the OSFI said.

Advertisement
Advertisement

The Canadian regulator wants to know which technical aspects of the BCBS requirements should be adjusted to fit a local context and key considerations for ensuring "proportionality of disclosures."

The BCBS has said banks must disclose any exposure to crypto and has proposed the highest possible risk weight of 1250% for volatile assets like bitcoin.

The public can submit comments on the requirements to OSFI until Jan. 31, 2024.

Edited by Oliver Knight.

İlgili Okumalar

BIT Research: The 2028 Halving Is Not the End, the Real Shake-Up of the Bitcoin Mining Industry Is Just Beginning

The Bitcoin mining industry is undergoing its most complex structural adjustment since inception. Despite Bitcoin's price holding near $61,000 and the network hash rate approaching a record 1 ZH/s, miner profitability is deteriorating. The industry is operating close to its breakeven point, with the 2028 halving expected to accelerate consolidation. The challenges extend beyond the halving's subsidy reduction; the industry's revenue model has yet to successfully transition towards a fee-driven structure. Increasingly, mining companies are evolving from simple Bitcoin producers into infrastructure and energy operators, including providers of AI/HPC computing power. Competition is shifting from pure hash rate expansion to business model upgrades. Economic pressure is evident. The theoretical daily mining revenue at current prices is around $78 million, yet the actual figure is only about $33 million—a 136% gap. Transaction fees remain low at roughly $220k daily, far below historical implied levels. With a current estimated industry-wide breakeven price near $65,000, mining alone is struggling to generate ideal profits. The 2028 halving is projected to push the fundamental production cost floor to approximately $93,289. This will likely accelerate a shift towards consolidation among larger, well-capitalized miners with diversified revenue streams. Competitive advantage will belong to institutionalized players with access to low-cost energy, AI/HPC hosting operations, and stronger balance sheets. In essence, Bitcoin mining is transitioning from a "mining business" to an "infrastructure business." Future profitability and resilience will depend less on block rewards and more on diversified income sources like energy management and computational infrastructure services. For investors, the key question is not the halving itself, but which miners can successfully navigate this business model transformation.

marsbit1 saat önce

BIT Research: The 2028 Halving Is Not the End, the Real Shake-Up of the Bitcoin Mining Industry Is Just Beginning

marsbit1 saat önce

This is How God Karpathy Uses Claude?

Andrej Karpathy, a prominent figure in AI, has reportedly joined Anthropic, leading to a noticeable decrease in his open-source contributions and social media activity. A document claiming to be his personal "CLAUDE.md" file—a set of instructions for the Claude AI to follow within a specific codebase—has been circulating online. While its authenticity is unverified, the content aligns closely with Karpathy's publicly shared principles on effective AI-assisted programming. The document outlines key rules for AI coding assistants, emphasizing the importance of reading existing code thoroughly before writing new code to maintain consistency. It advises against over-engineering, advocating for simple, surgical modifications that match the project's existing style. Other guidelines include clarifying assumptions upfront, writing meaningful tests, thoughtful debugging, and carefully considering dependencies. The core message is that these principles help prevent common AI coding failures, such as introducing unnecessary abstractions, style drift, or making invisible architectural decisions. The community has noted that even experts like Karpathy require detailed instructions to guide AI effectively, akin to managing a junior developer. A related GitHub repository, "andrej-karpathy-skills," which encapsulates these ideas, is reported to significantly reduce Claude's code error rate. Ultimately, the advice stresses that the best CLAUDE.md is tailored to one's own tech stack and coding practices.

marsbit1 saat önce

This is How God Karpathy Uses Claude?

marsbit1 saat önce

İşlemler

Spot
活动图片