Welcome to USD1disclosure.com

USD1disclosure.com is a plain-English guide to disclosure for USD1 stablecoins. In this context, disclosure means the public information that lets a reader understand how USD1 stablecoins are created, backed, redeemed, governed, monitored, and, if necessary, wound down.

A stablecoin (a digital token meant to keep a steady price) is only as understandable as its disclosures. Good disclosure does not guarantee that USD1 stablecoins are low risk. Good disclosure does make the design visible, comparable, and open to challenge. That is why major standards setters and regulators focus so heavily on transparency around reserves, redemptions, governance, operations, and legal rights.^[1]^[2]^[3]^[5]

For this site, the phrase USD1 stablecoins refers to any digital tokens stably redeemable one to one for U.S. dollars. This page is educational and is not legal, accounting, or investment advice.

What disclosure means for USD1 stablecoins

Disclosure for USD1 stablecoins is not one document and it is not just a reserve chart. A serious disclosure package usually includes a white paper (a formal document that explains structure, risks, and user rights), legal terms, reserve reports, independent assurance reports (reports from outside professionals that test or confirm stated information), public notices about changes, complaint procedures, and plain-language explanations for ordinary users. The point is not volume. The point is whether a careful reader can understand what promise is being made and what stands behind that promise.

In practice, disclosure for USD1 stablecoins should answer a simple set of questions. Who is the issuer (the legal entity that creates and redeems USD1 stablecoins)? What reserve assets (cash and similar assets held to support redemption) stand behind outstanding USD1 stablecoins? Who holds those reserve assets in custody (safekeeping by a bank or service provider)? Who can redeem USD1 stablecoins directly, at what price, and in what time frame? What fees, thresholds, and conditions apply? What operational controls exist if a bank, wallet provider, or blockchain network fails? And what legal rights does a holder actually have if something goes wrong?

The Financial Stability Board frames disclosure broadly. It says users and other relevant stakeholders should receive comprehensive and transparent information about governance, conflicts of interest, redemption rights, the stabilization mechanism, operations, risk management, and financial condition. It also provides a common reserve disclosure template so readers can compare the quality of reserves and the ability to maintain redemption at par, which means one U.S. dollar for each one-dollar unit of USD1 stablecoins.^[1]

That framing matters because a reader often sees only the easy part: a claim that USD1 stablecoins are backed one to one. Backing matters, but it is only one layer. A full disclosure regime also explains how backing is measured, where backing is held, whether backing can be sold quickly, whether backing is legally separate from the issuer's own property, and whether ordinary holders can enforce redemption rights themselves rather than depending entirely on an intermediary (a platform or service sitting between the holder and the issuer).^[1]^[3]

Why disclosure matters

Disclosure matters because confidence in USD1 stablecoins can fail long before reserves are fully exhausted. A run (many users trying to redeem at once because they fear delay or loss) can begin when people are unsure about reserve quality, unsure about legal rights, or unsure about whether redemptions will still work under stress. The U.S. Treasury stablecoin report explained this clearly: if issuers do not honor redemption requests, or if users lose confidence in an issuer's ability to honor them, runs can occur and harm both users and the broader financial system.^[3]

The same report also observed that public information has often been uneven. Reserve composition, redemption rights, and the legal nature of the user claim can differ a great deal from one arrangement to another. Some arrangements can postpone redemptions or limit who may redeem. Some give a direct claim on the issuer, while others do not give ordinary users direct redemption rights at all. When those details are not obvious, a label like "fully backed" tells a reader far less than it appears to tell.^[3]

Good disclosure also supports comparability. If two arrangements both say that they issue USD1 stablecoins, but one keeps reserves in overnight cash and short-term government bills while another holds longer-dated or harder-to-sell assets, the differences matter. If one arrangement allows direct redemption for small and large holders while another only allows certain institutions to redeem, that difference matters too. A person deciding whether to hold, receive, or redeem USD1 stablecoins needs more than a slogan. A person needs a way to compare structure, rights, and risk.

There is also a public-interest reason. Standards setters do not focus on disclosure only to help investors. They focus on disclosure because opacity can amplify market stress, weaken discipline, and make oversight harder. That is why international work on stablecoins repeatedly ties disclosure to governance, risk management, and the ability of authorities to understand the arrangement across borders.^[1]^[2]^[5]

