Neutrality & Non-Affiliation Notice:
The term “USD1” on this website is used only in its generic and descriptive sense—namely, any digital token stably redeemable 1 : 1 for U.S. dollars. This site is independent and not affiliated with, endorsed by, or sponsored by any current or future issuers of “USD1”-branded stablecoins.

Welcome to USD1courses.com

USD1courses.com is an educational site about USD1 stablecoins (digital tokens designed to be redeemable one-for-one for U.S. dollars and to keep their market price close to one U.S. dollar). The phrase USD1 stablecoins is used here in a generic, descriptive sense: it refers to any dollar-redeemable stable token, not a specific issuer, platform, or product.

If you are new to this topic, you will run into two worlds at once: money and software. A strong course helps you build a mental model that covers both. That means understanding how value is supported by reserves, how transfers settle on a blockchain (a shared ledger maintained by a network of computers), and how rules differ across jurisdictions. Many regulators and standard-setting bodies have published frameworks and guidance on stablecoins and broader crypto-asset (a digital asset recorded and transferred using cryptographic systems, often on blockchains) markets, and those sources are a solid foundation for serious learning.[1][2]

This page explains what "courses" can look like in the context of USD1 stablecoins, what core topics matter most, and how to evaluate learning materials so you can separate practical instruction from noise. It is for education only and is not legal, tax, or investment advice.

Overview

A course about USD1 stablecoins is not just a "how to send tokens" tutorial. It is a structured way to learn:

  • Mechanics: how issuance (creating new tokens), redemption (exchanging tokens back for U.S. dollars), and transfers work.
  • Risk: how a token can lose its peg (when the market price drifts away from one U.S. dollar), and what operational failures look like.
  • Controls: how custody (who controls the wallet or account) and security practices reduce avoidable loss.
  • Compliance: how AML (anti-money laundering) expectations, sanctions screening (checking against restricted-party lists), and reporting duties can apply.
  • Decision-making: how to compare designs and claims using evidence, not marketing.

Because USD1 stablecoins are designed to track the U.S. dollar, people often assume they are "simple." In practice, they can be simple to use at the surface and still complex under the hood. Complexity shows up in reserve design, legal terms, operational processes, smart contracts (software on a blockchain that can move funds based on rules), and the way different intermediaries interact.

A well-built course makes that complexity manageable. It introduces terms in plain English, uses real workflows, and links technical details to real-world outcomes. It also gives learners a habit that matters more than any one tip: verify claims with primary sources.

What you will learn

Most learners come to USD1 stablecoins with one of three goals:

  1. Personal understanding: You want to know what you are holding and what could go wrong.
  2. Professional capability: You need to support payments, treasury operations, customer support, or compliance in a business.
  3. Technical implementation: You are building software that accepts, stores, or moves USD1 stablecoins.

Courses can be organized to match these goals. Regardless of track, strong learning materials tend to deliver a set of durable skills:

  • Explain, in your own words, how USD1 stablecoins are supposed to maintain a one-dollar value.
  • Identify the difference between on-chain (recorded directly on a blockchain) activity and off-chain (recorded in traditional systems outside the blockchain) promises.
  • Read and interpret a reserve disclosure or attestation (a third-party assurance report) without over-trusting it.
  • Choose a custody model that matches your risk tolerance and operational needs.
  • Recognize common fraud patterns like fake support messages, address substitution, and phishing (tricking you into revealing secrets).
  • Understand why regulators emphasize governance (how decisions are made and controlled), risk management, and disclosure for stablecoin arrangements.[1][4]

You should also expect a good course to be clear about what it does not cover. For example, a foundation course can explain how pricing and redemption work, but it will not turn you into a lawyer, auditor, or security engineer. A clear scope is a sign of a trustworthy curriculum.

Learning paths

Below are common learning paths that a course library on USD1courses.com might support. Treat these as maps rather than rigid programs.

Path 1: Foundations

This path is for beginners and for experienced professionals who want a clean mental model. It typically covers:

  • What USD1 stablecoins are and why they exist.
  • Basic blockchain concepts, including addresses (public identifiers for accounts) and transaction fees (payments to network operators for processing transfers).
  • The idea of a peg (a target price relationship) and what can break it.
  • What to look for in disclosures, terms, and risk statements.

If you complete only one course, make it this one. It will help you understand later material and also help you ask better questions.

