Security & software articles
Scams, key controls, proof checks, software fixes and operational risks.
Topics group the whole archive; an article can cover more than one. For a suggested reading order, explore the learning paths.
49 matching articles · Security & software. Clear topic

Verify a Litecoin inclusion proof: Merkle roots, headers and limits
Reconstruct a synthetic Merkle branch, distinguish Core proof verification from standalone hashing, and check chain membership and recipient evidence separately.
Data / code included
Secure local Litecoin Core RPC access: cookies, ports and permissions
A practical guide to local RPC boundaries, authentication cookies, actual listening endpoints and narrowly scoped application access, with read-only inspection examples.

Review a Litecoin PSBT before signing: inputs, change and fees
Inspect a transparent PSBT v0 without treating decoding as approval. Reproduce a synthetic fee example and review recipient, change, inputs and signature commitments.
Data / code included
A Litecoin wallet can sign a payment without sending it
Our signed Litecoin payment stayed outside the mempool until explicit submission. Output changes broke its signature; a second complete signed file became unusable after its input was spent.
Data / code included
A valid Litecoin message signature does not prove a balance
A zero-funded address signed successfully, and the same expired response still verified. See what the legacy Core test establishes and which context, expiry and replay rules an application must enforce.
Data / code included
Need help with a Litecoin payment? Build a clear support request
The right question depends on whether a payment was broadcast, confirmed or credited. Eight fictional cases and six templates help organize a focused support request.
Data / code included
The old Litecoin backup still spent after a password change
An earlier encrypted copy unlocked with its known old password and spent the test output. Twelve Core cases separate local file encryption from on-chain control.
Data / code included
A valid Litecoin address can still be the wrong destination
An accepted address is not proof of the intended recipient or exchange credit. Our synthetic parser test explains shared historical formats, checksum limits and why recovery depends on the actual route.
Data / code included
Can a hardware wallet protect your Litecoin from every scam?
Seven scenarios show where hardware signing helps and where it does not: a copied recovery backup, a substituted address or a payment you approve to a scammer. Learn what to check on the device, how to verify the full destination and how native Litecoin payments differ from token approvals on other networks.

What a Litecoin payment QR code actually tells your wallet
Twenty URI cases across two parsers, SVG scan examples and a practical checklist for Litecoin amounts, labels, address checks and invoice expiry.
Data / code includedCan you recover your Litecoin wallet? Tested backups, seeds and account keys
We restored an encrypted Core wallet, Electrum seeds and BIP39-derived account keys. The tests separate matching addresses, finding funds and recovering signing authority.
Data / code includedProof of reserves: how to read a crypto exchange report
Check asset scope and liabilities, review dated Kraken and OKX disclosures, and reproduce a Merkle example showing the limits of inclusion proofs.
Data / code includedLitecoin multisig: how a 2-of-3 wallet works
Eight regtest cases show which key combinations can spend. Includes a recovery checklist, backup requirements and a reproducible Core experiment.
Data / code included
How to verify a Litecoin Core download before installing it
Check the signing key, manifest and installer hash. Includes four verified Core packages, tamper tests and commands for Windows, macOS and Linux.
Data / code included
Litecoin Core 0.21.5.8 released: what the MWEB fixes change
Core 0.21.5.8 strengthens MWEB validation, relay, mining and resource handling. We examine the code, explain the already-passed activation height and provide an operator checklist.

Litecoin security revenue after halvings: what the arithmetic can tell us
A transparent subsidy model for LTC and DOGE, with clear limits on interpreting revenue as network security.

What a 51% Litecoin attack estimate must assume
Our 42 hardware scenarios expose the capacity denominator and omitted costs. Download the model; it does not claim rentable supply or attack feasibility.
Data / code included
Unexpected Litecoin in your wallet? What to check before you send
A small incoming payment, a lookalike in history and a changed clipboard need different checks. Inspect the exact output and authenticate the next destination.
Data / code included
Can an AI agent pay with Litecoin? The controls a real payment needs
A payment request is only the start. A practical Litecoin integration must link an approved purchase to settlement and delivery, protect signing authority and reconcile uncertain attempts before retrying.

If Bitcoin fails: mapping Litecoin dependencies and failure modes
A mechanism-based review of Bitcoin-failure scenarios, with precise cryptographic and software boundaries instead of fixed correlations, automatic contagion or return forecasts.

Before you fund a Litecoin cold wallet, check recovery
A hardware wallet is only one part of cold storage. Verify the account, protect the backup and check recovery before moving the main balance.

Recovering a Litecoin wallet: identify the backup before restoring
Identify the backup format, preserve original files and diagnose a zero balance. Includes a reproducible encrypted Core wallet recovery experiment.
Data / code included
Who develops Litecoin? Code, review, funding and continuity
A practical method for assessing Litecoin development, upstream integration, review capacity and funding without unsupported headcounts or staffing conclusions.

Litecoin and Dogecoin merged mining: stress-test both revenue streams
Model a DOGE downturn and an LTC halving without assuming that two chains share every block or a fixed attack cost.