The core parts of a disclosure package

A balanced disclosure package for USD1 stablecoins usually has at least seven parts.

First, there should be a public description of the promise. Does the arrangement promise that USD1 stablecoins can be redeemed for U.S. dollars? If so, who makes that promise, to whom, and under what law? The promise should be stated in plain terms, not buried in marketing language.

Second, there should be reserve disclosure. Readers should be able to see the broad asset mix, the valuation method, the reporting date, the role of custodians, and whether reserves are free of legal or contractual restrictions. A reserve statement that gives only a single total without categories, dates, and methods is not enough.^[1]^[3]

Third, there should be redemption disclosure. This includes eligibility, timing, fees, minimum amounts, settlement routes, bank cutoffs, and what happens when normal channels fail. The word "redeemable" is not informative by itself. The process is what matters.^[1]^[3]^[4]

Fourth, there should be governance disclosure. A reader should know who makes decisions, who manages reserves, who approves trading and banking partners, who can change contracts or policies, how conflicts are managed, and how major decisions are documented. Clear lines of responsibility are a central theme in both financial market infrastructure guidance and crypto market policy work.^[2]^[5]

Fifth, there should be operational and technology disclosure. If USD1 stablecoins rely on one or more blockchains (shared digital record systems), on one or more wallet providers, on transfer agents, on market makers, or on bank partners, those dependencies matter. So do contract upgrade rights, pause rights, key management, and incident response plans.^[2]^[5]

Sixth, there should be compliance disclosure. AML/CFT (anti-money laundering and countering the financing of terrorism) controls, sanctions screening, suspicious activity escalation, complaint handling, and privacy limits should be described clearly enough that a user understands where monitoring occurs and where it does not. FATF's recent work on stablecoins and unhosted wallets shows why this area cannot be treated as an afterthought.^[9]

Seventh, there should be contingency disclosure. If a bank fails, a custodian freezes assets, a smart contract bug appears, or redemptions surge, what happens next? Good disclosure does not promise that nothing will ever go wrong. Good disclosure explains what the arrangement is supposed to do when something does go wrong.^[1]^[8]

Reserve disclosure in detail

Reserve disclosure is where many readers start, and rightly so. If USD1 stablecoins are marketed as stably redeemable one to one for U.S. dollars, the reserve is the first place a reader looks for evidence that the promise is plausible. But the right question is not just, "How large is the reserve?" The better question is, "What kind of reserve is it, where is it, how liquid is it, and who controls it?"

The FSB's common reserve disclosure template is useful here because it goes beyond a headline number. It points to categories such as demand deposits, term deposits, money market fund shares, reverse repurchase agreements, government bills, and government notes. It also points to market value, weighted average maturity, daily averages, and the amount of stablecoins in circulation. That structure tells the reader two important things. One, reserve quality is not a yes or no question. Two, reserve disclosure should make comparison possible over time, not just at one snapshot date.^[1]

Weighted average maturity (the average time until holdings come due, adjusted by their size) matters because assets that mature very soon are usually easier to convert into cash than assets with longer time horizons. Daily averages matter because month-end snapshots can look healthier than the typical position over the reporting period. If a reserve report gives only a single date without a methodology note, a careful reader should immediately ask how representative that number is.

A high-quality reserve disclosure for USD1 stablecoins should also say whether assets are unencumbered (free of legal, regulatory, or contractual restrictions that would slow sale or transfer). This point appears directly in the FSB template because an asset can exist on paper and still be difficult to monetize under stress. If reserve assets are pledged elsewhere, restricted by contract, or operationally difficult to liquidate, the reserve may be less useful in a redemption wave than a headline number suggests.^[1]

