₿ Bitcoin
Transactions in blocks
555,896
Counted from explorer-reported blocks; includes coinbase- Blocks in this UTC day
- 134
- Protocol block target
- 10 minutes
- Supply cap · protocol
- 21 million BTC
- Proof-of-work algorithm
- SHA-256d
LTC / THE DAILY EDITION
6 source briefings · Revision 1
6 sources collected · 2 unavailable

Lunch Time Conversations
A new testnet connection, an industry award and a growing builder directory. What changed, what users need to know, and what still needs proof.
Proof of Work / The daily magazine
Which observation has a genuinely new effective date?
This edition combines a dated source watch with original reading context. Publisher announcements, observations and historical material retain their own dates below.
AI-prepared by LTC Media. Not individually reviewed by a human editor. Data is a saved observation, with its own timestamp; illustrations are original conceptual art.LTC / The reading map
THE DAILY NEWS MAP · 2026-11-12

Since the previous published issue / Base source registry
Compared with 2026-11-11. These labels compare saved observations from the base registry; they do not summarize every event or the separate network, market and policy collections.
Source effective 2026-11-11T20:41:18Z; previous 2026-10-30T23:21:55Z. A recorded value or definition differs; no cause is inferred.
Source effective 2026-11-12T19:34:28.324Z; previous 2026-11-11T17:57:14.306Z. A recorded value or definition differs; no cause is inferred.
Source effective 2026-11-12T19:34:24.028Z; previous 2026-11-11T17:57:04.525Z. A recorded value or definition differs; no cause is inferred.
Source effective 2026-11-10; previous 2026-11-10. Rechecked context, not new news.
Source effective 2026-11-10; previous 2026-11-10. Rechecked context, not new news.
Source effective 2026-10-28T14:23:53Z; previous 2026-10-28T14:23:53Z. Rechecked context, not new news.
Source effective 2026-09-12T12:06:49Z; previous 2026-09-12T12:06:49Z. Rechecked context, not new news.
No accepted observation in this issue. Missing does not mean zero.
A reference check does not establish a newly measured fact.
No accepted observation in this issue. Missing does not mean zero.
A reference check does not establish a newly measured fact.
01 / The network pulse
A comparison starts with a shared definition and a shared time window. Blocks are assigned to a completed UTC day by their median block time. The figures below describe recorded activity—not a contest for the best coin.
2026-11-11 · Completed UTC day
2026-11-11T00:00:00.000Z → 2026-11-12T00:00:00.000Z
Transactions in blocks
555,896
Counted from explorer-reported blocks; includes coinbaseTransactions in blocks
Unavailable
Counted from explorer-reported blocks; includes coinbaseA comparison chart needs two complete observations for the same window. It is withheld when either network record is incomplete.
Active-address and fee figures are not derived from this block-metadata collector, so those fields remain unavailable. Native BTC and LTC fee amounts would use different units; do not rank them as though they were dollar costs. Block targets and supply caps are protocol context, not measured performance. Read the sourced protocol fieldbook →
Source: mempool.space ↗ · collected 2026-11-12T19:35:11.621Z · retrieved.
Source: Litecoin Space ↗ · collected 2026-11-12T19:36:56.342Z · failed.
A complete common-day BTC/LTC comparison is unavailable.
02 / The open-money desk
Native BTC and LTC, tokenized collateral and USDC are different assets. Four exact Morpho markets tell a small, clearly scoped part of the story.
Market 0xc2db905f…25815d
Supply APY3.44%
Borrow APY3.79%
Observed market state: . Rates are variable snapshots, not promised returns.
Chain ID 5042 · LLTV 86% (liquidation threshold, not a recommended borrowing level).
Collateral0x171A4217b86A807A64eB94757Db6849fb4bDbAA0
USDC loan asset0x3600000000000000000000000000000000000000
Market ID0xc2db905f174e5defcce01d321b09f15f78856a36a21b90cc7e1abbc29225815d
Market 0xabd17639…b7b566
Chain ID 5042 · LLTV 86% (liquidation threshold, not a recommended borrowing level).
Collateral0x171A4217b86A807A64eB94757Db6849fb4bDbAA0
USDC loan asset0x3600000000000000000000000000000000000000
Market ID0xabd1763943714b96b6590238d484a240019b4b842eb67fbcff7d96c081b7b566
State is older than 15 minutes; rates and liquidity are withheld.
Market 0x9103c3b4…191836
Supply APY4.5%
Borrow APY5.32%
Observed market state: . Rates are variable snapshots, not promised returns.
Chain ID 8453 · LLTV 86% (liquidation threshold, not a recommended borrowing level).
Collateral0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf
USDC loan asset0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Market ID0x9103c3b4e834476c9a62ea009ba2c884ee42e94e6e314a26f04d312434191836
Market 0x9125d0fa…4583c3
Supply APY5.64%
Borrow APY6.71%
Observed market state: . Rates are variable snapshots, not promised returns.
Chain ID 8453 · LLTV 62.5% (liquidation threshold, not a recommended borrowing level).
Collateral0xcb17C9Db87B595717C857a08468793f5bAb6445F
USDC loan asset0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Market ID0x9125d0fa03c3137166df68bcc72283477830de2a4a5536512374c573ad4583c3
Bars share a zero baseline and a common scale within this issue. cbBTC/cbLTC on Base and cirBTC on Arc are tokenized collateral with issuer, redemption and chain dependencies. USDC is the loan asset here; “supply APY” does not mean an interest rate on native BTC or LTC. LLTV, collateral valuation and rate risk are separate. No wallet, lending action or recommendation is offered.
bitcoin-blocks ↗
retrieved · 2026-11-12T19:35:11.621Z
Parser ltc-intelligence-v1f88ec2f6b2b88c90696606ab952391a7720dcde9d5dfdd573522e120c2d0177a
litecoin-blocks ↗
failed · 2026-11-12T19:36:56.342Z
Parser ltc-intelligence-v177dd6fe29f29609817dd426471609f75887d2b21d6bddb823133b84d359313bd
morpho-verified-markets ↗
retrieved · 2026-11-12T19:36:56.694Z
Parser ltc-intelligence-v1027956966c51c164346c0ae34aa0944f55971b7ce0248d2547a5c664620d101e
03 / Politics & public records
A proposal is not a final rule. An agency statement is not an independent finding. The original document is the starting point.
THE POLICY READING ROOM
Follow dated SEC and CFTC releases. Read the jurisdiction, action and effective date before adding a market narrative.
Official agency feed
Official press-release title, linked in its original context. This dated agency record is not a claim that the event happened on this issue’s publication day.
Official press-release title, linked in its original context. This dated agency record is not a claim that the event happened on this issue’s publication day.
Checked 2026-11-12T19:36:56.862Z · collected
Open the agency feed ↗Official agency feed
Official press-release title, linked in its original context. This dated agency record is not a claim that the event happened on this issue’s publication day.
Official press-release title, linked in its original context. This dated agency record is not a claim that the event happened on this issue’s publication day.
Checked 2026-11-12T19:36:56.854Z · collected
Open the agency feed ↗The selected long read / 2026-11-12
Dated source check · prepared for 2026-11-12. Read the original publications and the coverage gaps; the commentary is AI-prepared reading context.
13Keep reporting dates, legal conditions, reserve evidence and asset representations separate.
Litecoin / Treasury and Canton / Source-linked ecosystem special · dated evidence and context
Issuer disclosures, the Canton cLTC proposal and a timestamped Register inventory each have their own evidence and clock.
Lite Strategy’s November 10 results report 751,798 LTC as of September 30, including 64,700 LTC pledged for covered-call activity. Its approximately $130,000 in quarterly premiums should not be confused with its $16 million net-income figure, which largely reflects asset remeasurement. The same release reports $1.7 million in liabilities: debt-free does not mean liability-free. These are dated issuer disclosures, not today’s holdings or a trading recommendation.
Luxxfolio’s October 29 release describes a nonbinding October 27 letter of intent with Greywick for potential cLTC liquidity on Canton. Further commercial terms, reserves, attestation and technical readiness are separate milestones. A newer corporate update was published November 12, but the reviewed evidence did not establish a later binding cLTC agreement. The Canton arrangement remains an institutional-development watch rather than evidence of live cLTC trading volume.
In its November 12 corporate update, Luxxfolio reports 50 newly commissioned L9 miners, bringing its fleet to 338 machines and approximately 5.58 TH/s of nameplate capacity. It reports LuxxPool at 7.7 TH/s and 520 workers as of November 11, and estimates treasury holdings of 26,838.23 LTC as of November 9. These are company-reported figures with different dates, not independently audited current totals. The company says it allocates 5% of its own pool fees to the Litecoin Foundation. LuxxWallet’s MWEB and LitVM work remains in development.
The symbols must remain distinct. Native LTC is the Litecoin asset; LitVM’s zkLTC is associated with its asset and testnet design; Greywick’s cLTC concerns Canton; Coinbase’s cbLTC is another wrapped representation. Similar names do not mean common custody, common redemption rights, equivalent security or interchangeable network support. The publication should compare each structure on its own documented terms.
Litecoin Register’s November 12 snapshot checked at approximately 18:46 UTC lists 98 holders and 15,428,199 LTC across its categories: exchanges 10,392,125; products 2,476,883; ecosystem 1,404,140; corporate 802,608; miners 341,678; and government 10,765. These categories reconcile to the displayed total, but the underlying reporting dates span November 14, 2013 to November 12, 2026. The tracker explicitly warns about possible double-counting where funds hold assets at exchanges. This is a dated tracker inventory, not proof of unique beneficial ownership or a daily purchase flow.
Greywick’s homepage still labels cLTC as in build in the November 12 check, with its latest newsroom item dated October 29. Product descriptions of reserves and credentialed holders do not establish that issuance, redemption or institutional trading is operating. A production-launch claim remains withheld pending explicit release and operating evidence.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
04Treat this as a testnet infrastructure and configuration update.
Litecoin / The lead / Source-linked ecosystem special · dated evidence and context
LiteForge moves from Caldera to Zeeve. The Foundation reminder explains what existing testnet users need to change.
LiteForge, LitVM’s test network, has moved its infrastructure from Caldera to Zeeve, according to LitVM’s announcement and current documentation. The Litecoin Foundation amplified the change with a practical configuration notice. This is the most immediate action item in the two posts supplied for this issue: existing users need current network connection details.
The team’s announcement was published November 11 at 01:01 UTC, which was November 10 at 8:01 p.m. in New York. The Foundation reminder followed November 12 at 02:39 UTC, or November 11 at 9:39 p.m. New York time. The dates describe an announcement and a later reminder, not two different network upgrades.
A remote procedure call endpoint is the server address a wallet or application uses to query the chain and submit transactions. A block explorer is the web interface for inspecting transactions and addresses. Changing these addresses changes how a user reaches the network; it does not by itself mean the underlying asset has changed or that a mainnet has launched.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
05Separate wallet HTTP configuration from developer WebSocket configuration; verify the official record before acting.
Litecoin / Practical guide / Source-linked ecosystem special · dated evidence and context
Chain ID 4441 and zkLTC stay unchanged; the documented HTTP connection changes and the old WebSocket is no longer active.
LitVM lists the new HTTP RPC as https://rpc.testnet.liteforge.zeeve.net/ and the explorer as https://explorer.testnet.liteforge.zeeve.net/. Chain ID 4441 and the gas-token label zkLTC remain unchanged. The Foundation says users can edit the existing network configuration rather than add it again.
The documentation also lists a Zeeve faucet at https://faucet.testnet.liteforge.zeeve.net/. Before changing wallet settings, verify each address directly against the official documentation. A faucet or configuration update should never require a seed phrase or private key. Testnet activity is for experimentation; test tokens should not be presented as redeemable native LTC.
The official configuration and status pages checked again on November 12 at 18:42 UTC say the old Caldera WebSocket endpoint is no longer active. The Zeeve HTTP RPC is the supported connection in the reviewed documentation; a replacement WebSocket service is not confirmed operational. Developers should remove reliance on the old WebSocket endpoint and consult the current documentation rather than infer that HTTP also provides WebSocket support.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
06Keep native Litecoin, testnet tokens, execution and settlement separate in every diagram.
Litecoin / Technical explainer / Source-linked ecosystem special · dated evidence and context
EVM execution, Ethereum settlement and an intended native-LTC route are different layers. Mainnet availability still needs proof.
LitVM’s current architecture documentation describes an Arbitrum Orbit EVM chain with Ethereum settlement. It also describes an intended route involving native LTC, Charms/zkLTC, Ethereum, Arbitrum and LitVM. These are distinct layers, each with its own operational and trust questions.
EVM compatibility lets developers use a familiar application environment. It does not make an application a native Litecoin transaction, and a settlement description is not interchangeable with the origin of an asset. Readers should not describe this architecture as Litecoin-settled based solely on Litecoin branding.
The important next evidence is an official release record identifying production parameters, supported deposits and withdrawals, deployed contracts, upgrade authority, audit findings and failure recovery. Testnet zkLTC use does not establish that the entire native-LTC route is available to the public. The migration announcement’s forward-looking mainnet language is not a mainnet launch notice.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
07Celebrate the recognition with source attribution, not unsupported performance claims.
Litecoin / Recognition / Source-linked ecosystem special · dated evidence and context
The Foundation’s November 6 post celebrates AIBC recognition. The dedicated winners list corroborates the award, not adoption metrics.
The dedicated AIBC winners list corroborates the Foundation’s November 6 announcement that Litecoin won the Best Layer-1 Blockchain award at AIBC’s Rome awards and directs readers to the organizer’s winners page. This belongs in the issue as recognition of the ecosystem, with the Foundation and organizer identified as the sources.
The Foundation describes the category as recognizing technical excellence, scalability and developer adoption. Those category criteria should not be converted into an independent measurement of Litecoin throughput, security, market share or application usage. An award announcement supports a recognition story; technical and adoption claims require their own data.
For the community, recognition can be a useful introduction to educational material and active projects. The editorial opportunity is to show newcomers what they can inspect next: native Litecoin development, privacy work, payments and the changing testnet application environment.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
08Explore the directory by category, then verify each project independently.
Litecoin / Ecosystem inventory / Source-linked ecosystem special · dated evidence and context
The official directory contains tools and experiments as well as applications. Inclusion is not a security audit.
The official LiteForge directory bundle reviewed for this package contains 97 entries. Ninety-six are not marked comingSoon, but that count includes an explorer and infrastructure tools; one entry is a More Apps placeholder. We therefore do not call it 96 live or audited dApps.
The companion inventory preserves project names, categories, destinations and published status flags. It is a discovery list for readers and a research queue for the newsroom. A directory listing does not establish audited contracts, available liquidity, active users, revenue or production readiness.
Useful follow-up reporting should classify a project by what is actually available: concept, testnet interface, documented contract, source repository, verified production release or measured usage. Every numerical claim should carry a source and date. Readers should also distinguish the project’s own description from something the newsroom has tested.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
09Measure release evidence and user outcomes, not the number of promotional posts.
Litecoin / What to watch / Source-linked ecosystem special · dated evidence and context
Production parameters, audits and operating evidence matter more than a launch-shaped headline.
The most useful follow-up to the migration is a dated operational record: updated developer documentation, reproducible network checks, deployment identifiers and a published account of what changed. A second social post repeating the announcement is not a second milestone.
For the applications listed around LiteForge, a durable project profile should record its repository, deployment network, audit status, upgrade controls, incident notices and an actual usage measure when one is available. Missing evidence should remain visible rather than be replaced with an enthusiastic estimate.
LTC will keep this special separate from the market tape. Daily prices, ETF flows, institutional holdings and lending rates must be refreshed through their own dated source records, not copied from an earlier PDF or inferred from ecosystem announcements.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
10Native software deserves a separate development desk, with version dates and audit limits visible.
Litecoin / Core and wallets / Source-linked ecosystem special · dated evidence and context
Core maintenance and the prototype Development Kit belong in the same reading map, with different maturity labels.
Litecoin Foundation’s project inventory spans Core, MWEB, the Development Kit, Electrum-LTC, Litecoin Computer, Litecoin Space, LTCSuite and other tools. These projects are not all LitVM applications. The distinction matters: native protocol and wallet work can improve how people use Litecoin without depending on a separate application chain.
The latest public Core release observed in the primary release listing is v0.21.5.8, dated September 12. Its notes discuss MWEB validation, relay, mining and resource-management changes. It is a relevant software baseline, not a new November announcement. Operators should read official release notes and verification instructions rather than treat the version label as an investment signal.
The Development Kit currently describes a v0.4.6 reference desktop wallet for Apple Silicon macOS and Linux x86_64, Rust/BDK-derived MWEB support, a Tauri interface and experimental mobile bindings. It explicitly calls the work a prototype that has not been independently audited. Independent review of funds-related code and signed releases are among its stated funding priorities.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
11Put shipped features, historical incidents and current software guidance in the same reader-friendly context.
Litecoin / Wallets and security / Source-linked ecosystem special · dated evidence and context
Historical Nexus and MWEB records provide context, not a new announcement or blanket safety claim.
Nexus is a shipped wallet rather than a concept. The Foundation’s May 28 update describes gift-card features, MWEB, Tor, coin selection and Flexa. This is historical product context for newcomers, not a fresh November launch. Merchant, provider and jurisdictional requirements can differ even when a wallet supports privacy features.
The Foundation’s April 28 MWEB postmortem is essential historical context. It discusses a March validation exploit and recovery, followed by an April malformed-block handling failure and a 13-block invalid-chain reorganization. Its impact descriptions differ between the incidents. A blanket statement that there were no losses or no security incidents would erase those distinctions.
The useful editorial bridge is to explain what changed in software, how operators verify upgrades and what a wallet’s privacy features actually cover. Privacy claims should identify the relevant network and threat model; they should never promise immunity from merchant checks, exchange policies or all forms of traceability.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
12Explain the experimental design and its risks before introducing any financial metric.
Litecoin / Applications / Source-linked ecosystem special · dated evidence and context
A testnet lending interface should not be mistaken for an investable yield product.
The directory groups lending, decentralized exchange, payment, AI, tooling, game and collectible projects. Representative listings include Lithium and Ayni, LitVMSwap and LiteSwap, LitRoute, Dappit, Lester Labs, LitZap and LitAgent. These names are directory observations, not an endorsement or a claim that their contracts have been independently inspected.
LitVMSwap’s own lending page describes bridged-USDC lending against zkLTC and explicitly says both testnet tokens have no value. The metrics extracted during research were placeholders, so this special does not publish APY, total value locked or liquidity figures from that view. The page describes withdrawals subject to available liquidity and a seven-day delay for risk-increasing vault changes.
A reported November 9 Lithium partnership or investment points to a LitVM social post that the ecosystem desk could not yet retrieve directly. Its amount, conditions and production readiness remain outside the verified package. The entry stays on the source-check list rather than being converted into a definitive funding announcement.
Checked November 12, 2026 · Source dates and availability limits retained · Prepared for 2026-11-12; source check 2026-11-12. Not individually reviewed by a human editor.
The conversation is open
New to open money? Deep in the rabbit hole? Start where you are. Useful work can be a source check, a lesson, a translation or a thoughtful contribution.
Bitcoin & builders
Source-effective date
The official Bitcoin Core repository’s latest-release endpoint returned v32.1, published October 28, 2026. This briefing records the endpoint result; it does not present the release as today’s announcement.
A version announcement describes software, not adoption across a network or a market forecast. Read the upstream notes and verification instructions before deciding whether an update suits your setup.
Follow the evidenceBitcoin Core · software releases ↗
A release announcement is evidence of software publication, not universal adoption.
Identify the exact version and its original publication date.
A node independently checks blocks against its consensus rules.
Keep the block record separate from software version statistics.
Before you concludeCheck the canonical release, signatures and operator instructions.
Litecoin & proof of work
Source-effective date
The official Litecoin Core repository’s latest-release endpoint returned v0.21.5.8, published September 12, 2026. This briefing records the endpoint result; it does not present the release as today’s announcement.
A version announcement describes software, not adoption across a network or a market forecast. Read the upstream notes and verification instructions before deciding whether an update suits your setup.
Follow the evidenceLitecoin Core · software releases ↗
A release announcement is evidence of software publication, not universal adoption.
Identify the exact version and its original publication date.
A node independently checks blocks against its consensus rules.
Keep the block record separate from software version statistics.
Before you concludeCheck the canonical release, signatures and operator instructions.
Lightning & builders
Source-effective date
The official LND repository’s latest-release endpoint returned v0.21.8-beta, published November 11, 2026. This briefing records the endpoint result; it does not present the release as today’s announcement.
A version announcement describes software, not adoption across a network or a market forecast. Read the upstream notes and verification instructions before deciding whether an update suits your setup.
LND uses a beta suffix in the version name returned by its latest-release endpoint. Our parser preserves that suffix and rejects releases marked as drafts or prereleases by GitHub, as well as release-candidate tags. This is a description of the upstream channel, not a safety certification.
Follow the evidenceLND · Lightning software releases ↗
Public capacity is not payment volume. Channel balances and routing constraints matter.
Onchain transactions establish funded payment channels.
A payment can cross connected channels with sufficient directional liquidity.
Channel closure settles balances onchain under the channel’s rules.
Before you concludeCheck the invoice, expiry and actual payment state.
Market snapshot
Source-effective date
Coinbase Exchange returned a BTC/USD last trade of $71,466.82, timestamped 2026-11-12T19:34:28.324Z. This venue-reported trade was retrieved at 2026-11-12T19:34:30.476Z; the two times are recorded separately.
This is one exchange’s sampled last trade, not a global reference price, a live quote after publication or a 24-hour closing price. It does not establish a return, market-wide volume or a trend.
For newcomers: a quote belongs to a venue, a trading pair and a moment. For experienced readers: inspect the exact decimal value, source timestamp and parser in the sourcebook before making comparisons.
Follow the evidenceCoinbase Exchange · BTC/USD last trade ↗
One venue’s last trade is a sampled observation, not a universal price.
Match the asset, currency pair and trading venue.
Keep the trade time separate from the collection time.
Use the same units and a defined window before calculating change.
Before you concludeRead the pair, venue and exact trade time together.
Market snapshot
Source-effective date
Coinbase Exchange returned a LTC/USD last trade of $49.726, timestamped 2026-11-12T19:34:24.028Z. This venue-reported trade was retrieved at 2026-11-12T19:34:30.476Z; the two times are recorded separately.
This is one exchange’s sampled last trade, not a global reference price, a live quote after publication or a 24-hour closing price. It does not establish a return, market-wide volume or a trend.
For newcomers: a quote belongs to a venue, a trading pair and a moment. For experienced readers: inspect the exact decimal value, source timestamp and parser in the sourcebook before making comparisons.
Follow the evidenceCoinbase Exchange · LTC/USD last trade ↗
One venue’s last trade is a sampled observation, not a universal price.
Match the asset, currency pair and trading venue.
Keep the trade time separate from the collection time.
Use the same units and a defined window before calculating change.
Before you concludeRead the pair, venue and exact trade time together.
Wall Street & institutions
Source-effective date
The iShares Bitcoin Trust ETF holdings file reports 792,005.02580 BTC and 1,401,280,000.00 shares outstanding as of November 10, 2026. The source supplies a date, not an intraday timestamp.
This is an issuer-reported balance at a point in time. It is not a live price, independently audited total or measurement of money entering the fund. Holdings changes alone are not ETF flows.
For newcomers: read the “as of” date before comparing a number. For experienced readers: the source notebook preserves the exact decimal strings, parser version and retrieved-file hash for this observation.
Follow the evidenceiShares Bitcoin Trust ETF · holdings ↗
A higher dollar balance can reflect a price change without new investor money.
A quote values an asset at a particular moment.
A balance counts assets held at a disclosed cutoff.
Net creations and redemptions describe movement during an interval.
Before you concludeA flow needs a defined session, complete universe and stated method.
The complete issue / 29 sections
Markets, builders, public policy and the communities behind them. Illustrated desk spreads carry the context saved with this issue. Open the notebook to go deeper. A reference is not a fresh measurement; unavailable numbers stay unavailable.