Path 2: Payments and operations

This path focuses on how USD1 stablecoins move through real systems:

  • Payment flows (how a payer sends value and a payee receives it) and settlement (when a transfer is considered final).
  • Reconciliation (matching records across systems) for on-chain transactions and bank statements.
  • Chargebacks versus irreversibility: card payments can be reversed, while many blockchain transfers cannot.
  • Customer support and incident response: what to do when a transfer is stuck or sent to the wrong address.

Path 3: Compliance and risk

This path is for compliance teams, risk managers, and product owners. It focuses on:

  • KYC (know-your-customer identity checks) and AML controls for relevant intermediaries.
  • The Travel Rule (a standard that calls for certain sender and recipient information to accompany some transfers), and how it is implemented for virtual assets in many jurisdictions.[3]
  • Sanctions screening, transaction monitoring, and recordkeeping.
  • Cross-border considerations and the limits of "one size fits all" rules.

International bodies such as the FATF (an intergovernmental standard-setter for anti-money laundering and counter-terrorist financing) provide guidance that many countries use as a baseline when writing local rules.[3]

Path 4: Developer and security

This path is for engineers and security practitioners:

  • Wallet architecture: custodial wallets (where a provider controls keys on your behalf) and non-custodial wallets (where you control the private keys).
  • Private keys (secrets that authorize spending) and seed phrases (word lists that can restore a wallet).
  • Smart contract interactions, token standards (shared technical rules for how tokens behave), and safe integration patterns.
  • Monitoring, logging, and incident response aligned with common cybersecurity frameworks such as the NIST Cybersecurity Framework (a widely used set of outcomes for managing cyber risk).[8]

Path 5: Policy and product

This path is for people who translate between teams:

  • How stablecoin arrangements can raise financial stability (the ability of the financial system to keep functioning under stress) concerns at scale.[1]
  • The role of governance, disclosures, and oversight.
  • How rules like the European Union Markets in Crypto-Assets Regulation (a European Union rulebook commonly shortened to MiCA) shape stablecoin-like tokens in the EU.[5][6]
  • How banking standards treat crypto-asset exposures in regulated institutions.[10]

Core concepts

This section outlines the concepts that almost every course about USD1 stablecoins should cover. Think of it as shared ground, even if your end goal is compliance or software development.

1) Issuance and redemption

Issuance (creating new units) and redemption (exchanging units back for U.S. dollars) are at the center of most USD1 stablecoins.

In a typical reserve-backed model, an issuer (the entity that creates and redeems the token) issues new units when it receives dollars and redeems units when a holder returns them for dollars. The issuer holds reserve assets (cash or cash-like holdings intended to support redemptions) to meet those requests.

A course should explain that details shape risk:

  • Who can redeem directly: everyone, only certain customers, or only intermediaries?
  • What are the redemption terms: delays, fees, minimum amounts, or limits?
  • What are reserve assets made of, and how liquid (how easily they can be converted to cash without significant price impact) are they?

These details have direct impact on outcomes, especially under stress. Public-sector reports often note that stablecoin arrangements can face run risk (the danger that many holders try to redeem at the same time), similar in spirit to other forms of short-term money.[4]

2) Price stability and the peg

A peg is not a guarantee. A course should explain the mechanisms that can keep a one-dollar value and the reasons those mechanisms can fail.

Common stabilizing factors include:

  • Redemption access: if holders can reliably redeem for dollars, market prices tend to stay close to one dollar.
  • Arbitrage (profiting from price differences): traders may buy discounted units and redeem them, which can push prices back toward the peg.
  • Transparency: clear, frequent reserve disclosures can support confidence, though transparency alone is not a substitute for sound design.

Common failure points include:

  • Unclear or restrictive redemption processes.
  • Reserve assets that are risky, illiquid, or poorly managed.
  • Operational failures, legal disputes, or loss of confidence.
  • Technology failures, including smart contract vulnerabilities.

3) On-chain versus off-chain reality

A useful mental model is to separate what happens on-chain from what happens off-chain.

  • On-chain: token transfers recorded on a blockchain, visible to network participants.
  • Off-chain: bank accounts, legal agreements, reserve custody arrangements, and internal control processes that are not visible on a blockchain.

Courses that ignore the off-chain side often leave learners with an incomplete picture. If a USD1 stablecoins arrangement claims to be redeemable for dollars, the redeemability depends on off-chain institutions, legal rights, and operational processes, not only on token code.