Location and control matter too. The disclosure should identify the main custodians and banking partners, describe the custody arrangement, and explain whether reserve assets are segregated (kept separate from the issuer's own property). Segregation is especially important in an insolvency or enforcement scenario. IOSCO's custody recommendations similarly emphasize segregation, reconciliation (checking that records from different systems match), and disclosure of safekeeping arrangements, including what rights clients have if a service provider fails.^[5]

Related-party exposure is another area that deserves plain treatment. If the arrangement can lend to affiliates, hold obligations of affiliates, or use a related company as a critical service provider, those facts belong in the disclosure. The reader should not have to reverse-engineer them from corporate filings or code repositories. The same applies to reserve managers, trading firms, and administrators. Disclosure is not credible if it names risks in the abstract but hides who sits on each side of the transaction.

One more point is often missed: reserve disclosure should explain what is not in the reserve. It should be obvious whether the reserve excludes loans to affiliates, speculative assets, or instruments with limited trading history. The FSB recommendation on stabilization is explicit that reserve-based stablecoin arrangements should rely on conservative, high-quality, and highly liquid assets, with particular attention to liquidity and the danger of fire sales (rapid forced selling at bad prices) during stress.^[1]

This is why a short reserve pie chart is never enough. The serious reader of USD1 stablecoins wants categories, dates, valuation rules, custodian names, restrictions, maturity profile, concentration limits, and assurance over the numbers. Without that, "one to one" remains more of a slogan than a disclosure.

Redemption disclosure in detail

Redemption is the heart of the promise for USD1 stablecoins. Redemption means converting USD1 stablecoins back into U.S. dollars through the issuer or another approved path. The critical disclosure question is not whether redemptions exist in theory. It is whether an ordinary holder can tell, in advance, exactly how redemptions work in normal times and under stress.

The FSB says users should have a robust legal claim and timely redemption, and that for single-currency arrangements redemption should be at par into fiat currency. It also says arrangements should not impose conditions that unduly restrict redemption rights, such as minimum thresholds that are so large they become a practical barrier, or fees so high that redemption becomes a practical deterrent.^[1]

The Treasury report reinforces why this matters. It notes that redemption rights vary significantly across arrangements. Differences can include who may present a token for redemption, how much may be redeemed, whether redemptions can be delayed or suspended, and whether the user has a direct claim on the issuer or no direct redemption right at all. For a reader, this means that "redeemable" without a clear process description is close to meaningless.^[3]

A strong redemption disclosure for USD1 stablecoins should therefore answer at least nine questions. Who can redeem directly? What identification or account opening is required? What bank account types are accepted? What fees apply? What are the minimum and maximum amounts? What time of day counts as same-day or next-day processing? What happens on weekends or bank holidays? What happens if a primary banking partner is unavailable? And does the holder have an alternative route if an intermediary becomes unavailable?

New York's supervisory model offers one concrete example of what specific redemption disclosure can look like. As summarized by the superintendent of the New York State Department of Financial Services, or DFS, regulated U.S. dollar-backed arrangements under that guidance are expected to have clear policies for timely redemption within no more than two business days after a valid redemption request, along with reserve, audit (independent review), and attestation (an accountant's statement on a specific subject) expectations.^[4] That is not the only possible model, but it shows the level of specificity that makes a disclosure useful.

Good redemption disclosure should also distinguish direct redemption from selling in the secondary market (trading between users or on venues rather than redeeming with the issuer). Many holders of USD1 stablecoins may never interact with the issuer directly. They may instead sell USD1 stablecoins for U.S. dollars through a platform, a broker, or another user in the secondary market (trading between users or on venues rather than redeeming with the issuer). That route can depend on market liquidity, platform solvency, and trading conditions. It is not the same as a legal redemption right against the issuer. A good disclosure package states the difference plainly.

The final test is whether the redemption section still reads clearly under adverse scenarios. If reserve liquidation takes time, if banks close, if sanctions controls trigger reviews, or if a contract pause function is used, the arrangement should say how this affects redemptions. EBA guidance on redemption plans in the European Union makes this point in a formal way by requiring planning around liquidation strategies, critical activities, claims, steps in the process, and crisis triggers.^[8]

Governance and accountability

Governance means who makes decisions and who can be held accountable for them. It sounds abstract until something changes: a reserve policy is revised, a bank partner is replaced, a smart contract is upgraded, a freeze function is used, or redemptions are restricted. At that point, weak governance disclosure becomes a real risk factor.

