{ "version": "2026-10-06.2", "items": [ { "title": "Transaction size, change and reorganizations", "topic": "payments", "evidence": "regtest", "date": "2026-09-26", "version": "Core 0.21.5.8 · release 2026-09-26", "scope": "12 signed size constructions, three amount checks and a two-node reorganization. No mainnet attack likelihood or propagation benchmark.", "url": "/transaction-lab/", "method": "/uploads/research/transaction-lab-20260926/README.txt", "image": "/uploads/articles/transaction-lab-20260926/transaction-lab.svg", "article": "/articles/what-actually-happens-when-you-send-litecoin", "id": "transaction-construction", "release_order": 1, "finding": "The same two-output payment measured 141 vB with one native SegWit input and 219 vB with one legacy input.", "data": "/uploads/research/transaction-lab-20260926/measurements.csv" }, { "title": "Recovery and address discovery", "topic": "wallets", "evidence": "regtest", "date": "2026-09-27", "version": "Core 0.21.5.8 / Electrum-LTC 4.2.2.1 · release 2026-09-27.2", "scope": "Synthetic wallet balances and discovery cases. A package consistency check does not rerun the wallet experiments.", "url": "/wallet-recovery/", "method": "/uploads/research/source-20260927/README.txt", "image": "/uploads/articles/wallet-discovery-20260927/missing-history.svg", "article": "/articles/why-a-restored-litecoin-wallet-can-show-zero-three-controlled-tests", "id": "wallet-discovery", "release_order": 2, "data": "/uploads/research/wallet-discovery-20260927/core-history-stages.csv" }, { "title": "Dust policy boundaries", "topic": "payments", "evidence": "regtest", "date": "2026-09-27", "version": "Core 0.21.5.8 · release 2026-09-27.1", "scope": "Transparent standard outputs tested against local policy. Policy is not consensus or guaranteed miner acceptance.", "url": "/articles/how-small-can-a-litecoin-payment-be-dust-limits-tested-in-core", "method": "/uploads/research/dust-20260927/README.txt", "image": "/uploads/articles/dust-20260927/one-litoshi.svg", "article": "/articles/how-small-can-a-litecoin-payment-be-dust-limits-tested-in-core", "id": "dust-policy", "release_order": 3, "data": "/uploads/research/dust-20260927/dust-core-results.csv" }, { "title": "One transaction or 50 payments?", "topic": "payments", "evidence": "regtest", "date": "2026-09-30", "version": "Core 0.21.5.8 · release 2026-09-30.1", "scope": "164 signed candidate checks with equal input budgets. No real customer payments.", "url": "/articles/paying-50-people-with-litecoin-one-transaction-or-50", "method": "/uploads/research/practical-20260930/batching/README.txt", "image": "/uploads/articles/practical-20260930/batching-20260930-hero.webp", "article": "/articles/paying-50-people-with-litecoin-one-transaction-or-50", "id": "batch-payments", "release_order": 4, "data": "/uploads/research/practical-20260930/batching/batch-results.csv" }, { "title": "Payment URI parsing and QR round-trips", "topic": "payments", "evidence": "parser", "date": "2026-09-30", "version": "Electrum-LTC 4.2.2.1 / bip21 3.0.0 · release 2026-09-30.1", "scope": "20 URI cases and digital QR decoding. No camera, signing or complete wallet GUI test.", "url": "/articles/what-a-litecoin-payment-qr-code-actually-tells-your-wallet", "method": "/uploads/research/practical-20260930/qr/README.txt", "image": "/uploads/articles/practical-20260930/qr-20260930-hero.webp", "article": "/articles/what-a-litecoin-payment-qr-code-actually-tells-your-wallet", "id": "payment-uri", "release_order": 5, "data": "/uploads/research/practical-20260930/qr/uri-results.csv" }, { "title": "Two wallet payment-request parsers", "topic": "wallets", "evidence": "parser", "date": "2026-09-30", "version": "Electrum-LTC 4.2.2.1 / Cake Wallet 6.4.5 · release 2026-09-30.1", "scope": "Identical fixtures in pinned source functions. Parsing without error does not imply a valid signed payment.", "url": "/wallet-qr/", "method": "/uploads/research/wallet-qr-20260930/README.txt", "image": "/uploads/research/wallet-qr-20260930/hero.svg", "article": "/articles/how-two-wallet-parsers-handle-litecoin-payment-requests", "id": "wallet-parsers", "release_order": 6, "data": "/uploads/research/wallet-qr-20260930/results.csv" }, { "title": "Costs between bank and wallet", "topic": "investing", "evidence": "observation", "date": "2026-09-30", "version": "Public order-book snapshots / replay scripts · release 2026-09-30.1", "scope": "Nine LTC/EUR snapshots and 18 purchase replays; provider fees are illustrative. No actual purchase.", "url": "/articles/buying-100-euros-of-litecoin-the-costs-between-your-bank-and-wallet", "method": "/uploads/research/practical-20260930/purchase/README.txt", "image": "/uploads/articles/practical-20260930/purchase-20260930-hero.webp", "article": "/articles/buying-100-euros-of-litecoin-the-costs-between-your-bank-and-wallet", "id": "purchase-costs", "release_order": 7, "data": "/uploads/research/practical-20260930/purchase/book-observations.csv" }, { "title": "First mainnet observation to confirmation", "topic": "network", "evidence": "observation", "date": "2026-09-27", "version": "Core 0.21.5.8 · protocol 2026-09-27-v2", "scope": "One-node sampled cohort with open outcomes, gaps and daily exports. First seen is a polling time.", "url": "/confirmation-times/", "method": "/uploads/research/confirmation-observer-20260927-v2/README.txt", "image": "", "article": "", "id": "confirmation-protocol", "release_order": 8 }, { "title": "Seven Scrypt hardware configurations", "topic": "mining", "evidence": "model", "date": "2026-10-01", "version": "Python Decimal calculations · release 2026-10-01.1", "scope": "Frozen prices and difficulty; manufacturer specifications, not wall-power measurements. Cooling and extra merged coins excluded from the published base model.", "url": "/articles/is-litecoin-mining-profitable-now-asic-electricity-costs", "method": "/uploads/research/mining-economics-20261001/README.txt", "image": "/uploads/research/mining-economics-20261001/hero-mining-costs-v1.webp", "article": "/articles/is-litecoin-mining-profitable-now-asic-electricity-costs", "id": "scrypt-economics", "release_order": 9, "data": "/uploads/research/mining-economics-20261001/hardware-results.csv" }, { "title": "Old and new receiving addresses", "topic": "wallets", "evidence": "regtest", "date": "2026-10-01", "version": "Core 0.21.5.8 · beginner-debates 2026-10-01", "scope": "Controlled address-reuse case after 41 later addresses. No restored-wallet discovery or exchange deposit test.", "url": "/articles/why-your-litecoin-receive-address-changes", "method": "/uploads/research/beginner-debates-20261001/README.txt", "image": "/uploads/research/beginner-debates-20261001/hero-addresses.webp", "article": "/articles/why-your-litecoin-receive-address-changes", "id": "receiving-addresses", "release_order": 10, "finding": "The old address still received coins after 41 later addresses were generated. Its confirmed total reached 0.4 test LTC.", "data": "/uploads/research/beginner-debates-20261001/core-results.json" }, { "title": "Replacement before and after confirmation", "topic": "payments", "evidence": "regtest", "date": "2026-10-01", "version": "Core 0.21.5.8 · beginner-debates 2026-10-01", "scope": "Default versus explicit replacement policy and a confirmed-input conflict. No mainnet cancellation probability.", "url": "/articles/can-you-cancel-a-litecoin-payment-what-changes-after-broadcast", "method": "/uploads/research/beginner-debates-20261001/README.txt", "image": "/uploads/research/beginner-debates-20261001/hero-cancel.webp", "article": "/articles/can-you-cancel-a-litecoin-payment-what-changes-after-broadcast", "id": "payment-replacement", "release_order": 11, "finding": "The default node rejected the conflicting replacement. With replacement enabled, the higher-fee candidate was accepted.", "data": "/uploads/research/beginner-debates-20261001/core-results.json" }, { "title": "Fund fees and premium/discount arithmetic", "topic": "investing", "evidence": "model", "date": "2026-10-01", "version": "Python Decimal · beginner-debates 2026-10-01", "scope": "Reproducible fee scenarios and rounded-price uncertainty. No investment forecast, transaction or holdings audit.", "url": "/articles/does-buying-a-litecoin-etf-mean-you-own-litecoin", "method": "/uploads/research/beginner-debates-20261001/README.txt", "image": "/uploads/research/beginner-debates-20261001/hero-etf.webp", "article": "/articles/does-buying-a-litecoin-etf-mean-you-own-litecoin", "id": "fund-fees", "release_order": 12, "data": "/uploads/research/beginner-debates-20261001/etf-fees.csv" }, { "id": "confirmation-pilot", "release_order": 13, "title": "What our node has observed about Litecoin confirmation times so far", "topic": "network", "evidence": "observation", "date": "2026-10-01", "version": "Core 0.21.5.8 · frozen pilot 2026-10-01T22:20:00Z · analysis 1.0", "scope": "17 h 14 min of covered polling at one node. Timings exclude open and censored outcomes; they are not a population success rate.", "finding": "7,595 matched confirmations had a 135-second median. The full 8,148-row cohort also retains open waits and collection gaps.", "url": "/articles/what-our-node-has-observed-about-litecoin-confirmation-times-so-far", "article": "/articles/what-our-node-has-observed-about-litecoin-confirmation-times-so-far", "method": "/uploads/research/confirmation-pilot-20261002-v1/README.txt", "data": "/uploads/research/confirmation-pilot-20261002-v1/cohort.csv", "image": "/uploads/articles/confirmation-pilot-20261002/hero.svg" }, { "id": "early-headers", "release_order": 14, "title": "What Litecoin’s first 1,001 block headers actually show", "topic": "network", "evidence": "observation", "date": "2026-10-02", "version": "Core 0.21.5.8 · capture and analysis 2026-10-02-v1", "scope": "1,001 retained mainnet headers; signed header-time differences, not a wall-clock or miner-attribution study.", "finding": "Heights 3–1,000 span 47 min 26 s in recorded header times; eight adjacent differences are negative.", "url": "/articles/litecoin-s-first-week-on-chain-archaeology-of-blocks-0-to-1-000", "article": "/articles/litecoin-s-first-week-on-chain-archaeology-of-blocks-0-to-1-000", "method": "/uploads/research/chain-audit-20261002-v1/README.txt", "data": "/uploads/research/chain-audit-20261002-v1/early-headers.csv", "image": "/uploads/articles/chain-audit-20261002/early-header-time.svg" }, { "id": "early-output-census", "release_order": 15, "title": "We checked 998 early Litecoin outputs. Unspent does not mean lost", "topic": "network", "evidence": "observation", "date": "2026-10-02", "version": "Core 0.21.5.8 · capture and analysis 2026-10-02-v1", "scope": "998 selected coinbase output-zero checks at height 3188251. Unspent status does not identify lost keys or owners.", "finding": "42 selected outpoints remained unspent with 2,100 LTC; this is not an estimate of all lost Litecoin.", "url": "/articles/how-much-litecoin-is-lost-forever-on-chain-forensics-of-dormant-ltc-supply", "article": "/articles/how-much-litecoin-is-lost-forever-on-chain-forensics-of-dormant-ltc-supply", "method": "/uploads/research/chain-audit-20261002-v1/README.txt", "data": "/uploads/research/chain-audit-20261002-v1/early-output-status.csv", "image": "/uploads/articles/chain-audit-20261002/early-unspent.svg" }, { "id": "large-output-classification", "release_order": 16, "title": "Why a large Litecoin transaction is not always a whale transfer", "topic": "network", "evidence": "observation", "date": "2026-10-02", "version": "Core 0.21.5.8 · capture and analysis 2026-10-02-v1", "scope": "14,278 decoded rows in blocks 3188200–3188249. Output totals include change and do not identify economic transfers.", "finding": "All ten largest naive non-coinbase output totals were HogEx rows. The largest ordinary total was 22,351.31551018 LTC.", "url": "/articles/the-10-most-expensive-litecoin-transactions-in-history-on-chain-forensics", "article": "/articles/the-10-most-expensive-litecoin-transactions-in-history-on-chain-forensics", "method": "/uploads/research/chain-audit-20261002-v1/README.txt", "data": "/uploads/research/chain-audit-20261002-v1/ordinary-output-ranking.csv", "image": "/uploads/articles/chain-audit-20261002/hogex-ranking.svg" }, { "id": "mweb-window", "release_order": 17, "title": "What 50 Litecoin blocks tell us about MWEB activity", "topic": "network", "evidence": "observation", "date": "2026-10-02", "version": "Core 0.21.5.8 · capture and analysis 2026-10-02-v1", "scope": "50 consecutive blocks, selecting HogAddr separately from peg-outs. No private amounts or distinct-user count.", "finding": "The HogAddr endpoint value fell 7.85100985 LTC; 13 blocks contained 16 kernel records.", "url": "/articles/mweb-three-years-on-what-the-adoption-data-actually-says-about-litecoin-privacy", "article": "/articles/mweb-three-years-on-what-the-adoption-data-actually-says-about-litecoin-privacy", "method": "/uploads/research/chain-audit-20261002-v1/README.txt", "data": "/uploads/research/chain-audit-20261002-v1/mweb-window.csv", "image": "/uploads/articles/chain-audit-20261002/mweb-reserve.svg" }, { "id": "additional-scrypt-capacity", "release_order": 18, "title": "What a 51% Litecoin attack estimate must assume", "topic": "mining", "evidence": "model", "date": "2026-10-02", "version": "Python Decimal · declared scenarios 2026-10-02.1", "scope": "42 additional-capacity scenarios with frozen manufacturer inputs. No inventory, rental-market census or attack-success probability.", "finding": "Adding 0.51 times unchanged honest hashpower gives 33.77% of the enlarged total, not a majority.", "url": "/articles/what-would-a-51-attack-on-litecoin-actually-cost-the-math", "article": "/articles/what-would-a-51-attack-on-litecoin-actually-cost-the-math", "method": "/uploads/research/editorial-models-20261002-v1/README.txt", "data": "/uploads/research/editorial-models-20261002-v1/attack.csv", "image": "/uploads/research/editorial-models-20261002-v1/additional-capacity.svg" }, { "id": "payment-denominator", "release_order": 19, "title": "Do people pay with Litecoin? Read the denominator before the headline", "topic": "payments", "evidence": "model", "date": "2026-10-02", "version": "Python Decimal · declared scenarios 2026-10-02.1", "scope": "Arithmetic from a provider’s published 2025 totals and rounded share; not an exact merchant ledger or global adoption survey.", "finding": "Applying the same 14.4% share to bases with and without excluded off-chain orders changes the estimate by about 14,416 orders.", "url": "/articles/does-anyone-actually-pay-with-litecoin-in-2026-the-real-adoption-data", "article": "/articles/does-anyone-actually-pay-with-litecoin-in-2026-the-real-adoption-data", "method": "/uploads/research/editorial-models-20261002-v1/README.txt", "data": "/uploads/research/editorial-models-20261002-v1/results.json", "image": "/uploads/research/editorial-models-20261002-v1/payment-denominator.svg" }, { "id": "treasury-share-scenarios", "release_order": 20, "title": "A Litecoin treasury stock is not Litecoin: holdings, dilution and NAV", "topic": "investing", "evidence": "model", "date": "2026-10-02", "version": "Python Decimal · declared scenarios 2026-10-02.1", "scope": "18 synthetic per-share scenarios. Not Lite Strategy NAV, audited holdings, a market quote or an investment forecast.", "finding": "An illustrative discount change reduces a 42.86% LTC rise to a 4.22% synthetic share-price rise.", "url": "/articles/the-litecoin-treasury-trade-who-is-hoarding-ltc-on-a-balance-sheet-and-why-it-s-riskier-than-it-looks", "article": "/articles/the-litecoin-treasury-trade-who-is-hoarding-ltc-on-a-balance-sheet-and-why-it-s-riskier-than-it-looks", "method": "/uploads/research/editorial-models-20261002-v1/README.txt", "data": "/uploads/research/editorial-models-20261002-v1/synthetic_treasury.csv", "image": "" }, { "id": "card-sale-scenarios", "release_order": 21, "title": "Spending Litecoin with a crypto card: check the route and the real cost", "topic": "investing", "evidence": "model", "date": "2026-10-02", "version": "Python Decimal · declared scenarios 2026-10-02.1", "scope": "Six hypothetical €100 conversion cases. No real card purchase, provider quote or personalised eligibility check.", "finding": "A 1% sale spread plus a €1 fixed fee consumes 2% of an illustrative €100 budget.", "url": "/articles/the-best-crypto-cards-for-spending-litecoin-in-2026", "article": "/articles/the-best-crypto-cards-for-spending-litecoin-in-2026", "method": "/uploads/research/editorial-models-20261002-v1/README.txt", "data": "/uploads/research/editorial-models-20261002-v1/card_sale_scenarios.csv", "image": "" }, { "id": "backup-materials", "release_order": 2, "title": "Can you recover your Litecoin wallet? Tested backups, seeds and account keys", "topic": "wallets", "evidence": "regtest", "date": "2026-09-27", "version": "Core 0.21.5.8 / Electrum-LTC 4.2.2.1 · 2026-09-27", "scope": "Controlled synthetic backup and account-key cases. Not a recovery guarantee or a test of every hardware wallet.", "url": "/wallet-recovery/", "article": "/articles/can-you-recover-your-litecoin-wallet-tested-backups-seeds-and-account-keys", "method": "/uploads/research/source-20260927/README.txt", "data": "/uploads/research/wallet-recovery-20260927/cross-implementation.csv", "image": "/uploads/articles/wallet-recovery-20260927/recovery-workbook.svg" }, { "id": "fee-budget", "release_order": 22, "title": "How could Litecoin mining work after the block subsidy ends?", "topic": "mining", "evidence": "model", "date": "2026-10-02", "version": "Python Decimal · declared scenarios 2026-10-02-v1", "scope": "Nine declared fee-revenue targets and charged-vbyte scenarios. Not measured occupancy, maximum block size, future demand or an attack budget.", "finding": "A 1 LTC revenue target across 500,000 charged vbytes requires a 200 litoshis/vB weighted average.", "url": "/articles/what-happens-when-all-84-million-litecoin-are-mined", "article": "/articles/what-happens-when-all-84-million-litecoin-are-mined", "method": "/uploads/research/workflow-models-20261002-v1/README.txt", "data": "/uploads/research/workflow-models-20261002-v1/fee-budget.csv", "image": "" }, { "id": "inventory-ledger", "release_order": 23, "title": "Keeping Litecoin records: a worked ledger for transfers, fees and payments", "topic": "investing", "evidence": "model", "date": "2026-10-02", "version": "Python Decimal · declared scenarios 2026-10-02-v1", "scope": "Seven synthetic inventory rows, with a blank bookkeeping CSV. Not customer records, historical quotes or a completed tax return.", "finding": "An own-wallet transfer preserves the transferred inventory but consumes its separate fee; final example inventory is 6.997 LTC.", "url": "/articles/litecoin-tax-guide-how-ltc-is-taxed-in-the-us-uk-eu-and-australia", "article": "/articles/litecoin-tax-guide-how-ltc-is-taxed-in-the-us-uk-eu-and-australia", "method": "/uploads/research/workflow-models-20261002-v1/README.txt", "data": "/uploads/research/workflow-models-20261002-v1/inventory-ledger.csv", "image": "" }, { "id": "wallet-spendability", "title": "Why your Litecoin wallet shows a balance but cannot send", "topic": "wallets", "evidence": "regtest", "date": "2026-10-03", "version": "Core 0.21.5.8 · beginner-wallets 2026-10-03-v1", "url": "/articles/why-your-litecoin-wallet-shows-a-balance-but-cannot-send", "article": "/articles/why-your-litecoin-wallet-shows-a-balance-but-cannot-send", "method": "/uploads/research/beginner-wallets-20261003-v1/README.txt", "image": "/uploads/articles/beginner-wallets-20261003/balance-hero.webp", "data": "/uploads/research/beginner-wallets-20261003-v1/balance-states.csv", "release_order": 25, "scope": "11 controlled wallet states on one isolated node. No mobile, hardware, exchange or MWEB test.", "finding": "A watch-only wallet and a selection-locked wallet both reported 1 LTC, but had different missing conditions for a payment." }, { "id": "exact-and-max-payments", "title": "How to send an exact Litecoin amount or your whole wallet balance", "topic": "payments", "evidence": "regtest", "date": "2026-10-03", "version": "Core 0.21.5.8 · beginner-wallets 2026-10-03-v1", "url": "/articles/how-to-send-an-exact-litecoin-amount-or-your-whole-wallet-balance", "article": "/articles/how-to-send-an-exact-litecoin-amount-or-your-whole-wallet-balance", "method": "/uploads/research/beginner-wallets-20261003-v1/README.txt", "image": "/uploads/articles/beginner-wallets-20261003/send-hero.webp", "data": "/uploads/research/beginner-wallets-20261003-v1/payment-cases.csv", "release_order": 26, "scope": "24 controlled constructions with explicit equal 1 LTC budgets. 18 signed candidates policy-tested, six rejected and one sweep mined; no mainnet fee recommendation.", "finding": "A one-input send-max candidate delivered 0.99999780 LTC from 1 LTC; the exact-full-balance construction failed before broadcasting." }, { "id": "address-route-validation", "title": "Sending Litecoin to the wrong network: address checks and recovery limits", "topic": "wallets", "evidence": "regtest", "date": "2026-10-03", "version": "Core 0.21.5.8 · address-validation 2026-10-03-v1", "url": "/articles/sending-litecoin-to-the-wrong-network-address-checks-and-recovery-limits", "article": "/articles/sending-litecoin-to-the-wrong-network-address-checks-and-recovery-limits", "method": "/uploads/research/beginner-address-orders-20261003-v1/README.txt", "image": "/uploads/articles/editorial-refresh-20261006/network-route.webp", "data": "/uploads/research/beginner-address-orders-20261003-v1/address-checks.csv", "release_order": 27, "scope": "18 synthetic fixtures, 36 address checks in disconnected mainnet-mode and regtest Core, height zero and wallets disabled. No transfer, ownership, service-credit or recovery test.", "finding": "A historical version-5 P2SH address and its modern LTC encoding produced the same script; syntax did not establish the intended chain or recipient." }, { "id": "limit-order-mechanics", "title": "Why a Litecoin limit order can fill instantly, partly or not at all", "topic": "investing", "evidence": "model", "date": "2026-10-03", "version": "Python Decimal · synthetic orders 2026-10-03-v1", "url": "/articles/why-a-litecoin-limit-order-can-fill-instantly-partly-or-not-at-all", "article": "/articles/why-a-litecoin-limit-order-can-fill-instantly-partly-or-not-at-all", "method": "/uploads/research/beginner-address-orders-20261003-v1/README.txt", "image": "/uploads/articles/editorial-refresh-20261006/limit-order-queue.webp", "data": "/uploads/research/beginner-address-orders-20261003-v1/order-cases.csv", "release_order": 28, "scope": "12 synthetic matching scenarios and two FIFO queue events. Declared prices, fees and future events; no actual exchange order, live book or engine audit.", "finding": "A marketable 2 LTC limit at 60.10 bought 1.5 immediately. GTC retained 0.5, IOC cancelled it and FOK bought nothing in the declared book." }, { "id": "fee-reward-snapshot", "title": "One 0.2 LTC fee changed the picture in our 144-block sample", "topic": "mining", "evidence": "observation", "date": "2026-10-04", "version": "Core 0.21.5.8 · frozen network snapshot 2026-10-04-v1", "url": "/articles/one-0-2-ltc-fee-changed-the-picture-in-our-144-block-sample", "article": "/articles/one-0-2-ltc-fee-changed-the-picture-in-our-144-block-sample", "method": "/uploads/research/network-analyses-20261004-v1/README.txt", "data": "/uploads/research/network-analyses-20261004-v1/fee-blocks.csv", "image": "/uploads/articles/editorial-refresh-20261006/fee-outlier-v2.webp", "release_order": 29, "scope": "144 fixed mainnet blocks, subsidy/fees/coinbase reconciliation and MWEB decomposition. Header-time window; no payer identity, live quote, DOGE income or mining-profit audit.", "finding": "One 0.2 LTC entry supplied 9.74% of fees; removing it lowered the base-chain sample mean from 4643.08 to 4190.70 litoshis." }, { "id": "hashrate-window-snapshot", "title": "Why Litecoin hashrate estimates disagree at the same block", "topic": "network", "evidence": "observation", "date": "2026-10-04", "version": "Core 0.21.5.8 · frozen network snapshot 2026-10-04-v1", "url": "/articles/why-litecoin-hashrate-estimates-disagree-at-the-same-block", "article": "/articles/why-litecoin-hashrate-estimates-disagree-at-the-same-block", "method": "/uploads/research/network-analyses-20261004-v1/README.txt", "data": "/uploads/research/network-analyses-20261004-v1/hashrate-windows.csv", "image": "/uploads/articles/editorial-refresh-20261006/hashrate-windows.webp", "release_order": 30, "scope": "601 frozen headers and 30/120/576-block estimates at height 3,189,039. Reconstructed expected work/header time, not hardware telemetry or a causal test of miner departures.", "finding": "At one ending block, 30/120/576-block windows returned 3.434/2.956/2.945 PH/s, a 16.57% largest-to-smallest difference." }, { "id": "ltc-eur-cost-history", "title": "A 7 bp Litecoin spread hid a 231 bp cost in our €10,000 replay", "topic": "investing", "evidence": "observation", "date": "2026-10-05", "version": "Public LTC/EUR books · frozen replay 2026-10-05-v1", "url": "/articles/ltc-eur-trading-costs-what-our-first-order-book-observations-show", "article": "/articles/ltc-eur-trading-costs-what-our-first-order-book-observations-show", "method": "/uploads/research/liquidity-history-20261005-v1/README.txt", "data": "/uploads/research/liquidity-history-20261005-v1/replays.csv", "image": "/uploads/articles/editorial-refresh-20261006/liquidity-order-book.webp", "release_order": 31, "scope": "392 capture rounds / 1,176 raw public books from 30 September–4 October UTC; 7,056 amount/direction replays reconstructed. Visible-level arithmetic, not submitted trades, total account costs, simultaneous venue quotes or a future ranking.", "finding": "One Coinbase snapshot had a 6.99 bp spread but its €10,000 buy replay cost 231.48 bp above its midpoint; every recorded case had enough retained visible depth." }, { "id": "timelock-controls", "title": "Can you schedule a Litecoin payment? We tested what a timelock actually locks", "topic": "payments", "evidence": "regtest", "date": "2026-10-06", "version": "Core 0.21.5.8 · isolated controls 2026-10-06-v1", "url": "/articles/can-you-schedule-a-litecoin-payment-what-timelocks-actually-lock", "article": "/articles/can-you-schedule-a-litecoin-payment-what-timelocks-actually-lock", "method": "/uploads/research/keys-and-time-20261006-v1/README.txt", "data": "/uploads/research/keys-and-time-20261006-v1/timelock-cases.csv", "image": "/uploads/articles/new-articles-20261006/timelock-hero.webp", "release_order": 32, "scope": "13 controlled transparent regtest cases: absolute transaction locktime, key-signed P2SH CLTV, next-block admission and artificial median-time boundary. Four negative block-validation attempts and two observed positive inclusion cases; no mainnet timing, MWEB or production custody test.", "finding": "An alternative ordinary spend confirmed at height 1,358, before a future candidate's locktime 1,367; the required CLTV spend passed at 1,363." }, { "id": "wallet-password-copy-controls", "title": "We changed a Litecoin wallet password. The old backup could still spend.", "topic": "wallets", "evidence": "regtest", "date": "2026-10-06", "version": "Core 0.21.5.8 · isolated controls 2026-10-06-v1", "url": "/articles/we-changed-a-litecoin-wallet-password-the-old-backup-could-still-spend", "article": "/articles/we-changed-a-litecoin-wallet-password-the-old-backup-could-still-spend", "method": "/uploads/research/keys-and-time-20261006-v1/README.txt", "data": "/uploads/research/keys-and-time-20261006-v1/password-cases.csv", "image": "/uploads/articles/new-articles-20261006/wallet-password-hero.webp", "release_order": 33, "scope": "12 controlled Core cases with a known-password encrypted legacy wallet copy, one copied-keypool address and independent-wallet transfer. Signing, mempool admission and confirmed migration are separate; no cracking, real compromise or hardware device tested.", "finding": "The earlier encrypted copy kept its old password and confirmed a spend; changing the current file password did not replace the copied key." } ] }