4) Intermediaries and roles

Even when you use a non-custodial wallet, you may still rely on intermediaries:

  • Exchanges (platforms that match buyers and sellers).
  • Wallet providers (software and services that help manage keys).
  • Payment processors (services that help merchants accept payments).
  • Banks and custodians (institutions that hold reserve assets).

A course should clarify which role does what, because responsibility and risk often sit at the boundaries. Regulatory guidance frequently emphasizes governance and clear allocation of responsibilities across a stablecoin arrangement.[1]

5) Disclosure and assurance

You will hear terms such as:

  • Proof of reserves (evidence about assets held to support redemptions).
  • Attestation (a limited-scope assurance report, often periodic).
  • Audit (a broader examination of financial statements under established standards).

A good course explains these terms in plain language and teaches you how to read them skeptically. For example, an attestation might cover a particular date rather than continuous coverage. It might also focus on certain balances without fully addressing liquidity under stress. This does not make attestations useless; it means you should know what question each document answers and what it does not answer.

Wallets and custody

Wallet terminology is overloaded, so courses should be explicit.

A wallet is software or hardware that helps you manage an address and sign transactions. Signing (cryptographically authorizing a transfer) normally needs a private key. If you lose the private key or seed phrase, you usually lose access permanently.

Two broad custody models show up in practice:

  • Custodial wallet (a provider controls keys or accounts on your behalf): easier account recovery, but you take on provider risk.
  • Non-custodial wallet (you control the private keys): more direct control, but you are responsible for security and backups.

Courses should also cover hybrid models, such as multi-signature (a setup where more than one key must approve a transfer) and hardware-backed key storage (keeping keys on a dedicated device designed to stay isolated from malware).

In professional settings, custody is an operations and governance topic, not only a technical choice. Controls like separation of duties (different people handle approvals and execution) and defined approval workflows reduce insider risk and error.

A well-rounded course will link custody to a broader cybersecurity approach. The NIST Cybersecurity Framework encourages organizations to define governance, understand assets, protect systems, detect issues, respond, and recover.[8] Those outcomes map cleanly onto stablecoin operations, even if the underlying technology is new.

Practice and workflows

Courses about USD1 stablecoins become far more useful when they include guided practice. Practice does not need to involve risky behavior, large transfers, or speculation. It can be built around small, controlled exercises that teach verification and operational discipline.

Here are example practice themes that fit many curricula:

Reading a transaction record

Most blockchains have explorers (websites that let you search and view on-chain transactions). An exercise can teach learners to identify:

  • The sender and recipient addresses.
  • The amount transferred and the token contract address (the on-chain identifier for the token).
  • The network fee paid and the confirmation count (how many blocks have been added after the transaction).

This builds a habit of checking facts from primary data rather than screenshots.

Understanding network and address details

A frequent real-world mistake is sending assets on the wrong network. A course should teach that:

  • The same address format may exist on more than one network.
  • Tokens with similar names can exist on different networks.
  • A transfer is only meaningful in the context of a specific network and token contract.

A simple exercise is to compare two networks and explain what changes in fees, confirmation times, and support tools, without actually sending funds.

Basic reconciliation

Reconciliation (matching records across systems) is the daily work of many teams. A course can teach a basic reconciliation workflow:

  • Start from an internal record (an invoice, payout file, or support ticket).
  • Match it to an on-chain transaction hash (a unique identifier for a transaction).
  • Record the confirmation status and timestamp.
  • Document any mismatch and the steps taken to resolve it.

This is not glamorous, but it is where many operational failures show up.

Permission hygiene

On programmable networks, users may grant token approvals (permissions that allow another contract to spend tokens). Courses should teach:

  • Approvals can be broad and long-lived.
  • Least privilege means granting only what you need for the shortest time that is practical.
  • Revoking approvals can reduce exposure if a contract is later compromised.

Incident drills

A short drill can teach clear thinking during mistakes:

  • A transfer was sent to the wrong address.
  • A wallet device is lost.
  • A staff member clicked a phishing link.

The point is not to promise perfect recovery. The point is to teach documentation, containment, and escalation. A cybersecurity framework like NIST CSF 2.0 gives a common language for these steps.[8]

Risk and safety

USD1 stablecoins can reduce friction in some kinds of transfers, but they are not risk-free. A course that treats them as "cash on the internet" without caveats is incomplete.

