Receiving Litecoin while the recipient wallet is offline
Release: offline-wallet-20261012-v1 / 1.0.0
Measurement date: 12 October 2026
Software: Litecoin Core 0.21.5.8, Linux executables; Python 3 standard library.

WHAT WAS OBSERVED
Two fresh Core nodes synchronized on a new regtest chain at height 101. The
recipient wallet had pre-generated three native SegWit addresses and zero LTC.
Its daemon was stopped and its process exited with code zero.
The sender paid 0.125, 0.02 and 0.03 regtest LTC while that process remained
stopped. One block was generated after each payment, producing sender height
104 and final confirmation depths 3, 2 and 1.
The recipient restarted from its same test data directory without peers:
height 101, balance zero, all three TXIDs unknown to its wallet.
After a single manually requested loopback connection, the recipient reached
104 and discovered 0.175 LTC. Its balances, three unspent receipts and each
payment amount agreed. Best-block hashes agreed, and confirmation depths
matched the sender. Both final processes exited cleanly.

ISOLATION AND LIMITS
The test creates two unique temporary data directories and four distinct
ephemeral RPC/P2P ports. RPC and P2P are bound to 127.0.0.1. Automatic outgoing
connections, DNS seeding, DNS lookups, address discovery, UPnP and onion
listening are disabled. Only the script's loopback peer is manually requested.
Both nodes use dbcache=32 and par=1. Their maxconnections cap permits the
one actual inbound connection after Core reserves its outgoing slots; it is
not a request to connect to twelve peers. Actual peer metadata is published.
No existing wallet, configuration, node, account, private key or seed is used.
Fresh regtest keys stay inside disposable node data directories and are never
exported. Temporary wallets are removed only after their processes exit.

No mainnet timing, consensus-attack resistance, mobile application, hardware
device, backend outage, business invoice, exchange credit or MWEB receipt was
tested. Regtest blocks were generated on demand; elapsed times are not a
confirmation benchmark. The recipient wallet did not spend its received coins.
The test does not prove backup recovery or watch-only signing capability.
The wallet is a new ordinary wallet with three known addresses. Large restored
wallet discovery and account derivation limits require separate investigation.

REPRODUCE
Obtain the pinned Core release from the official project and verify the
download separately. Pass binary paths, never an existing wallet/data directory:
  python offline-wallet-test.py.txt /path/litecoind /path/litecoin-cli new-output

The script creates its own disposable nodes and valueless funding. It writes
results.json, rpc-trace.json, payments.csv and states.csv to the chosen output
directory. It does not fetch software or contact mainnet peers. The tested
platform was Linux; no Windows/mobile interoperability claim is made.
Output identifiers, keys, blocks, timestamps and port numbers vary on a rerun.
The height transitions, three exact recipient amounts, stale balance and
post-sync total should reproduce with the same version and options.

VERIFY PUBLISHED EXPORTS WITHOUT RUNNING CORE
  python verify-results.py.txt .
This separately parses signed ordinary SegWit transaction bytes to check
recipient litoshis and reconstruct TXIDs, recomputes confirmation depth, sums
amounts with Decimal, checks stopped-process timestamps and peer metadata.
The recorded run passed 63 experiment assertions; the export verifier passed
38 checks. The verifier does not validate signatures or independently attest
to process execution or network history. The transcript is an execution
record supplied by Litecoin.watch, not a third-party proof.

FILE LIST
- offline-wallet-test.py.txt: complete two-node experiment runner.
- verify-results.py.txt: independent export and transaction-byte checks.
- results.json: states, payment outputs, peers, process lifecycle and assertions.
- rpc-trace.json: test RPC calls and results; no private-key export/cookies.
- payments.csv: exact three recipient outputs and confirmation comparisons.
- states.csv: four observed state snapshots; stopped-node values are blank.
- offline-receiving-checklist.txt/.csv: blank operational record, no secrets.
- SHA256SUMS.txt: release file hashes (integrity, not independent attestation).

All published addresses start with the regtest native-SegWit prefix and all
TXIDs are test-chain identifiers. Do not send real LTC to these addresses or
expect a mainnet explorer to find them.

Research, code and drafting used AI assistance. No independent external
review, funded account test or personal attendance is claimed.