Before choosing a Litecoin wallet/node storage arrangement

[ ] Record who controls spending keys; keep recovery material private.
[ ] Record where transaction/chain information comes from.
[ ] Decide whether independent own-node validation is the goal.
[ ] Decide whether locally retained old blocks are needed for a specific task.
[ ] Record exact software version, network, data paths and enabled indexes.
[ ] Record synchronized height and actual current status; do not infer it from
    application startup or a pruned=true flag alone.
[ ] Separate configured block/undo target from actual complete storage use.
[ ] Measure chainstate, metadata and MWEB supporting data where applicable.
[ ] Check index compatibility and storage separately.
[ ] Account for wallets, independent backups, logs and operating free space.
[ ] Keep unmeasured quantities unknown rather than adding them as zero.
[ ] Check connection constraints and initial-sync needs; pruning is not a
    promise to skip initial chain processing or minimize download traffic.
[ ] Follow the wallet's documented backup procedure; use an appropriate
    separate test environment to check restoration, never erase a working copy.
[ ] Consider whether restoring older history will need blocks no longer local.
[ ] Review the existing full-node setup guide before changing settings.

No keys, passwords, addresses, balances or user identifiers are requested.
This checklist is not a wallet backup, storage estimate or measured benchmark.