Below are risk categories that course materials should cover, with plain-English explanations.

Market and liquidity risk

Even if a token is designed to track one dollar, secondary markets can trade above or below one dollar. During stress, liquidity can thin out and prices can move.

Courses should teach learners to separate:

  • Value claim: "redeemable one-for-one for dollars"
  • Market price: what you can sell it for right now
  • Time to cash: how long it takes to actually receive dollars in your bank account

Redemption and counterparty risk

Counterparty risk (the risk that another party fails to meet obligations) matters when redemption depends on an issuer and its banking partners.

Learners should understand that legal rights, terms of service, and jurisdiction can affect whether and how redemption works. Public reports note that stablecoin arrangements can create prudential (safety-and-soundness focused) and run-like risks if not appropriately managed.[4]

Operational risk

Operational risk (losses from process failures, mistakes, or system breakdowns) is common:

  • Sending funds to the wrong address.
  • Misconfigured wallet software.
  • Poor key management.
  • Incomplete reconciliation between on-chain and internal records.
  • Downtime at a service provider.

Courses should include realistic failure scenarios and teach recovery playbooks, such as how to validate an address, how to confirm a transfer, and how to document incidents for audits and compliance reviews.

Smart contract and protocol risk

If USD1 stablecoins live on programmable networks, they may rely on smart contracts or token standards. Bugs and exploits can lead to losses or unexpected behavior.

Courses should teach basic security habits:

  • Prefer audited code when interacting with complex contracts.
  • Use least privilege (grant the minimum permissions needed) when approving token spending.
  • Understand upgradeability (whether a contract can be changed later) and its governance.

Fraud and social engineering

Social engineering (manipulating people rather than systems) is a leading cause of loss. Courses should cover:

  • Fake customer support and impersonation.
  • Phishing and malicious links.
  • Address poisoning (sending tiny transfers to create look-alike addresses in history).
  • SIM swap attacks (hijacking a phone number to intercept codes).

A practical course does not only describe these; it teaches verification habits, such as confirming communications through official channels and using strong authentication.

Regulatory and policy risk

Rules can change quickly, and they can differ widely across countries. When USD1 stablecoins are used for payments, lending, or investment-like activity, different regulators may become involved depending on facts and structure.

Global bodies such as the Financial Stability Board have urged comprehensive regulation, supervision, and oversight for stablecoin arrangements that may pose financial stability risk.[1] In the EU, MiCA creates an authorization framework and detailed rules for certain categories of tokens, including e-money tokens and asset-referenced tokens.[5][6] In the United States, FinCEN guidance explains when certain activities involving convertible virtual currency (a term used in U.S. guidance for value that can be exchanged for currency or acts as a substitute for currency) can trigger money services business (a category of regulated financial service business under U.S. federal rules) obligations under federal rules.[7]

Courses should not pretend there is a single universal rulebook. Instead, they should teach learners how to identify the right questions and where to look for authoritative sources.

Compliance and policy

Compliance is often presented as a checklist. Courses that do this miss the point. In practice, compliance is about managing risk, protecting users, and meeting legal obligations while keeping systems usable.

A strong curriculum typically covers:

AML, KYC, and sanctions basics

AML (anti-money laundering) programs aim to reduce misuse of financial systems for crime. KYC (know-your-customer) processes help institutions understand who is using a service. Sanctions screening checks whether a person, entity, or address is linked to restricted parties.

For stablecoin-related businesses, the relevant obligations depend on the role you play. If you are a virtual asset service provider (a business that exchanges, transfers, or safeguards virtual assets for others), international standards and local laws may expect controls like customer due diligence (steps to identify customers and assess risk), transaction monitoring (reviewing activity for suspicious patterns), and recordkeeping (keeping logs needed for audits and regulators).[3]

In the United States, FinCEN has published guidance on how its regulations apply to different business models involving convertible virtual currency.[7] That guidance is not the last word for every situation, but it is a core reference for courses that discuss U.S.-facing operations.

The Travel Rule

The Travel Rule (a rule to transmit certain originator and beneficiary information with transfers above thresholds in many regimes) is a practical topic, not just a legal one. Implementing it can affect product design, data storage, vendor choices, and customer experience.

The FATF Updated Guidance explains how the Travel Rule concept applies to virtual asset transfers and provides examples and expectations that many jurisdictions follow when drafting local rules.[3]

