出典確認済みリサーチ: Basel Sco60 Cryptoasset Exposure
本文は確認済みの英語原文で表示しています。翻訳版は出典確認後に追加します。
NexuAlpha direct answer: The Basel Framework's SCO60 chapter is current from 1 January 2026 and sets prudential treatment for banks' cryptoasset exposures. It distinguishes classification conditions, Group 1 and Group 2 treatment, market and credit risk, counterparty credit risk, liquidity risk and operational risk. For market users, the relevant decision is not a price forecast; it is whether a bank-facing product, custody route or tokenized exposure can identify which Basel category and capital treatment would apply.
閉じる
Decision outcome: Before treating bank participation as de-risking a crypto product, map the asset classification, redemption and stabilization mechanism, legal enforceability, issuer and reserve claim, hedge eligibility, counterparty exposure, infrastructure-risk add-on, operational controls and whether the bank's local regulator has implemented the standard without material differences.
Evidence snapshot. This article was researched at 2026-09-21T23:42:09.751Z using Bank for International Settlements, Basel Committee on Banking Supervision, Hong Kong Monetary Authority. A local queue, old generated draft, search snippet, social repost, price chart or AI summary was not treated as proof. Those surfaces can suggest a question, but every material claim below maps to the public source list for this article.
記事の表：横にスクロールするか、表の領域にフォーカスして矢印キーを使ってください。
| Decision checkpoint | Evidence to read | Stop condition |
|---|---|---|
| Official object | Basel SCO60, cryptoasset exposures, Group 1 cryptoassets | the source cannot name the exact venue, report, rule, account surface or control |
| User boundary | account, key, venue, wallet, asset, issuer, counterparty or jurisdiction state | the user's state differs from the public source |
| Failure handling | throttle, retry, fallback, notice, record, disclosure or support path | the recovery process is undefined or secret-dependent |
| Rights and permissions | source-mapped eligibility, exemptions, limits, locks, records or scopes | the action depends on an inferred right or hidden permission |
| Evidence log | URL, access time, selected setting and non-secret stop rule | proof would expose credentials, balances, identity documents or private keys |
Verified facts. Claim c1: The BIS Basel Framework page for SCO60 says the cryptoasset exposures chapter is current and effective as of 1 January 2026. Claim c2: SCO60 sets out prudential treatment for banks' exposures to cryptoassets, including classification conditions, minimum capital requirements and liquidity risk requirements. Claim c3: The Basel Committee amendments page says targeted amendments to the cryptoasset prudential standard were finalized and the final revised standard was to be implemented by 1 January 2026. Claim c4: The original prudential treatment document and jurisdictional consultation material provide implementation context but do not prove any specific bank product is approved for a user. These facts are deliberately narrow. They do not prove personal eligibility, future availability, execution quality, legal status beyond the cited wording, tax treatment, account approval, customer support outcome, redemption success, price direction, liquidity depth or platform solvency.
Decision discipline for Basel SCO60 cryptoasset exposure standard bank capital implementation map. The useful answer is not a universal winner. It is a source-bound scorecard: which official source answers the immediate question, which control is blank, which blank changes user risk, which test is reversible and which condition reopens the decision. An honest blank is safer than an invented advantage.
FAQ. What is the short answer? The Basel Framework's SCO60 chapter is current from 1 January 2026 and sets prudential treatment for banks' cryptoasset exposures. What should be verified first? Verify the official source and the exact control surface. What should not be inferred? Do not infer eligibility, future support, legal treatment, tax treatment, recovery, execution quality, liquidity, redemption, consumer protection or account approval. When should the user stop? Stop when source, object, user state, permission, route, issuer, jurisdiction or failure handling is unclear.