CPMI-IOSCO guidance is especially useful here because it insists on documented and disclosed governance arrangements with clear and direct lines of responsibility and accountability. It also points out a subtle but important limit of technical transparency: code on a public ledger may exist as a form of disclosure, but the interaction of coded features can be too complex to be meaningful as disclosure for authorities, stakeholders, or the general public.^[2]

That is a powerful lesson for USD1 stablecoins. Publishing a contract address is not the same as explaining the power structure around that contract. A good governance disclosure should say who controls minting and burning, who can pause transfers, who can blacklist addresses if that function exists, who can replace a data feed service or reserve manager, who can approve a new chain deployment, and what approvals are needed for each action. If several signers or keys must approve an action, the disclosure should explain, in plain terms, who the signers are and how many approvals are needed.

Conflict disclosure is equally important. A conflict of interest exists when decision makers or related companies can benefit in ways that may not align with holders' interests. If the reserve manager is related to the issuer, if a market maker is affiliated, or if a director has financial exposure to a service provider, that does not automatically invalidate the arrangement. But it does belong in the disclosure, along with the controls meant to reduce bias.

Readers should also look for governance around change management. Change management is the process for approving and communicating modifications to the arrangement. This includes code upgrades, chain expansions, asset eligibility changes, custodian changes, fee changes, and policy changes. The FSB explicitly says users' interests should be protected when a potential modification could materially affect value, stability, or risk.^[1] That means a serious disclosure regime needs more than a one-time launch document. It needs an ongoing process for telling people what changed, why it changed, and when it takes effect.

A final governance point is legal visibility. The arrangement should identify the issuer and key service providers by legal name and jurisdiction (the legal place where rules apply). A disclosure that relies on brand names only is weak. Responsibility follows legal entities, contracts, and governing law, not logos or slogans.

Operations, technology, and custody

Operational disclosure for USD1 stablecoins is where many failures hide. Operational risk means the chance of loss caused by failures in systems, people, processes, vendors, or technology. A reserve could look strong on paper and still fail users if the transfer system breaks, if access keys are compromised, if reconciliations are weak, or if a banking connection goes offline.

IOSCO's final policy recommendations devote separate attention to custody, segregation, disclosure of custody and safekeeping arrangements, client asset reconciliation, and management and disclosure of operational and technological risks.^[5] That is a clue for how a careful reader should think. Technology risk is not a side issue. It is part of the core promise.

For USD1 stablecoins, the technology disclosure should identify the relevant blockchain networks, the token standards used, the main contract addresses, whether contracts can be upgraded, whether emergency pauses exist, and who controls those functions. A smart contract (software on a blockchain that follows preset rules) may automate issuance or transfers, but governance still sits around it. If the arrangement relies on off-chain records (records kept in internal systems rather than directly on the blockchain) for reserve balances, customer identity, or redemption queues, that should also be obvious.

Settlement finality is another technical point that deserves plain words. Settlement finality means the point at which a transfer becomes final and cannot be reversed under the governing rules. CPMI-IOSCO notes that on distributed ledger systems (shared record systems updated across many computers) there can be a misalignment between technical settlement on the ledger and legal finality under the relevant rules or contracts.^[2] For holders of USD1 stablecoins, that means the disclosure should explain what counts as final, how reversals are handled, and what happens during network splits, outages, or other exceptional events.

Custody disclosure should be equally specific. If a third party holds reserve assets, the disclosure should explain the custody chain, protections against creditor claims, reconciliation frequency, and whether holders have any rights that survive a custodian failure. IOSCO emphasizes accurate and up-to-date records, frequent reconciliation, and clear disclosure of terms, conditions, and safeguards.^[5] A serious disclosure package does not treat custody as a mere vendor line item.

Incident response belongs here as well. If keys are lost, contracts are exploited, or a service provider fails, what is the first communication channel? Who decides whether to pause activity? Is there a public status page? Is there a written process for notifying users, regulators, counterparties, and trading venues? Many arrangements say they value transparency, but true transparency is tested on the day of a disruption, not on the day of launch.

Compliance, privacy, and financial crime controls

Disclosure for USD1 stablecoins should also explain where compliance controls operate and where they do not. This part is often underwritten in marketing materials because it can sound restrictive, but it is central to how the arrangement functions in the real world.