Courses should treat the Travel Rule as a design constraint and discuss tradeoffs: privacy, security, interoperability (how well systems work together), and the risk of collecting more data than is truly needed.

Consumer protection and disclosure

When people hold USD1 stablecoins, they often care about two promises: "Will it hold value near one dollar?" and "Can I redeem it when I want to?" A compliance-oriented course should cover how disclosures support informed decision-making and how misleading claims can create legal and reputational risk.

International frameworks emphasize clear disclosures, governance, and risk management for stablecoin arrangements.[1][2] The details of disclosure obligations vary by jurisdiction, but the general direction is consistent: if a product resembles money, regulators tend to expect high standards.

EU MiCA basics for stablecoin-like tokens

MiCA (the EU Markets in Crypto-Assets Regulation) is a central reference for anyone building courses with an EU audience. MiCA distinguishes between categories such as asset-referenced tokens and e-money tokens, with authorization and reserve-related rules for issuers.[5][6]

A good course avoids overconfident summaries and instead teaches learners how to read official sources, understand definitions, and track updates. Even within a single regime, many details sit in technical standards, guidelines, and supervisory practice.

Banking supervision and systemic risk topics

As stablecoin usage grows, regulators also look at how traditional financial institutions are exposed to crypto-assets. The Basel Committee on Banking Supervision, for example, has published standards and amendments related to banks' exposures to cryptoassets, including how those exposures should be treated prudentially.[10]

This is not a "stablecoin rule" in the consumer sense, but it matters for enterprise courses because it influences how banks and large payment firms interact with stablecoin-related business models.

How to choose a course

If you are browsing course options about USD1 stablecoins, a simple way to compare them is to check for depth, balance, and primary sources.

Here are signals that a course is likely to be useful:

Clear audience and scope

Look for a course that states who it is for and what it covers. A course for developers should say which networks and tooling it focuses on. A course for compliance teams should say which jurisdictions it discusses and which parts are general concepts versus local rules.

Definitions before debate

Courses should define core terms early, in plain language. If a course assumes you already know jargon, it may be skipping the foundations that prevent mistakes later.

Primary sources and citations

Look for references to regulators, standard-setters, and official legal texts. A course can include opinions, but it should not treat opinions as facts. Documents such as the FSB high-level recommendations and FATF guidance are common anchors because they summarize risk themes and compliance expectations that show up across jurisdictions.[1][3]

Risk is treated as central, not as a footnote

If a course focuses only on speed and convenience, it is missing the real picture. A balanced course explains custody risk, operational risk, and what happens in failure scenarios.

Practice that teaches verification

Hands-on exercises are useful when they build habits: verifying addresses, reading transaction data, documenting incidents, and reconciling records. Avoid courses that push learners toward risky behavior to create excitement.

Updates and change tracking

Stablecoin rules and market structures evolve. A course can stay current if it teaches durable concepts and points learners to official sources for the latest details, such as MiCA text for the EU or FinCEN guidance for U.S. federal framing.[5][7]

Designing good courses

If you are building educational material for USD1 stablecoins, it helps to start with learning outcomes and work backward. A course is effective when it changes what learners can do, not only what they can repeat.

Here are design principles that translate well into course content.

Start with concrete scenarios

Abstract explanations land better when they are tied to realistic scenarios, such as:

  • A freelancer receives USD1 stablecoins for remote work and wants to move the funds to a bank account.
  • A small business wants to accept USD1 stablecoins for invoices and needs an approval workflow.
  • A developer needs to integrate USD1 stablecoins payments in an app and must choose between custodial and non-custodial designs.
  • A compliance officer needs to draft a policy for handling suspicious activity reports (reports filed to authorities when activity looks illegal or suspicious) and customer complaints.

Each scenario can be reused across modules to show how technical, legal, and operational considerations interact.

Teach the difference between knowledge and proof

Stablecoin discussions are full of confident claims. Courses should train learners to ask:

  • What is asserted, and what is evidenced?
  • Is the evidence current, independent, and specific?
  • Does a document cover a point in time or an ongoing process?

Using official frameworks as anchors helps avoid rumor-based learning. The FSB high-level recommendations and broader crypto framework are good examples of documents that outline risk themes and supervisory expectations at a high level.[1][2]

Use plain language check-ins

