A special report for builders, miners, investors and newcomers. Source-led reporting checked November 16, with publication and observation dates kept separate.
Status context from the November 16 special and Moon revision 4. “In build” is Greywick’s label; testnet availability is not mainnet or full native-LTC route availability. Diagrams illustrate distinctions, not audited technical architecture.
Litecoin is an open-source payment network. LTC is its native asset. A wallet helps you use the network; an exchange account and a self-custody wallet put different people in control of the keys.
Start with the tradeoffs: monetary rules, mining, confirmation assumptions, privacy and who controls the software you use. Shared roots make for a useful comparison, not identical systems.
Explore wallet software, documentation and the LitVM testnet directory. Choose a small contribution: test a demo, improve an explanation or report a reproducible bug.
Which rules can I verify? Who holds the keys? What assumptions change when I use another layer? These are useful questions on either side of the table.
Protocol design, not a ranking of investments
Design choice
Bitcoin
Litecoin
What to ask
Nominal supply ceiling
21 million BTC
84 million LTC
Different unit counts do not establish a fair price or investment value.
Target block interval
10 minutes
2.5 minutes
Targets are averages, not guaranteed payment or finality times.
Subsidy halving interval
210,000 blocks
840,000 blocks
Both reduce new issuance by block height; calendar dates vary.
Proof of work
SHA-256d
Scrypt
Different mining systems; raw hashrate figures are not directly comparable.
Optional privacy route
Depends on tools and transaction design
MWEB extension blocks
MWEB is distinct from a rollup or an exchange’s wrapped token.
Parameters checked October 15 against Bitcoin Core and Litecoin Core. A shorter interval does not imply equal security after the same number of confirmations. Fees and payment experience vary by time, wallet and layer.
Luxxfolio reports a completed miner expansion and describes LuxxPool and LuxxWallet development. The company says MWEB and LitVM wallet features are still in development.
Company claims are attributed. Pool figures are dated November 11 and treasury figures November 9; neither becomes a November 18 balance.
Read the context ↗01Dated publisher announcement · original text reviewed
Luxxfolio’s October 29 release describes a non-binding letter of intent with Greywick to explore cLTC liquidity and borrowing applications on Canton. Further commercial commitments require a signed agreement.
A proposed reserve-backed representation is not native LTC. This announcement does not establish launch, redemption availability, DTCC acceptance or realized institutional demand.
Read the context ↗02Dated publisher announcement · original text reviewed
LitVM’s October 27 announcement describes work on Litecoin and Ethereum integrations for Charms and an infrastructure migration to Zeeve. These are publisher-described development plans and infrastructure changes.
Testnet transaction claims do not establish independently verified users or adoption. Read current network status before treating an end-to-end route as available.
A preserved selection from an earlier source scan, not an exhaustive live feed or the November 16 reporting update. Original publication dates remain visible. Read the LitVM Family special for replay markers, project sources and review-method notes.
The institutional field guide
Same asset. Different doors.
Follow the legal claim as carefully as the ticker. Native coins, fund shares and wrapped representations give their holders different rights.
01 / HOLD
Treasuries & custody
A company’s disclosed holdings and an exchange’s customer balances belong in different columns. Read the reporting date, custodian and ownership basis before comparing totals.
A share provides exposure under a product’s own terms. Compare issuer disclosures, fees, redemption rules and jurisdiction; a listing does not make every wrapper interchangeable.
Canton cLTC, Coinbase cbLTC and LitVM belong to different systems. Start with the issuer, network and stage, then investigate custody, redemption and application risk.
Zero baseline; the small movement stays small. Last-known observations carry forward across missing days. A balance change can reflect transfers, fees, revised coverage or a new disclosure.
The compiled categories
exchange10.95M LTC
68.6% of compiled total · 14 records
investment2.47M LTC
15.5% of compiled total · 23 records
ecosystem1.41M LTC
8.8% of compiled total · 12 records
treasury0.80M LTC
5.0% of compiled total · 12 records
miner0.34M LTC
2.1% of compiled total · 41 records
government0.01M LTC
0.1% of compiled total · 1 records
Adapted from Litecoin Register under CC BY 4.0; cutoff selection, aggregation and charting by LTC Media. Categories may overlap economically. This is not a unique-coin census, circulating-supply share, beneficial-ownership map or independently audited reserve total.
05 / Historical layer guide · Sources checked November 3
Follow the coin. Then follow the claim.
Read this map horizontally: base money → representation → application. These are research categories, not a claim that every system connects to every other.
A practical map of the different systems
Asset / route
Where to look
The essential question
Native LTC / MWEB
Litecoin protocol and supported wallets
Who controls my keys?
cbLTC
Coinbase issuance and Base applications
What custody and redemption terms apply?
cLTC
Greywick and Canton documentation
What is live, who is eligible, and what backs the claim?
LitVM / zkLTC
Official network and bridge documentation
Is this testnet or production, and what verifies the bridge?
01
The base network
Native Litecoin
LTC moves under Litecoin’s own consensus rules. MWEB provides an optional confidential route within the protocol. A token elsewhere is a different representation.
Coinbase documents cbLTC backed 1:1 by LTC held in its custody, with direct support on Base. A third-party bridge to Solana adds another system and its own dependencies.
Greywick describes one cLTC per LTC in a reserve, with transfers between credentialled holders. Its home page still labels the product “In build.” Luxxfolio’s October 29 announcement concerns a non-binding liquidity LOI, not a completed treasury allocation or verified launch.
LiteForge is the active testnet. LitVM’s October 27 V2 announcement describes Charms integration work and a migration to Zeeve. Current network documentation says that migration is not complete; full-route availability and mainnet details require release documentation. Test zkLTC is separate from native LTC.
MWEB lets supported wallets take a confidential route within Litecoin. It conceals amounts inside extension blocks; the surrounding wallet, network and entry/exit behavior still matter.
Full nodes check the rules their operators choose to run. Developers propose code; miners produce blocks. A Foundation announcement, company investment or token vote does not automatically rewrite Litecoin’s rules.
Custodians control the assets entrusted to them. Product issuers define their wrappers. Legislators, regulators and courts affect access and obligations. These powers are different from validating a native Litecoin transaction.
A useful public square welcomes hard questions about privacy, censorship, recovery and concentrated influence. We ask for sources and demonstrations, and leave room for disagreement without turning it into a loyalty test.
Descriptor-wallet libraries with native MWEB work and language bindings.
The listing says independent review of the funds path is not complete. This is not Lightning Dev Kit.
Public prototype; review pending · Source review Oct 4, 2026
LiteForge directory snapshot / collected Oct 15, 2026
87 entries. A workshop worth exploring.
All entries visible at that collection, including the explorer. The list is a dated snapshot; the current network-status documentation governs availability. Grouped by the directory’s own categories; names link to project sites. Inclusion is not endorsement, an audit, mainnet readiness or evidence that a project spoke in the community Space.
The official testnet directory cautions that applications may be unaudited. This page has not connected a wallet, deposited funds or independently tested each app. Testnet participation does not promise a token allocation.
The deeper fieldbook / preserve the research trail
Keep asking. Keep checking.
New sections above carry their own dates and source links. The original October 4 research remains available below as historical context, including its privacy roadmap, wallet notes and publication limits.
A foundation. An open network. Different jobs.+
Original review October 4, 2026 · Foundation mission and project listings
The Litecoin Foundation describes its mission as adoption, awareness and development. Its public project directory gives readers a place to follow software, education and contributor work.
A directory entry tells us a project is listed. It does not make every project Foundation-owned, independently audited or ready for production. Our fieldbook keeps those distinctions visible.
Original review October 4, 2026 · Activated protocol feature · Historical explainer
The Foundation reported MWEB activation in May 2022. Users can keep using transparent Litecoin transactions or use supported wallets to move into the extension-block system.
Inside MWEB, transaction amounts are concealed and old transaction data can be pruned. Entering and leaving that system are separate steps. Confidentiality is a property to understand, not a promise that every surrounding activity becomes anonymous.
Original review October 4, 2026 · Historical developer report · Not a current incident alert
David Burkett’s postmortem describes a validation flaw, an inflated pegout, coordinated recovery and a later denial-of-service/reorganization incident. It reports fixes, including Litecoin Core 0.21.5.4 for the April failure mode.
We link the developer’s account so readers can inspect the response and its tradeoffs. This summary is not an independent audit, a current version recommendation or a claim that all future risks are resolved.
Original review October 4, 2026 · LiteForge testnet documented · Mainnet TBD
LitVM announced its LiteForge testnet on April 17, 2026. Its network documentation still labels mainnet as coming soon with a date to be determined. A test environment gives developers a place to learn; it does not prove a production system is ready.
The current architecture describes Arbitrum Nitro execution, Succinct SP1 proofs, Espresso sequencing and BitcoinOS Grail bridging. Its roadmap starts with Ethereum settlement and targets Litecoin settlement later. These are project-described components and phases, not an LTC Media deployment audit.
Original review October 4, 2026 · Project announcement · Implementation not independently verified
On August 26, 2026, LitVM announced a Web3 privacy initiative and identified SilentSwap as an early participant. Its article describes planned support for both LTC and zkLTC.
This is a separate ecosystem initiative from Litecoin’s activated MWEB feature. The announcement does not by itself verify a live production integration, bridge safety, current liquidity or direct MWEB compatibility.
Original review October 4, 2026 · Foundation product announcements
The Foundation announced Nexus for Android and iOS on June 6, 2025. Its May 28, 2026 update announced in-app gift-card purchases, alongside its existing payments and optional privacy features.
The original launch notice scheduled the older Litewallet app’s sunset for December 31, 2025. This fieldbook points readers to current official product information instead of presenting the older wallet as a newly maintained release.
Independent AI-assisted editorial by AI Satoshi Ma / LTC Media, a Satnam Satoshi project. No affiliation with the Litecoin Foundation, Bitcoin Core or the projects featured is implied. No independent human fact-check or product audit is claimed. Sources can change; submit corrections with evidence through our reporting guide.
ISSUER RECORD / SOURCE REVIEW NOVEMBER 9, 2026
Same asset. Different dates.
A tracker observation, a balance-sheet date and a fund’s daily holdings answer different questions. Read the date beside each number.
Issuer disclosures and tracker context · checked November 9, 2026
The NAV panel has an earlier date than the holdings table. Asset-value changes are not automatically inflows.
The Register aggregate remains the source’s compiled series. We do not silently replace a historical tracker row with a later filing or add custody, fund backing and company holdings as unique coins.
THE TREASURY & DISTRIBUTION DESK
A number needs a date.
Saved source check 2026-11-19T01:05:33.511Z. 103 eligible records; recorded aggregate 15,970,213.37 LTC. Source observations retain their dates.
Secondary compiled records may overlap. This is not a unique-coin census, audited reserve or fund-flow series. Negative changes are recorded balance changes, not proof of sales. Missing baselines remain unknown.
Ten largest eligible register records · 30-day comparison · LTC
Record
Recorded balance
Observation date
30-day change
Binance Exchange
5,064,980.98
2026-11-18
-259,194.72
OKX Exchange
3,021,512.84
2026-11-18
40,775.25
Grayscale Litecoin Trust
1,950,265.36
2026-11-18
-3,877.91
ByBit Exchange
1,194,754.67
2026-11-18
-59,593.54
Lite Strategy, Inc.
751,798
2026-09-30
0
Binance-Peg Litecoin
745,000.1
2026-01-14
0
Japan Virtual and Crypto Assets Exchange Association
652,468
2026-09-01
0
Gate Exchange
553,534
2026-10-18
0
Mimblewimble Extension Blocks
532,056.78
2026-11-18
63,177.13
Binance Pool
299,876.21
2026-11-11
0
Source: Litecoin Register · CC BY4.0. This on-demand cloud check works without the Mac; it does not generate articles or rewrite saved editions.