FATF's 2026 work on stablecoins and unhosted wallets shows why. The report describes how stablecoin activity can move through centralized intermediaries, decentralized venues, and peer-to-peer transfers. It also notes that users may hold and transfer stablecoins directly through unhosted wallets (wallets controlled by the user rather than by a platform), which can create compliance gaps when transactions occur outside regulated intermediaries.^[9] For USD1 stablecoins, that means the disclosure should not imply that every transfer is screened in the same way.

A clear compliance disclosure should therefore answer basic questions. Are sanctions checks applied at issuance, redemption, or both? Can addresses be blocked? Under what authority? Are blockchain analytics tools used, and if so, for what purpose? What data is collected at onboarding and redemption? What transaction patterns trigger review? When can a transaction be delayed, rejected, or reported? What complaints path exists if a user thinks a compliance action was wrong?

At the same time, privacy should not be described vaguely. A public blockchain is transparent in one sense and not in another. The transaction trail may be visible, while the identity behind an address may not be obvious. Treasury's stablecoin report described public blockchains as allowing pseudonymous use in many settings, which means identity may be unknown even while transaction details are visible.^[3] A good disclosure makes these limits understandable. It should say what the issuer or service providers can see, what outside observers can see, and what legal process may compel additional disclosure.

This is also an area where regulatory regimes converge. The details differ, but the direction is similar: arrangements that issue or support stable-value tokens are expected to describe their compliance framework with more than a generic promise to follow the law. In the European Union, EBA materials tie the Markets in Crypto-Assets Regulation, often called MiCA, to white papers, governance, complaints handling, reserve assets, and redemption planning.^[6]^[7] In New York, DFS has paired stablecoin-specific guidance with broader expectations around disclosures, custody structures, transaction monitoring, and consumer protection.^[4] The common thread is that compliance disclosure is part of product disclosure, not a separate universe.

Stress events, recovery, and wind-down

The best test of disclosure for USD1 stablecoins is whether it still helps the reader during a stress event. Recovery and resolution planning (planning for stabilization or orderly wind-down if the arrangement becomes distressed) is not exciting copy, but it is one of the clearest indicators that the arrangement is built for the real world rather than for ideal conditions only.

The FSB recommends that stablecoin arrangements have appropriate recovery and resolution plans and that disclosures explain the functioning of the arrangement, the risks, the value and composition of reserves, and the redemption process.^[1] The EBA's redemption plan guidance goes even further into crisis mechanics by referencing liquidation strategies for reserve assets, the mapping of critical activities, the content of redemption claims, the main process steps, and the conditions that can trigger the plan.^[8]

For USD1 stablecoins, practical crisis disclosure should cover at least five themes. First, triggers: what events move the arrangement from ordinary operations into contingency mode? Second, authority: who decides that the plan is activated? Third, liquidity steps: what reserve assets are sold first and why? Fourth, communications: how quickly are users told what is happening and where are updates posted? Fifth, user treatment: what rights remain in place and what delays, if any, might apply?

This area is where vague reassurance causes the most harm. Telling users that reserves are "safe" is not a recovery plan. A real plan explains how reserves are accessed under operational pressure, how claims are prioritized, how data are reconciled, and how cross-border service dependencies are managed. If a disclosure package never discusses adverse scenarios, it is leaving out the conditions under which readers most need accurate information.

Readers should also look for historical disclosure. Has the arrangement published incident summaries after operational problems? Has it explained previous pauses, banking changes, or policy changes? Past communication behavior often tells a reader more about future disclosure quality than the launch document ever will.

How to read disclosure critically

A careful reading of disclosure for USD1 stablecoins usually starts with rights, not branding. The first question is what a holder can actually claim. If the legal terms are hard to find or inconsistent with public marketing, the legal terms matter more. A serious reader compares the user-facing summary, the legal terms, the reserve report, and the redemption process to see whether they describe the same arrangement.

The next step is to compare the promise with the plumbing. If USD1 stablecoins promise one-to-one redemption into U.S. dollars, the reserve report should support that promise and the operational sections should explain how the promise is executed. If redemptions depend on a narrow set of bank windows, on one provider, or on conditions not mentioned in the headline summary, that gap matters.