Courses should include short moments where learners restate concepts without jargon. For example:

  • "Redeemable" means you can exchange tokens back for dollars, but only if the rules and operations actually allow it.
  • "Custody" means who has the power to move funds.
  • "Finality" means when you can treat a payment as done, without expecting reversal.

These check-ins make later modules more approachable.

Include failure modes and recovery

Training is incomplete without showing what breaks. Learners should practice:

  • Detecting wrong-network transfers.
  • Recognizing fake support attempts.
  • Verifying addresses and transaction status.
  • Documenting incidents and communicating clearly.

Even a beginner course can include a "what can go wrong" section. It reduces the chance that learners will treat USD1 stablecoins as a shortcut around basic financial controls.

Keep the tone balanced

USD1 stablecoins can be useful tools, but they sit in a fast-changing field with real risks. Courses should avoid hype, avoid fearmongering, and make uncertainty explicit.

For example, it is fair to say that stablecoin markets and rules evolve quickly, and that learners should verify the latest legal rules in relevant jurisdictions. It is also fair to say that global bodies have repeatedly emphasized the need for consistent oversight and risk management when stablecoin arrangements scale.[1][2]

FAQ

Are USD1 stablecoins the same as a bank deposit?

Not necessarily. A bank deposit is a claim on a bank and is often covered by deposit insurance up to certain limits, depending on the country and conditions. USD1 stablecoins are digital tokens that may have redemption rights, but those rights depend on the issuer, the legal structure, and the jurisdiction. Courses should treat this distinction carefully and avoid implying that all stable tokens carry bank-like protections.

If something is redeemable one-for-one, is it risk-free?

No. One-for-one redeemability is a design goal. Risk still exists in reserves, operations, legal terms, cybersecurity, and market liquidity. Public-sector reports highlight that stablecoin arrangements can create run-like risks and other vulnerabilities if not appropriately managed.[4]

Do I need to understand blockchain to use USD1 stablecoins?

You can use USD1 stablecoins through custodial services with minimal technical detail, but understanding the basics reduces mistakes and helps you evaluate risk. A foundation course should explain what an address is, how to confirm a transfer, and why blockchain transfers can be difficult to reverse.

What is the single best security habit?

Protect your keys and verify requests. If you control a non-custodial wallet, your seed phrase is the master key. If someone gets it, they can move funds. If you use custodial services, protect account access with strong authentication and be skeptical of support messages or urgent requests.

How do regulations affect course content?

Regulation shapes what is possible and what is risky. A course that teaches stablecoin operations without mentioning AML expectations, sanctions screening, and consumer disclosure rules will leave learners unprepared. At the same time, courses should avoid providing legal advice and should encourage learners to consult authoritative sources such as regulators and standard-setting bodies.[1][3][5][7]

Can a course stay current in a fast-moving field?

Yes, if it focuses on durable concepts and teaches learners how to find and interpret primary sources. High-level frameworks from bodies like the FSB, FATF guidance, and official legal texts like MiCA provide stable reference points even as details evolve.[1][3][5]

Sources

  1. Financial Stability Board, "High-level Recommendations for the Regulation, Supervision and Oversight of Global Stablecoin Arrangements: Final report" (17 July 2023)
  2. Financial Stability Board, "Global Regulatory Framework for Crypto-asset Activities" (17 July 2023)
  3. Financial Action Task Force, "Updated Guidance for a Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers" (October 2021)
  4. U.S. Department of the Treasury, President's Working Group on Financial Markets, Federal Deposit Insurance Corporation, and Office of the Comptroller of the Currency, "Report on Stablecoins" (November 2021)
  5. European Union, "Regulation (EU) 2023/1114 on markets in crypto-assets" (31 May 2023)
  6. European Banking Authority, "Asset-referenced and e-money tokens (MiCA)"
  7. Financial Crimes Enforcement Network, "Application of FinCEN's Regulations to Certain Business Models Involving Convertible Virtual Currencies" (FIN-2019-G001, 9 May 2019)
  8. National Institute of Standards and Technology, "The NIST Cybersecurity Framework (CSF) 2.0" (NIST CSWP 29, 26 February 2024)
  9. Bank for International Settlements, "Blueprint for the future monetary system" (Annual Economic Report 2023, Chapter III)
  10. Basel Committee on Banking Supervision, "Cryptoasset standard amendments" (17 July 2024)