One Litecoin transaction, two invoices: match the outputs
Litecoin.watch. Prepared 6 November 2026 (Europe/Warsaw).

Replay offline
  python replay.py.txt

Python 3 standard library only. Keep fixtures.json alongside the script. The
script generates four deterministic unsigned transparent transactions, parses
those bytes, recomputes their TXIDs and replays six exact-output allocation
cases. It checks the regenerated data against fixtures.json. Each previous
outpoint is fabricated; scripts use repeated-byte hash templates. Do not use
these examples as receiving addresses or attempt to send their transactions.

The fixture network label is a bookkeeping namespace for the experiment. A
network label is supplied by the ledger context, not read from the raw bytes.
All amounts are integer litoshis in the model, with 100,000,000 litoshis per LTC.
The model considers only the output deliveries and open invoices listed in a
case. It leaves multiple candidates in either direction for review. Its
complete pairing count covers all open invoices and exact-match outputs and
is used only for these small fixture sets. It is not a production matcher or
an invoice credit system.

Core cross-check
  core-check.json records a separate local run on Litecoin Core 0.21.5.8.
  It includes the network and peer checks, decoder responses, and the
  distinct-address and duplicate-address constructor controls. Wallet support
  was disabled; the isolated regtest node stayed at genesis, with no peers.
  The duplicate-address constructor returned -8. This is an RPC construction
  restriction. A decoded unsigned transaction is not proof of admission or
  spendability.

  To repeat a decode on your own disposable regtest node, pass a fixture's
  raw_hex as the first decoderawtransaction argument and false as the second
  (non-witness) argument. Compare txid, size, version and locktime, the single
  vin reference, and each vout's n, value and scriptPubKey.hex. To repeat the
  constructor controls, use the parameters recorded in core-check.json on
  the same network. None of these RPCs submits a transaction.

sources.json gives immutable Core source links, line anchors and hashes of
source file contents. SHA256SUMS.txt covers the five evidence payloads. These
checks document the supplied bytes, arithmetic and RPC observations. They do
not attest binary provenance, prove that real money moved or validate a
merchant policy, wallet UX, relay, confirmations or MWEB behavior.