Methodology

The register records how much Litecoin (LTC) publicly known organizations hold, and exactly how we know. A figure without a source, a date and a method does not go in.

What a record contains

Each entity has a stable id that never changes and appears in all of its URLs. A record holds ahistory of holding snapshots. Each snapshot has:

A record can also have a file of attributed addresses.

The current holding is the snapshot with the latest as_of date. Full field definitions are in the JSON Schema.

Categories

Exchange exchange
A trading venue, broker or custodian holding LTC, usually on behalf of customers. Figures normally reflect customer balances, not the company’s own treasury.
  • Centralized exchange centralized-exchange: A custodial trading platform holding customer LTC.
  • Broker broker: A brokerage or investment app that holds LTC for its customers.
  • Swap service swap-service: An instant-exchange service that holds LTC reserves to fill swaps.
  • Industry aggregate industry-aggregate: Combined holdings reported for a group of exchanges, such as a national industry association.
Investment product investment_product
An ETF, ETP, trust or fund whose shares are backed by LTC. The figure is the LTC held by the product, not by its sponsor.
  • Single-asset fund single-asset-fund: An ETF, ETP or trust holding only LTC.
  • Multi-asset fund multi-asset-fund: An index or basket product holding LTC alongside other crypto assets.
Company treasury corporate_treasury
A company holding LTC on its own balance sheet as a treasury or investment asset, including mining companies holding coins they produced.
  • Public company public-company: A company whose shares are publicly listed.
  • Private company private-company: A company whose shares are not publicly listed.
  • Mining company mining-company: A company operating its own Scrypt mining hardware and holding LTC, including coins it mined, on its balance sheet.
Miner miner
A mining pool that mines Litecoin (typically merge-mined with Dogecoin), identified by its coinbase tag. The figure is the LTC it mined that has never been spent. Mining companies are listed under Company treasuries.
  • Mining pool mining-pool: A pool identified by its coinbase tag; the figure is coins it mined that remain unspent.
Government government
A national or sub-national government body holding LTC, whether as a reserve asset or as funds seized through legal process.
  • Seized funds seized-funds: LTC taken into custody through seizure, forfeiture or other legal process.
  • Reserve holding reserve-holding: LTC held as a reserve or treasury asset by a government.
Ecosystem ecosystem
Protocols, extension blocks, bridges, wrapped tokens and other Litecoin infrastructure that hold or lock LTC, such as MWEB, the Lightning Network and wrapped LTC.
  • Layer 2 layer-2: A network built on top of Litecoin that locks LTC in its channels or contracts.
  • Extension block extension-block: A Litecoin protocol extension, such as MWEB, holding LTC moved into it.
  • Cross-chain protocol cross-chain-protocol: A protocol that holds native LTC to swap it with assets on other blockchains.
  • Wrapped token wrapped-token: A token on another blockchain backed by LTC held in reserve.
  • Collectible collectible: Physical coins or other collectibles loaded with LTC.

Methods

Proof of reserves proof_of_reserves
Cryptographic proof of on-chain balances, usually with an independent attestation of liabilities.
Regulatory filing regulatory_filing
A figure stated in a filing with a regulator or legislature, or in audited financial statements.
Court record court_record
A figure stated in a court order, indictment or other court document.
Self-reported self_reported
Published by the entity itself (press release, factsheet, website) without independent verification.
On-chain attribution on_chain_attribution
The summed balance of addresses attributed to the entity. Usually a lower bound.
Third-party estimate third_party_estimate
An estimate published by an analytics firm, journalist or researcher, without on-chain proof.

Attributed addresses

For on-chain attribution figures, the register publishes the addresses whose balances are summed, so anyone can check the figure on a block explorer. They are kept in a separate file per entity,/data/addresses/{id}.csv, linked from the entity's sources, rather than on its page. Each address belongs to at most one entity, so no balance is counted twice. The lists are kept current by the registry's address scanner:

Each file has three columns: address, label (what the address is used for) andattribution, which says who linked it to the entity:

Self-disclosed self_disclosed
The entity published the address itself, for example in a proof-of-reserves list.
Third party third_party
A named third party linked the address to the entity.
Inferred inferred
The registry linked the address to the entity, for example from a mining pool’s coinbase tag.

Records give the number of addresses as address_count and the file's URL as urls.addresses_csv.

USD values

Every figure is recorded in LTC. The LTC/USD toggle at the top of each page shows US-dollar values derived from the daily prices in /data/prices/ltc-usd.csv(4,911 days, 2013-04-28 to 2026-10-13):

Hover over a USD figure to see the LTC amount, price and date behind it.

How totals are computed

Totals add each entity’s most recent figure. Those figures have different as_of dates and methods, so a total is an approximation, not a point-in-time balance. Holdings may also overlap (e.g. an investment product’s LTC held in custody at an exchange).

Fixture records

Records with is_fixture: true are fictional placeholders used while the site is built. They useexample.com-style source URLs and, for governments, ISO user-assigned jurisdiction codes (XA–XZ). They must not be cited.

Machine access and crawling

All search engines and AI crawlers are welcome; see robots.txt. Every HTML page embeds schema.org JSON-LD and links to its JSON and Markdown equivalents with <link rel="alternate">. The site index for language models is at /llms.txt, and the whole register as one Markdown file is at /llms-full.txt. URLs and field names are versioned; breaking changes get a new /api/v2/ path.

Citing the register

Cite the entity page URL and the snapshot's as_of date, for example: “Litecoin Register, entityexample-id, holding as of 2026-09-30.” Where possible, also cite the primary source we link to.