Frequency also matters. A stale report can be worse than no report if users assume it is current. High-quality disclosure tells the reader how often reserve data, attestation results, and policy updates are published. It also says what period each report covers and whether numbers are month-end, daily average, or something else. The FSB's reserve template is useful here because it pushes disclosure away from single-point snapshots and toward comparable reporting periods.^[1]

The assurance layer matters too. If there is an independent report, the reader should ask what subject it actually covers. Does it speak to reserve existence, reserve valuation, internal controls, or financial statements as a whole? If it covers only a narrow statement prepared by management, that can still be helpful, but it should not be mistaken for a broad review of every operational and legal risk.

A good reader also watches for language that hides discretion. Terms like "may," "can," or "reserve the right" are not automatically problematic, but they matter most when attached to redemption timing, fee changes, asset eligibility, contract pauses, or use of compliance controls. If the arrangement keeps broad discretion in all the places that affect user outcomes, the disclosure is weaker than it first appears.

Finally, plain language matters. Complex systems are sometimes unavoidable, but unreadable disclosure is not. CPMI-IOSCO's warning about coded governance being too complex to function as meaningful disclosure is a reminder that technical openness and public understanding are not the same thing.^[2] Strong disclosure for USD1 stablecoins translates complex mechanics into language that a non-specialist can still follow.

Common red flags

One red flag is reserve language without reserve detail. If USD1 stablecoins are said to be fully backed, but the reader cannot find asset categories, dates, custody structure, restrictions, or assurance, the disclosure is thin.

A second red flag is redemption language without a redemption path. If the arrangement promises redemption but does not say who can redeem, in what size, with what timing, and under what conditions, the core promise is underdisclosed.^[1]^[3]

A third red flag is invisible governance. If the arrangement does not identify the issuer, reserve manager, custodian, and operators with legal precision, the reader may not know who is actually responsible for key functions.^[2]

A fourth red flag is silence about operational powers. If a smart contract can be paused, upgraded, or restricted, but the disclosure never says who controls those actions, the operational risk section is incomplete.^[2]^[5]

A fifth red flag is outdated reporting. If reports exist but the publication schedule is unclear, if links break, or if change notices appear only after the fact, the arrangement may be disclosing reactively rather than systematically.

A sixth red flag is weak crisis language. If there is no mention of recovery, redemption planning, or communication under stress, the arrangement may have designed its disclosures only for normal conditions.^[1]^[8]

A seventh red flag is overconfident compliance language. If the disclosure implies perfect monitoring or perfect privacy at the same time, it is probably oversimplifying. FATF and Treasury materials show why stablecoin activity sits in a complicated middle ground between visibility, pseudonymity, and intermediary-based controls.^[3]^[9]

What balanced disclosure looks like

Balanced disclosure for USD1 stablecoins is clear without pretending that risk disappears. It does not say that reserves solve every problem. It does not say that code solves governance. It does not say that regulation solves operations. Instead, it gives the reader enough information to judge the arrangement as a whole.

In practical terms, balanced disclosure usually has five qualities. It is specific, which means the reader gets names, dates, categories, and process steps. It is layered, which means there is a short plain-language summary backed by deeper legal and technical materials. It is recurring, which means reserve data, notices, and policy changes are published on a visible schedule. It is independently checked where appropriate, which means outside accountants, auditors, or supervisors play a role in verifying important facts. And it is event-driven, which means material changes and incidents are disclosed promptly rather than waiting for the next routine update.^[1]^[4]^[5]

That kind of disclosure does not guarantee that every arrangement issuing USD1 stablecoins is sound. What it does is reduce guesswork. It narrows the gap between what users think they hold and what the legal, financial, and operational structure actually provides. In a market where confidence can move quickly, that gap is often the difference between informed use and blind reliance.

The clearest lesson from the global policy record is simple. Disclosure for USD1 stablecoins should be treated as core infrastructure, not as decoration. Reserves, rights, governance, custody, compliance, and crisis handling all need to be visible in forms that both specialists and ordinary users can understand. When disclosure reaches that standard, the market is still not risk-free. It is just more legible, more testable, and more accountable.^[1]^[2]^[5]^[6]^[7]^[8]^[9]