QuadrigaCX was identified as a Canadian crypto exchange, but the evidence available for this account does not establish its operating dates, specific services, collapse chronology, insolvency findings, customer recoveries, or present status. The permitted evidence describes general centralized-exchange patterns only. It cannot establish what QuadrigaCX itself did or what happened to its customers. A reliable historical account must keep that boundary clear rather than turn broad industry descriptions into case-specific facts.

What was QuadrigaCX, and what role did it serve?

The assignment identifies QuadrigaCX as a Canadian crypto exchange. The available evidence does not independently document its history, its operating period, the assets it listed, or the services it offered. It is therefore possible to identify its broad category here, but not to provide a verified timeline or a detailed account of its place in Canada’s crypto market.

A centralized crypto exchange is a business category, not a single fixed operating design. Some centralized exchange operators may combine third-party trading, proprietary trading, margin lending, token issuance, and custody. Not every operator performs every function; combining roles can create operational dependencies and conflicts. This evidence supports a general description of possible exchange activities, not a claim that QuadrigaCX offered any particular service or combined those roles. source

The distinction matters because an exchange can be discussed at several different levels: as a business, as a venue for trading, and as a provider of services such as custody. A general description of the category does not answer which of those functions a named company performed. Nor does it establish whether a company remained operational at a particular time. No current, dated evidence in the permitted material verifies QuadrigaCX’s present status, so this account makes no claim that it offers service today.

How did QuadrigaCX’s exchange operations and custody work?

The permitted evidence does not establish QuadrigaCX’s account system, trading records, deposit or withdrawal process, custody arrangements, or control of customer assets. Those are case-specific questions. It would be inaccurate to answer them by assuming that QuadrigaCX followed a general model used by some centralized venues.

At a high level, a centralized exchange customer may transfer funds and custody to the exchange before trading on its internal order book. Custody and legal ownership arrangements vary by platform and jurisdiction. This broad pattern is not a finding about QuadrigaCX, its customers’ rights, or how any assets were held or controlled. source

A centralized crypto exchange commonly records outstanding buy and sell orders in an off-chain limit order book. That description concerns a general venue mechanism; it does not establish that QuadrigaCX used a particular order-book design, or that its internal records were complete, reconciled, or accessible in any specific way.

In evaluating a case-specific account, keep the questions separate. Trading records concern orders and executed trades. Custody concerns the arrangements for holding or controlling assets. Deposit and withdrawal procedures concern movements into or out of an exchange. Evidence about one does not, by itself, settle the others. The allowed claims do not provide QuadrigaCX-specific records for any of these areas, so the details remain unestablished here.

What is documented about the collapse and insolvency?

The evidence permitted for this article contains no dates, official findings, court records, or other case-specific material about QuadrigaCX’s collapse or insolvency proceedings. It therefore cannot support a chronology, identify procedural steps, describe customer impact, or attribute findings to a court, regulator, or investigator.

The same limitation applies to claims about customer recovery. No allowed claim establishes amounts recovered or distributed, eligibility for any distribution, the handling of customer claims, or the status of proceedings. Those statements require relevant, dated proceeding records. General descriptions of exchange custody or trading do not serve as evidence of what happened in this case.

This is not a conclusion that no such records or findings exist. It is a boundary on what can be established from the evidence available here. A case history should distinguish a reported event from an official finding and should not present an allegation as a court conclusion. Without the underlying records in the permitted evidence, supplying dates or outcomes would risk overstating what is known.

What remains unresolved, and how should claims be assessed?

For this account, the key case-specific questions remain unanswered: when QuadrigaCX operated, how its customer services worked, what events preceded its collapse, what formal proceedings found, and what happened to customer claims. The available claims do not identify which assertions about those matters are confirmed, disputed, or unresolved. Those categories should not be assigned without the underlying evidence.

A careful reader can assess a proposed historical account by checking whether each material statement is tied to an identifiable, relevant record. Dates and procedural steps need records that establish them. Claims attributed to a regulator or court need the corresponding official material. Claims about deposits, withdrawals, custody, or customer balances need evidence specific to the company and the period being discussed. Repetition of a claim does not, on its own, establish its accuracy.

It is also important not to treat an industry pattern as proof of company conduct. For example, a general description of an internal order book does not show that a named exchange maintained accurate customer balances. A general description of custody before trading does not establish the legal or operational treatment of a particular customer’s assets. The distinction between category-level evidence and case-level evidence is essential to a factual account.

What exchange-infrastructure lessons can be drawn from QuadrigaCX?

The permitted evidence does not establish which controls, governance arrangements, recordkeeping practices, or continuity measures QuadrigaCX had or lacked. It cannot show that a particular infrastructure failure caused the collapse. Any such conclusion would require case-specific evidence beyond the claims available here.

A bounded general lesson is to examine which entity performs each function and how those functions relate. Some exchange operators may combine trading and custody with other activities, and combining roles can create dependencies and conflicts. That is a reason to investigate arrangements in a documented case—not evidence that QuadrigaCX had a particular control weakness or organizational structure. source

Market liquidity is a separate analytical question. It reflects the time and expense of buying or selling, including spread, transaction cost, price impact, and immediacy. That framework can help describe market conditions, but it does not establish QuadrigaCX’s historical liquidity, whether customers could withdraw at a particular time, or why any customer experienced a loss. source

Accordingly, the infrastructure issues a complete case study would examine include the records supporting customer balances and trades, the specific custody and control arrangements, the allocation of responsibilities, and the evidence for operational continuity. These are questions to investigate, not findings about QuadrigaCX. The supplied evidence supports only general distinctions about exchange functions, custody, order books, and liquidity. It does not establish the company’s chronology, collapse findings, proceeding outcomes, customer recoveries, or present status.

Sources and references