The reference’s opening tape includes BTC, LTC, XLM, DOGE and PEPE. Our daily collector currently supplies validated BTC/USD and LTC/USD last-trade snapshots. The other three remain named research lines, with no invented quote or daily return.
Explore the desk ↗A proposal can change or be withdrawn. It does not establish the final rule.
An agency puts a proposed action into the public record.
Comments and later agency actions belong to the same dated record.
If a final rule follows, inspect its scope and effective date separately.
Before you concludeKeep agency, docket, legal status and effective date visible.
The SEC and CFTC have distinct responsibilities. LTC follows their original records and the legal status of each action; an agency announcement does not establish approval of a token, a lending market or our community project.
Explore the desk ↗A higher dollar balance can reflect a price change without new investor money.
A quote values an asset at a particular moment.
A balance counts assets held at a disclosed cutoff.
Net creations and redemptions describe movement during an interval.
Before you concludeA flow needs a defined session, complete universe and stated method.
This is the home of the Bitcoin ETF flow tape: completed-session totals, constituent products and rolling windows. The 29-page reference included these fields; the current validated daily dataset does not yet contain a comparable flow series.
Explore the desk ↗Buying a security and holding native Bitcoin are different ownership arrangements.
Identify the asset or exposure the product references.
Inspect custody, legal form, fees and redemption terms.
Read the rights attached to the security you actually hold.
Before you concludeMatch the exact product, legal structure, issuer and prospectus.
A useful global register compares instruments before ranking them. The original design’s Top 21 is a coverage ambition, not evidence that twenty-one current rows have been independently reconciled.
Explore the desk ↗Fund units, company equity and preferred securities do not grant identical rights.
Start with the disclosed entity and its holdings.
Read debt, preferred claims and custody arrangements.
Locate the investor’s claim within that structure.
Before you concludeDistinguish company assets from assets held for clients.
A fund, an operating company and a corporate capital strategy should not be collapsed into one league table. The first task is to identify who owns the asset and what security a reader is observing.
Explore the desk ↗Coins held for customers are not automatically a company’s treasury.
Record the native asset and disclosed quantity.
Identify who owns it and who holds the keys.
Keep debt and shareholder rights beside the asset disclosure.
Before you concludeFind the issuer record, as-of date and any encumbrances.
This desk follows corporate Bitcoin disclosures, capital raises, dilution and the difference between gross reserves and the claim attached to a share. The reference’s tracker ranking is a research lead; it is not a current, reconciled register.
Explore the desk ↗Two mNAV figures can disagree because their formulas or cutoffs differ.
Identify the security, price and share-count basis.
Use the holdings and asset price from compatible cutoffs.
Explain cash, debt and preferred claims before comparing multiples.
Before you concludeState the numerator, denominator and treatment of debt and dilution.
mNAV is not a universal formula. A useful valuation desk shows the method before the number: equity value or enterprise value, gross or adjusted asset value, securities included, prices and the common cutoff.
Explore the desk ↗Custody, beneficial ownership and wrapped backing can describe the same coins.
Begin with the native Litecoin asset.
Identify treasury, custodian, product or wrapped reserve.
Trace the disclosed rights and avoid counting the same backing twice.
Before you concludeDo not add overlapping categories into a supposed total.
The Register supplies an attributed view of entities associated with LTC. A tracker’s entity count or aggregate can change because its classification or observed universe changes. That alone is not evidence of market buying.
Explore the desk ↗A dedicated Litecoin product and a multi-asset basket need different labels.
Identify native LTC, derivatives or a basket allocation.
Keep the legal structure and fees beside the name.
Check identifiers so cross-listings do not become duplicate holdings.
Before you concludeRead the issuer document before comparing exposure.
A Litecoin trust, ETF, ETP and multi-asset basket can carry different exposure and legal structures. A basket containing LTC is not automatically a dedicated Litecoin fund. The reference’s twenty rows remain a historical research universe.
Explore the desk ↗A company announcement needs an asset date and a clearly identified entity.
Find the original issuer or filing record.
Read holdings, debt and any restrictions together.
Keep the share-count basis and cutoff with per-share calculations.
Before you concludeSeparate reported holdings from estimates and computed values.
This desk follows companies reporting LTC, their original filings and the share basis behind per-share calculations. A shorter verified list is more informative than an invented twenty-company league table.
Explore the desk ↗
Foundation coverage has its own place in LTC: wallet releases, merchant tools, education, public events and engineering support. The publication date belongs beside every announcement, even when an older article remains the most recent item returned.
Explore the desk ↗
MWEB coverage follows Litecoin’s extension-block engineering, validation, wallet support and disclosed incidents. Privacy language should explain what a system hides, what remains visible and what an operator must verify.
Explore the desk ↗A release announcement is evidence of software publication, not universal adoption.
Identify the exact version and its original publication date.
A node independently checks blocks against its consensus rules.
Keep the block record separate from software version statistics.
Before you concludeCheck the canonical release, signatures and operator instructions.
Bitcoin Core coverage follows official releases, changes and verification instructions. A release label does not measure network adoption, and a downloaded binary does not prove its own origin.
Explore the desk ↗Public capacity is not payment volume. Channel balances and routing constraints matter.
Onchain transactions establish funded payment channels.
A payment can cross connected channels with sufficient directional liquidity.
Channel closure settles balances onchain under the channel’s rules.
Before you concludeCheck the invoice, expiry and actual payment state.
Lightning coverage connects software releases with the practical questions of channels, routing, liquidity and payments. A conceptual channel diagram is an illustration, not a measured map of the network.
Explore the desk ↗Block timestamps, a node’s observation time and an estimated future event are different fields.
A block references its predecessor.
Nodes check proof of work and the applicable consensus rules.
An observer records when that block was seen; forecasts remain estimates.
Before you concludePreserve the block hash, height, source and observation time.
This desk preserves the Timechain theme from the design: block height, block hash, timestamps, fees, difficulty progress and halving estimates. A live dashboard reached in a browser is not a reproducible numeric source unless the relevant observation is captured.
Explore the desk ↗Proof of work and independent validation have different jobs in the same system.
Miners perform proof of work to propose candidate blocks.
Nodes validate the block and its transactions.
Valid blocks extend the chain under its chain-selection rules.
Before you concludeName the chain and its rules before making a comparison.
For LTC, the Nakamoto standard is an editorial framework: examine consensus, incentives, verification and custody instead of treating a brand or price chart as proof. It is our stated approach, not a certification granted by an outside organization.
Explore the desk ↗A borrower supplies collateral; a lender supplies the loan asset. These are different roles.
The borrower supplies the collateral accepted by that isolated market.
An oracle provides valuation; market parameters govern borrowing and liquidation.
Lenders supply the loan asset; borrowers draw it subject to liquidity and rules.
Before you concludeVerify chain, token addresses, oracle, rate model and liquidation threshold.
Morpho deserves its own recurring desk: lending design, collateral, oracles, rates, liquidity and evidence about each exact deployment. The reference’s Base cbLTC/USDC and cbBTC/USDC rate observations remain historical; they are not executable offers or today’s rates.
Explore the desk ↗A wrapped token adds an issuer, redemption arrangement and host-chain dependency.
BTC and LTC originate on their own networks.
The issuer or custodian describes how backing and redemption work.
The host-chain token carries those additional dependencies.
Before you concludeVerify the asset, issuer, host network and exact contract.
cbBTC and cbLTC are Coinbase-wrapped representations of Bitcoin and Litecoin. Coinbase states that it holds the underlying coins in custody with 1:1 backing. A token on another network is not a native Bitcoin or Litecoin output.
Explore the desk ↗
The reference names Litecoin Core, the Litecoin Foundation, LitVM, LiteForge and a community x402 example. Every named thread belongs in the notebook, but a project mention cannot establish production readiness.
Explore the desk ↗Native XLM and an issued asset on Stellar have different asset identities.
Identify the settlement network.
Distinguish native XLM from an issuer-created token.
An anchor or other provider adds its own terms and dependencies.
Before you concludeInspect the network, asset identifier, issuer and redemption arrangement.
Stellar coverage belongs in the wider-settlement section of the magazine. Accounts, issued assets, payments, smart contracts and access to traditional rails are distinct observations; a network activity count is not a direct measure of XLM investment demand.
Explore the desk ↗A native proof-of-work coin and a token on another chain are different systems.
Start with the exact asset, not the ticker alone.
Distinguish the native network from the token’s host network.
Use asset-specific sources for supply, trading and concentration.
Before you concludeResolve the canonical chain or contract before interpreting a quote.
The reference gives DOGE and PEPE space in its wider-market section. They remain visible here, with token identity and protocol context kept separate from enthusiasm, price and community culture.
Explore the desk ↗
LTC is a Satnam Satoshi media project, with AI-assisted research and production under human governance. A project name does not establish legal incorporation, a charitable trust or a staffed global newsroom.
Explore the desk ↗On Arc, native and ERC-20 USDC interfaces expose the same balance. Adding them double-counts it.
Arc exposes USDC for gas through its native interface, using 18 decimals.
Both interfaces refer to one underlying USDC balance.
The USDC token interface uses 6 decimals. EURC is a separate euro asset.
Before you concludeKeep EURC, bridged tokens, network identity and issuer terms separate.
This desk expands the reference’s Circle/Arc page to include EURC, Circle’s euro-denominated stablecoin. USDC is dollar-denominated. EURC is the issuer ticker intended here; there is no separate ERUC asset in this guide.
Explore the desk ↗A submission, a paid placement and an editorial story are different relationships.
Identify the contributor and their inspectable work.
Check claims, licenses and commercial interests.
Disclose the relationship and preserve editorial independence.
Before you concludeMake the contributor, conflicts and placement status visible.
The reference reserves a partner canvas. On this site it is a house invitation to contribute open tools, education and service. There is no booked paid advertisement or implied sponsor relationship.
Explore the desk ↗A useful register can have missing rows. A complete-looking table can still mislead.
State the universe and what qualifies for inclusion.
Keep comparable units, sources and cutoffs.
Show missing evidence rather than inventing a complete ranking.
Before you concludeKeep unavailable distinct from zero and reported distinct from computed.
Twenty-one is a recurring editorial motif rooted in Bitcoin’s supply limit. It gives the publication a recognizable rhythm; it does not justify manufacturing twenty-one products, companies or verified observations.
Explore the desk ↗This record preserves the guide text and evidence status at publication. Later guide edits do not rewrite this edition. The sourcebook identifies the measurements actually collected. The original design’s 26-source notebook remains available.
The sourcebook
Each source keeps its own clock. Open any entry to inspect the observation, collection time and evidence record.
This index covers the original daily briefings. Additional records are saved with this issue: network metadata, Morpho methods and hashes, official agency feeds and the feature citations. The edition download contains all of them.
Collected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: dated observation.
ibit-csv-v12026-11-12T19:34:30.476Za01caf94c5766b78824263d15109cee73945e02d68e6b8d6f59b0479336e4b47Collected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: dated event.
github-release-v12026-11-12T19:34:30.476Z01ca6b013be46bfcfc6e2a30f7c3a7604aab6ea58d440fcf2285dbc43840bcd2Collected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: dated event.
github-litecoin-release-v12026-11-12T19:34:30.476Z9b376ac4d99591bd10bfadd0f8577a761b30d04e41143268030ee51b1cd784daCollected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: dated event.
github-lnd-release-v12026-11-12T19:34:30.476Zeaa95997fd5dd6b81ab7ae0a9bac5cac4721df9dbb175b18840bba7b25c27b6dCollected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: unknown.
Collection unavailable (HTTP 403). No observation is reported.
source-check-v12026-11-12T19:34:30.476ZNo retrieved source hashhttp_failureCollected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: unknown.
Collection unavailable (HTTP 403). No observation is reported.
source-check-v12026-11-12T19:34:30.476ZNo retrieved source hashhttp_failureCollected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: unknown.
The page was retrieved as a reference. No numerical metrics were validated from it.
source-check-v12026-11-12T19:34:30.476Z96c7fe39609f4e4450316c971f8ba777c5ec50f03b31b37480a0235d201de70bCollected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: dated observation.
coinbase-btc-ticker-v12026-11-12T19:34:30.476Z8ad0161bbb2592d741b537c426a5e861d1f0ab902c14a71e7b4c7a55b20cb0a6Collected November 12, 2026 at 2:34 PM · America/New_York.
Freshness at edition preparation: dated observation.
coinbase-ltc-ticker-v12026-11-12T19:34:30.476Za2b13c7e155ac7e9fabaa9eb777db2ef156321360c178465af71bc0b3c78a0ae“Collected” means source observations were parsed. “Reference retrieved” records availability only. Hashes identify retrieved bytes; they do not certify a publisher’s claims. These are not independently audited metrics.
Download the edition record ↗Leave room for what is missing
A dated upstream release can remain the latest returned record for months. Its original date stays attached. A missing observation never becomes zero.
Keep the earlier pages
No update or correction note is recorded for this revision. Changes become a new saved version; earlier editions remain visible.
Permanent page for November 12, 2026
Link to this exact revision
The date page shows the latest accepted revision for this day. Exact revision links preserve the earlier record.
Edition date: 2026-11-12 in America/New_York. Preparation: 2026-11-12T19:37:02.289Z. Release record: 2026-11-12T19:37:02.289Z. The publishing process records this timestamp; it is not independently certified.
Publication follows a source-bound automated briefing policy. Material analysis, opinion and other editorial previews remain labeled for human review. Read the newsroom policy.
General education and research, not individualized investment advice. No affiliation with cited organizations is implied. Report a correction with evidence. Public submissions must not contain confidential information.
A question to carry with you
Which detail changes your understanding when you step back from the headline?
Choose one number in this edition. Write its unit, source date and what it does not measure. Compare those notes with a friend’s reading.
Keep the curiosity. Bring it back to the table.
Read slowly.Original editorial reflection, prepared by AI and saved with this edition. It is not an additional news claim.