{
  "review_type": "Assisted editorial source checks; no independent review or unperformed live service tests claimed.",
  "scope": "Five overdue articles only. Original publication dates and URLs are retained. A due review is not by itself evidence of an error.",
  "articles": [
    {
      "article_id": 80,
      "url": "https://litecoin.watch/articles/litecoin-for-freelancers-invoicing-receiving-payments-and-handling-taxes",
      "reviewed_on": "2026-10-25",
      "due_on": "2026-11-25",
      "summary": "Expanded the invoice-to-bank workflow, separated legal invoice requirements and sender/recipient costs, and added a reproducible fictional cash ledger with separate tax-record examples.",
      "changes": [
        {
          "issue": "The complete invoice checklist focused on payment fields and omitted examples of required business invoice details.",
          "correction": "Separate legal invoice requirements from LTC payment instructions; link the UK authority checklist as a labelled jurisdictional example."
        },
        {
          "issue": "The cost table did not clearly identify whose network fee was deducted or how many LTC were actually sold.",
          "correction": "Replace with a native-quantity cash ledger separating client-paid fees, seller transfer fees, gross execution proceeds and bank net; round only at the displayed end."
        },
        {
          "issue": "BTCPay wording did not explain the altcoin maintenance boundary.",
          "correction": "State opt-in/community maintenance and separate invoice software from conversion and fiat settlement; no live integration test claimed."
        },
        {
          "issue": "Existing receipt/disposal tax explanation was broadly sound but lacked a clear separation between cash-route proceeds and tax-gain calculations.",
          "correction": "Keep IRS receipt/basis distinction, label fee-free tax example separately, add a narrowly scoped HMRC valuation note, and identify records rather than promising universal treatment."
        },
        {
          "issue": "Useful operational gaps: quote expiry, sender fee subtraction and wallet payment notes.",
          "correction": "Add authenticated invoice reconciliation workflow and link the existing measured guides; additions are not described as newly discovered errors."
        }
      ],
      "primary_sources": [
        {
          "url": "https://www.gov.uk/invoicing-and-taking-payment-from-customers/invoices-what-they-must-include",
          "checked_claim": "Required UK invoice fields and additional sole trader/company/VAT conditions."
        },
        {
          "url": "https://www.irs.gov/individuals/international-taxpayers/frequently-asked-questions-on-digital-asset-transactions",
          "checked_claim": "Q57-60 service income, receipt fair market value, basis and independent-contractor treatment."
        },
        {
          "url": "https://www.gov.uk/hmrc-internal-manuals/cryptoassets-manual/crypto40100",
          "checked_claim": "Appropriate transaction-time sterling conversion, consistent valuation methodology and records; accounting rules subject to law."
        },
        {
          "url": "https://docs.btcpayserver.org/FAQ/Altcoin/",
          "checked_claim": "Litecoin listed as opt-in altcoin; Bitcoin core focus; community maintenance and integration boundaries."
        }
      ],
      "before_content_sha256": "876151e6fad584d3c0fd40fdc861174f8407dba1fbaf63cdd8895249e0decaf5",
      "after_content_sha256": "5c01b09478df3c9b71c34240feaea856f1b020855de70dc785ced658d96f0659"
    },
    {
      "article_id": 30,
      "url": "https://litecoin.watch/articles/2-million-ltc-stolen-in-phishing-attack-what-happened-and-how-to-protect-yourself",
      "reviewed_on": "2026-10-25",
      "due_on": "2026-11-25",
      "summary": "Clarified what the January theft reports establish, separated reported amounts and attribution from independent verification, and expanded the response checklist for different kinds of exposure.",
      "changes": [
        {
          "kind": "evidence clarification",
          "issue": "The current text uses attributed historical estimates but does not explain the present inability to retrieve the original social-post body.",
          "correction": "Link the canonical X/Telegram posts, disclose this review's access limitation, retain incident date and amounts only as contemporary attributed claims, and make no assertion about final recoveries, manufacturer, exposed seed or exact workflow."
        },
        {
          "kind": "useful addition",
          "issue": "Key isolation, recovery secrecy and recipient verification are discussed but their different failure modes are not made concrete.",
          "correction": "Separate all three controls; explain that a device can correctly sign an attacker's address and that sufficient recovery material can restore access outside the original device."
        },
        {
          "kind": "useful addition",
          "issue": "The existing migration advice does not spell out why restoring an old backup on another device or changing a passphrase is not re-keying.",
          "correction": "Distinguish app password, device PIN, passphrase wallet and threshold backup; explain that transferring to a newly generated wallet is different from restoring the same keys."
        },
        {
          "kind": "useful addition",
          "issue": "The current incident response is a single general paragraph.",
          "correction": "Add a short triage table for message-only, account/remote-access exposure, recovery exposure and wrongly approved payment; preserve evidence and avoid wiping the only working device before recovery is understood."
        },
        {
          "kind": "useful addition",
          "issue": "Readers need a route to apply the prevention advice without providing secrets.",
          "correction": "Link the existing migration planner and cold-storage guide, with clear limits, and expand private evidence/reporting instructions and recovery-scam checks."
        }
      ],
      "primary_sources": [
        {
          "url": "https://trezor.io/guides/backups-recovery/general-standards/how-to-use-a-wallet-backup",
          "checked_claim": "A wallet backup can restore signing access independently of the original device; keep it private and follow the device-specific recovery process."
        },
        {
          "url": "https://trezor.io/guides/backups-recovery/advanced-wallets/what-is-a-passphrase",
          "checked_claim": "A passphrase selects a separate wallet; recovering that wallet requires its exact passphrase as well as the backup, and the feature is not an ordinary resettable app password."
        },
        {
          "url": "https://trezor.io/learn/security-privacy/personal-security-standards/understanding-trezor-wallet-backups-12-20-or-24-words",
          "checked_claim": "Single-share and threshold backups have different recovery requirements; making a new backup for the existing wallet does not invalidate the old one."
        },
        {
          "url": "https://www.ledger.com/academy/hardwarewallet/best-practices-when-using-a-hardware-wallet",
          "checked_claim": "Verify transaction/address details using the trusted signing display rather than relying only on the connected computer; a hardware wallet does not remove operational risks."
        },
        {
          "url": "https://trezor.io/guides/backups-recovery/general-standards/move-crypto-to-a-wallet-with-a-new-wallet-backup",
          "checked_claim": "Compromised backup response uses a newly generated wallet and transfers remaining coins; a replacement device restoring the old backup retains the old keys."
        },
        {
          "url": "https://www.ic3.gov/CrimeInfo/Cryptocurrency",
          "checked_claim": "Useful report details include asset, amount, addresses, transaction hashes, dates and times; recovery services charging upfront are a further risk."
        },
        {
          "url": "https://consumer.ftc.gov/articles/refund-and-recovery-scams",
          "checked_claim": "Earlier scam victims are targeted by unsolicited recovery offers requesting advance payment; claimed knowledge of the loss does not establish legitimacy."
        },
        {
          "url": "https://www.cftc.gov/LearnAndProtect/AdvisoriesAndArticles/6Steps.html",
          "checked_claim": "Stop further losses, preserve original communications/payment evidence, secure affected accounts and report promptly; paid professional advice requires independently verified identity and clear written terms."
        },
        {
          "url": "https://x.com/zachxbt/status/2012212936735912351",
          "checked_claim": "Canonical primary post located; direct body fetch returned 403. NOT independently reverified; historical incident date and amounts remain explicitly attributed to the investigator through contemporary coverage.",
          "access_status": "unavailable"
        },
        {
          "url": "https://t.me/investigations/302",
          "checked_claim": "Canonical Telegram post linked by contemporary coverage; the current fetch returned only a landing page. NOT treated as independently read evidence of final losses or mechanism.",
          "access_status": "landing_only"
        }
      ],
      "before_content_sha256": "59d509bf3468203a913bb7c814c78654debd855c2cede51e85c0cc6d04fba425",
      "after_content_sha256": "389b38ea6a980b8a2b3a287cdbc17d97c3771da292f56e65c4ddcf23caea5020"
    },
    {
      "article_id": 72,
      "url": "https://litecoin.watch/articles/mweb-security-after-the-exploit-what-changed-what-was-fixed-and-what-risks-remain",
      "reviewed_on": "2026-10-25",
      "due_on": "2026-11-25",
      "summary": "Updated the documented MWEB incident and Core-version context, distinguishing consensus fixes, transaction policy, wallet behavior and service restrictions.",
      "changes": [
        {
          "kind": "clarification",
          "issue": "Incident narrative and version statement were tied to a September edition and did not clearly bound the postmortem's own scope.",
          "correction": "Rechecked the actual developer postmortem, kept March/April distinct and attributed, and stated that it does not settle every third-party loss or unrelated later finding."
        },
        {
          "kind": "addition",
          "issue": "Release discussion did not explain where the protections apply.",
          "correction": "Added selected 0.21.5.4, 0.21.5.6 and 0.21.5.8 changes, distinguishing transaction policy, peer-service limits, block validation and restart/reorganization handling."
        },
        {
          "kind": "addition",
          "issue": "Operator checklist offered little inspectable evidence.",
          "correction": "Added read-only Core RPC inspection examples checked against the release's pinned source, with fields to preserve and what they cannot prove."
        },
        {
          "kind": "clarification",
          "issue": "An upgrade, confidentiality and service account credit could be read as one broad security outcome.",
          "correction": "Separated binary authenticity, actual process deployment, consensus validity, privacy, wallet recovery and application accounting; no network-wide upgrade percentage or safety guarantee is claimed."
        },
        {
          "kind": "addition",
          "issue": "Service recovery guidance lacked a concrete evidence ledger.",
          "correction": "Added proposed pause/resume and reconciliation records, same-height hash comparison and limits of a small operational test."
        }
      ],
      "primary_sources": [
        {
          "url": "https://litecoin.com/news/litecoin-mweb-security-incident-postmortem",
          "checked_claim": "Developer-authored 28 April 2026 account establishes the March and April events, coordinated recovery and limits of the loss/security scope."
        },
        {
          "url": "https://api.github.com/repos/litecoin-project/litecoin/releases/latest",
          "checked_claim": "Fresh API capture identifies stable non-prerelease v0.21.5.8, published 12 September 2026; no claim about every deployed node."
        },
        {
          "url": "https://github.com/litecoin-project/litecoin/releases/tag/v0.21.5.4",
          "checked_claim": "Release notes list MWEB input/accounting checks, kernel-fee overflow, mutated-block data handling and associated regression work."
        },
        {
          "url": "https://github.com/litecoin-project/litecoin/releases/tag/v0.21.5.6",
          "checked_claim": "Release notes distinguish light-client resource limits, early transaction policy, malformed-data handling and the height 3,154,440 encoding rule."
        },
        {
          "url": "https://github.com/litecoin-project/litecoin/releases/tag/v0.21.5.8",
          "checked_claim": "Full-body revalidation, disk/reorganization/crash paths, relay/mining/resource changes, miner-distributed 0.21.5.7 and height 3,172,640 extra-data rule."
        },
        {
          "url": "https://github.com/litecoin-project/litecoin/blob/ec1b6489a900d09cf5991e220dce089c77a232a2/src/rpc/net.cpp",
          "checked_claim": "Pinned getnetworkinfo definition returns server version/subversion, connections and warnings; source inspected, command not executed."
        },
        {
          "url": "https://github.com/litecoin-project/litecoin/blob/ec1b6489a900d09cf5991e220dce089c77a232a2/src/rpc/blockchain.cpp",
          "checked_claim": "Pinned getblockchaininfo definition documents network, blocks, headers, bestblockhash, initialblockdownload and verificationprogress."
        },
        {
          "url": "https://github.com/litecoin-project/lips/blob/master/lip-0003.mediawiki",
          "checked_claim": "Optional extension-block and peg-in/out design; draft design is not service compatibility evidence."
        }
      ],
      "before_content_sha256": "7fbd6087a1090488f8fc7883f22960ef9976b3198002d5beb44d5e7224ee1b23",
      "after_content_sha256": "7428b3da6831329800040ade9a9e2039ab2f7ec30dfe8032f2d08fd17f26b79b"
    },
    {
      "article_id": 59,
      "url": "https://litecoin.watch/articles/common-litecoin-scams-in-2026-and-how-to-protect-yourself",
      "reviewed_on": "2026-10-25",
      "due_on": "2027-01-25",
      "summary": "Expanded documented scam examples and verification steps, including the limits of phishing-resistant login, signed checksums and native Litecoin signing.",
      "changes": [
        {
          "kind": "substantive correction",
          "issue": "The opening says most cryptocurrency scams exploit authorization and trust without a dataset establishing that majority.",
          "correction": "Describe observable request patterns without the unsupported 'most' prevalence claim."
        },
        {
          "kind": "useful addition",
          "issue": "A familiar sender or polished support message can be mistaken for proof of authenticity.",
          "correction": "Add the separately identified September 2026 Trezor/Brevo example using Trezor's own notice, without suggesting that wallet systems were compromised or linking it to the January theft."
        },
        {
          "kind": "useful addition",
          "issue": "The brief hardware-security-key FAQ does not clearly separate phishing-resistant login, payment approval and recovery secrets.",
          "correction": "Explain FIDO/WebAuthn's account-authentication scope, its limits, and the difference between a security key and a cryptocurrency hardware wallet."
        },
        {
          "kind": "useful addition",
          "issue": "The fake-investment section does not warn that a successful small withdrawal can be staged.",
          "correction": "Use FBI/IC3 guidance to explain early-withdrawal confidence building and repeated taxes/fees demanded to unlock a larger amount; verify the actual firm and contact route."
        },
        {
          "kind": "useful addition",
          "issue": "The checksum section is correct but leaves the reader without an ordered authentication workflow.",
          "correction": "Add source/platform/signature/fingerprint/hash checks, identify the signed-checksum file in the reviewed official Core directory, and keep the PowerShell example read-only with a placeholder path."
        },
        {
          "kind": "clarification",
          "issue": "Dust, message signatures, native LTC transfers and external token approvals can require different responses.",
          "correction": "Keep dust separate from private-key theft; distinguish Ethereum token allowances from ordinary native LTC transfers and explain why approval revocation does not repair a stolen Litecoin backup."
        },
        {
          "kind": "useful addition",
          "issue": "Recovery-service credentials alone can look like an endorsement or sufficient proof.",
          "correction": "Reject unsolicited upfront guarantees while distinguishing independently verified paid professional advice with a written scope and costs; expand private evidence handling and link the existing safe-support guide."
        }
      ],
      "primary_sources": [
        {
          "url": "https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams",
          "checked_claim": "Impersonation, giveaways, fabricated investment returns and demands for more money are documented scam patterns; cryptocurrency payments lack a general card-style chargeback."
        },
        {
          "url": "https://trezor.io/blog/news/security-incident-at-brevo-our-third-party-email-provider",
          "checked_claim": "Trezor's September 2026 notice says its newsletter provider was used to send a phishing email leading to an app asking for wallet backups; newsletter contacts, not product/wallet systems, were affected. No linkage to January theft inferred."
        },
        {
          "url": "https://trezor.io/learn/security-privacy/personal-security-standards/scams-and-phishing",
          "checked_claim": "Unsolicited support/update requests must not obtain wallet backups, PINs, passwords or codes; independently reopen a verified product/support channel."
        },
        {
          "url": "https://www.cisa.gov/sites/default/files/2023-01/fact-sheet-implementing-phishing-resistant-mfa-508c.pdf",
          "checked_claim": "FIDO/WebAuthn provides phishing-resistant account authentication. This is not transaction-destination verification or protection for a separately disclosed recovery phrase."
        },
        {
          "url": "https://trezor.io/support/troubleshooting/coins-tokens/what-are-address-poisoning-attacks-and-how-to-avoid-them",
          "checked_claim": "Lookalike addresses can be inserted into history; check the whole destination on the device and avoid copying from transaction history. Receipt of such an entry alone does not leak a private key."
        },
        {
          "url": "https://trezor.io/support/troubleshooting/coins-tokens/dusting-attacks-airdrop-scam-tokens",
          "checked_claim": "On UTXO networks dust consolidation can link activity; unsolicited amounts and external token interactions have distinct risks. The article avoids universal claims that any received dust steals keys."
        },
        {
          "url": "https://www.ic3.gov/CrimeInfo/Investment",
          "checked_claim": "Fake investment schemes may allow early withdrawals to build trust, then demand new taxes or fees to release a larger balance."
        },
        {
          "url": "https://github.com/litecoin-project/litecoin/releases",
          "checked_claim": "Official Litecoin Core release location; links to project downloads and version-specific checksums."
        },
        {
          "url": "https://download.litecoin.org/litecoin-0.21.5.8/",
          "checked_claim": "The checked release directory contains SHA256SUMS.asc and a signing-key file; this does not independently authenticate a key downloaded from the same place."
        },
        {
          "url": "https://trezor.io/guides/trezor-suite/download-verify-trezor-suite",
          "checked_claim": "Download verification is distinct from running an installer; signature verification requires checking the expected signing-key fingerprint."
        },
        {
          "url": "https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash?view=powershell-7.5",
          "checked_claim": "Get-FileHash -Algorithm SHA256 -LiteralPath computes a local file hash without executing the downloaded file."
        },
        {
          "url": "https://eips.ethereum.org/EIPS/eip-20",
          "checked_claim": "ERC-20 defines approve/allowance/transferFrom permissions for Ethereum tokens; that mechanism is not created by an ordinary native LTC payment."
        },
        {
          "url": "https://trezor.io/guides/backups-recovery/general-standards/move-crypto-to-a-wallet-with-a-new-wallet-backup",
          "checked_claim": "When recovery material is compromised, remaining funds need a newly generated wallet rather than merely a new application password/device."
        },
        {
          "url": "https://www.ic3.gov/CrimeInfo/Cryptocurrency",
          "checked_claim": "Preserve asset, network, amount, addresses, transaction IDs and timestamps; report via verified authorities and be cautious about recovery services."
        },
        {
          "url": "https://consumer.ftc.gov/articles/refund-and-recovery-scams",
          "checked_claim": "Unsolicited recovery offers demanding advance payment can cause a second loss."
        },
        {
          "url": "https://www.cftc.gov/LearnAndProtect/AdvisoriesAndArticles/6Steps.html",
          "checked_claim": "Report promptly, protect affected accounts, verify professional help independently and request a written scope and costs; recovery is not guaranteed."
        }
      ],
      "before_content_sha256": "2edf24f1aa78684141c5cc30bcd0519c1a0607783b13c1c2c77cce5edfc4e152",
      "after_content_sha256": "62dd147fd5708620b2c9200cdab00a9aea86d5985c02361911e38919b2a3971d"
    },
    {
      "article_id": 39,
      "url": "https://litecoin.watch/articles/tristero-adds-mweb-support-litecoin-privacy-gets-easier",
      "reviewed_on": "2026-10-25",
      "due_on": "2026-11-25",
      "summary": "Clarified documented MWEB destination support and the reserve-funded Feather swap route, with limits, return paths and the meaning of its slippage setting.",
      "changes": [
        {
          "kind": "correction",
          "issue": "The earlier X-based account left the documented direction of MWEB support vague.",
          "correction": "Replaced the inaccessible X announcement as the central proof with the directly read 17 March operator post: buying LTC and sending to MWEB addresses was announced; full end-to-end MWEB was discussed as a possible expansion."
        },
        {
          "kind": "correction",
          "issue": "The dated Binance link was the article's practical compatibility example.",
          "correction": "Fresh direct retrieval was unusable; replaced the current-policy example with Kraken's 22 October 2026 documentation explicitly restricting MWEB deposits including peg-outs."
        },
        {
          "kind": "addition",
          "issue": "The service architecture remained generic despite current primary documentation.",
          "correction": "Added the distinction between EVM signed-order/smart-contract paths and the reserve-funded Feather deposit/output route; marketing custody labels are not independently endorsed."
        },
        {
          "kind": "addition",
          "issue": "Missing route-specific limits could mislead a reader funding a swap.",
          "correction": "Added the documented return-address and MaxInput behavior, unspecified late-deposit grace period, and MaxSlippage default 0 meaning no limit. These are documentation findings, not live enforcement tests."
        },
        {
          "kind": "addition",
          "issue": "No structured way to reconcile source payment, service order and destination receipt.",
          "correction": "Added three separate evidence records, fictional net-output arithmetic and a check-before-retry workflow without creating any quote or trade."
        },
        {
          "kind": "clarification",
          "issue": "Historical announcement and current LTC asset listing could imply tested current MWEB availability.",
          "correction": "Kept the announcement historical; explicitly left current MWEB input/output availability, pair liquidity, backend implementation, reserve sufficiency and independent audit unverified."
        }
      ],
      "primary_sources": [
        {
          "url": "https://litecointalk.io/t/litecoin-swaps-are-now-live-on-tristero-mweb-enabled/81401",
          "checked_claim": "17 March 2026 project announcement identifies BTC/ETH/SOL/XMR-to-LTC swaps and sending to MWEB addresses; wider end-to-end support is conditional future language."
        },
        {
          "url": "https://docs.tristero.com/docs/tristero",
          "checked_claim": "Current product documentation distinguishes EVM trading from Feather cross-VM exchanges including LTC."
        },
        {
          "url": "https://docs.tristero.com/docs/feather",
          "checked_claim": "Feather describes watching incoming deposits and paying outputs from reserves, without smart contracts or cross-chain messaging in that model."
        },
        {
          "url": "https://docs.tristero.com/docs/feather/supported-assets",
          "checked_claim": "Native LTC is listed on Litecoin; the list does not establish an MWEB direction or a live quote."
        },
        {
          "url": "https://docs.tristero.com/docs/feather/quickstart",
          "checked_claim": "Automatic chaining from smart-contract routes to Feather is not currently supported; manual sequential trades are distinct routes."
        },
        {
          "url": "https://docs.tristero.com/docs/feather/api/createTrade",
          "checked_claim": "Trade fields distinguish output and return addresses; MaxSlippage is a fraction and documented default 0 means no limit."
        },
        {
          "url": "https://docs.tristero.com/docs/feather/concepts/liquidity",
          "checked_claim": "Return handling depends on return-address provision, input limit and output liquidity; the page warns of excess-deposit loss without a return address."
        },
        {
          "url": "https://docs.tristero.com/docs/feather/concepts/states",
          "checked_claim": "No-deposit expiry is described as 2 hours; an unspecified grace period is mentioned. Delivery guarantees are the project's claims, not independently verified here."
        },
        {
          "url": "https://docs.tristero.com/docs/feather/api/getStatus",
          "checked_claim": "The endpoint reports service order state by TradeID, distinct from independently verified destination evidence."
        },
        {
          "url": "https://docs.tristero.com/docs/feather/api/getPrice",
          "checked_claim": "Quote documentation includes amount, price and capacity information; no live quote obtained."
        },
        {
          "url": "https://support.kraken.com/articles/203325283-cryptocurrency-deposit-processing-times",
          "checked_claim": "Policy dated 22 October 2026 states MWEB Litecoin deposits including peg-outs will not be credited and may be lost. Unrelated erroneous BTC 15-minute FAQ wording was not adopted."
        },
        {
          "url": "https://github.com/litecoin-project/lips/blob/master/lip-0003.mediawiki",
          "checked_claim": "Optional MWEB extension-block design and movement between transparent and MWEB forms."
        },
        {
          "url": "https://github.com/litecoin-project/lips/blob/master/lip-0004.mediawiki",
          "checked_claim": "One-sided transaction design complements LIP3; neither proposal is a service feature list."
        },
        {
          "url": "https://litecoin.com/news/litecoin-mweb-security-incident-postmortem",
          "checked_claim": "Primary developer account documents 2026 validation and service availability incidents; no current incident-free claim."
        },
        {
          "url": "https://github.com/litecoin-project/litecoin/releases/tag/v0.21.5.8",
          "checked_claim": "Current stable public Core release checked for operational context, not proof of Tristero deployment."
        }
      ],
      "before_content_sha256": "d685d0b18f9a1d506f5a53068bdf6c7dc1787b6d22888ab725237b7957e4b932",
      "after_content_sha256": "8bd45c09d5d09f31e528dffa288975843d36a2d5e393c1528537485831e096af"
    }
  ]
}