Litecoin.watch editorial calculations and examples Version: editorial-six-20261021-v1 Checked: 21 October 2026 Purpose and scope These files support the capacity, full-node, mempool and energy guides updated on the stated date. The examples and network energy scenarios are synthetic. They are not measured network saturation, mainnet RPC responses, observed electricity consumption, a fleet census or forecasts. Reproduction Python 3 standard library only. Run reproduce-calculations.py.txt with --output pointing to an example-results directory. It creates five CSV files and two JSON files. No network request, node RPC, signing or broadcasting is performed. Decimal arithmetic is used for energy and fee calculations. Integer floor division is used for capacity counts. Nominal TPS is displayed to two decimal places; the chosen overhead and omitted constraints are recorded. Capacity Core v0.21.5.8 consensus/consensus.h specifies 4,000,000 block weight units. The model uses 1,000,000 virtual bytes, chooses 1,000 vB of block/coinbase allowance, and divides the remaining 999,000 by assumed transaction sizes. The 150-second target comes from chainparams.cpp. These are hypothetical repeatedly filled blocks; additional constraints and variable block timing matter. The separate batching measurements cited in the article remain in the original controlled batching study, not this capacity CSV. Energy One PH/s is one million GH/s. W = GH/s * J/GH. The constant facility multiplier is assumed to be 1.10 and the annualization period is 8,760 hours. Work rates and fleet shares are hypothetical. The 210 J/GH input comes from BITMAIN's typical L9 16 GH/s, 3,360 W specification at 25 C. It does not identify the actual Scrypt fleet. Other efficiency inputs and idle consumption are invented sensitivity inputs. Weighted efficiency is by shares of hashrate, not number of machines. Realized network work must not be reduced by the same uptime assumption twice. Device duty-cycle examples separately model running and idle electricity. Site loads are excluded from those device rows. Allocation of shared LTC/DOGE electricity is a stated accounting convention, not a second physical energy total. No emissions factor is assumed. Mempool The JSON is an annotated synthetic selection of transparent getmempoolentry fields based on Core v0.21.5.8 src/rpc/blockchain.cpp. Fee inputs are hypothetical. One LTC is 100,000,000 litoshis. LTC/kB * 100,000 gives litoshis/vB for the transparent conversion with 1,000 vB per kB. Ancestor and descendant counts include the transaction itself. The parent/child arithmetic does not assert admission or inclusion under any node's policy. MWEB-specific fee and weight handling needs separate interpretation. Node The configuration and returned fields illustrate a separate wallet-disabled Linux instance and a pruned data directory. The height, progress and prune height are synthetic. The example does not benchmark synchronization, disk usage or peer availability. Existing pruning and package-verification studies linked from the article retain their original scopes and dates. Primary technical references https://github.com/litecoin-project/litecoin/releases/tag/v0.21.5.8 https://github.com/litecoin-project/litecoin/blob/v0.21.5.8/src/consensus/consensus.h https://github.com/litecoin-project/litecoin/blob/v0.21.5.8/src/chainparams.cpp https://github.com/litecoin-project/litecoin/blob/v0.21.5.8/src/init.cpp https://github.com/litecoin-project/litecoin/blob/v0.21.5.8/src/rpc/blockchain.cpp https://support.bitmain.com/hc/en-us/articles/33850555425305-L9-Specifications Review responsibility Prepared with Codex assistance as an editorial source and calculation check. This is not a separate independent security, privacy, energy or hardware audit.