Electrum

This commit only updates comments in a build script for Android. It adds guidance about how to build test versions of the Electrum Android app and warns about a known build issue. No code behavior changes, no security fix or vulnerability introduced.

This is a routine build fix for Electrum's Linux AppImage packaging. The Alpine Linux package repository no longer offered an older version of the xz compression library, so the build script was updated to request the newer available version. There is no indication this change fixes or introduces a security vulnerability; it simply makes the automated build work again.

This commit is a minor code cleanup: it replaces a hard-coded number (10,000,000 satoshis) with a named constant called MAX_SWAP_AMT. The value is exactly the same as before, and the developer's own comment says it is only there to reduce accidental damage and is not enforced by the client. There is no security fix here.

This commit only changes internal test code for Electrum's 'toyserver' test harness. It improves how the fake server sorts transaction history and handles unconfirmed transactions in tests. There are no changes to production wallet or server code, and no security fix or vulnerability is present.

This commit only changes test code. It adds unit tests and expands a fake 'toy' Electrum server used in automated testing so it can simulate Bitcoin mempool transaction replacement. Nothing in production code is modified, so real Electrum users are not affected.

This commit adds a clearer error message inside Electrum's wallet code when a developer passes the wrong kind of transaction output object to a function that builds unsigned transactions. It is a defensive programming/debugging improvement, not a security fix. There is no indication it addresses a vulnerability or changes user-facing behavior beyond producing a more informative error.

This commit is a pure test-code reorganization: it moves the existing 'toyserver' helper from a single file into a new subdirectory package and updates the import path in one test file. No production code is changed, no behavior is altered, and there is no security fix or vulnerability introduced.

This commit only changes a test helper file (tests/toyserver.py). It extends a fake Bitcoin server used in Electrum's test suite so that when a transaction is removed from the simulated mempool, all dependent child transactions are also removed. There is no change to production code, no real wallet or network behavior is affected, and no security vulnerability is present in the diff.

This commit only adds test infrastructure. It introduces an ordered set helper class and expands a fake Bitcoin server used in unit tests so it can remove transactions from the mempool and simulate blockchain reorganizations. There is no change to production wallet code, networking, or cryptography, and nothing in the commit suggests a security fix or vulnerability.

This commit only adds a test-only 'faucet' feature to Electrum's internal toy server used by unit tests. It replaces a hard-coded test transaction with a dynamically generated one so tests can create their own fake Bitcoin for testing. There is no change to production wallet code, network handling, or user-facing behavior, and no security issue is present.

This commit only changes internal test code. It improves a small fake Bitcoin server used during automated tests so that it properly tracks unspent coins and rejects double-spending attempts. No production wallet or network code is affected, and there is no security risk to real users.

This commit only moves the code that starts and stops a small test server into the test server class itself. It is a cleanup of the test code and does not change any user-facing behavior or fix a security issue.

This commit is a simple housekeeping change in the project's test code. It moves a helper mock server (used only for automated testing) out of one test file and into a new dedicated file. There is no change to the actual Electrum wallet software that users run, and no security issue is present.

This commit only refactors the test code in Electrum. It splits a mock server class used for unit tests into two parts: a shared 'ToyServer' that holds fake blockchain state, and a 'ToyServerSession' that represents one client connection. No production wallet or network code is changed, and there is no security fix or vulnerability introduced.

This commit only adds a comment explaining how to enable debug logging of JSON network traffic. No code behavior changes, no security fix or vulnerability introduced.

This commit removes a helper that silently stripped unknown bits from Lightning channel-type flags during channel setup. Previously, if a peer sent a channel type containing an unrecognized flag, Electrum would drop that flag and continue. Now it keeps the full value and enforces that the peer's channel type exactly matches what Electrum expects and supports. This is a hardening change: it closes a path where a malicious or buggy peer could trick Electrum into accepting a channel type it did not actually agree to.

This commit changes Electrum's Lightning code so that, by default, it refuses to open new 'static_remotekey' channels unless they also use 'anchors'. Static_remotekey is an older channel type. The change is defensive: it prevents users from accidentally opening a less modern channel type, but it does not fix an active bug or vulnerability in existing channels. The commit message and code comments do not describe this as a security fix.

This commit only changes test code. It makes anchor channels the default setting for Electrum's Lightning test suite and removes the need to pass an explicit 'has_anchors' flag when creating mock wallets in tests. There is no change to the actual wallet or Lightning code that users run, so it does not affect real-world security.

This is a test-only cleanup commit. It removes a redundant 'anchor_outputs' parameter from helper functions used in Lightning Network tests and instead derives the channel type from a wallet configuration flag. It also re-enables an internal assertion that was previously commented out. There is no change to production wallet behavior or user-facing security.

This commit changes Electrum's Lightning wallet so it now requires anchor-style channels by default and removes the old user-facing setting that let people opt out. It replaces the opt-out with a hidden testing-only flag for older channel types. The change is a deliberate protocol hardening step, not a fix for an active exploit, though the commit message notes a follow-up is needed to fully block incoming old-style channels.

This is a small internal code cleanup in Electrum's Lightning onion message handling. It removes a redundant function parameter and lets the code figure out the same thing from an existing parameter. There is no security fix or behavior change visible in the commit.

This commit is a routine cleanup to match a recent change in the Lightning Network specifications. It renames a field from 'encrypted_data' to 'encrypted_recipient_data' everywhere and removes an old workaround that handled two different names. There is no indication this fixes a security bug; it is a standards-alignment refactor.

This commit only adds comments and a docstring to an existing Lightning Network payment function. No code behavior changes. The commit message explicitly says the change is meant to counter mistaken automated vulnerability reports, not to fix a real bug.

This commit tightens how Electrum's Lightning code handles channel setup messages. Previously, the code tolerated missing optional fields (channel_type) in some situations; now it requires them to be present and rejects the connection if they are missing. This is a defensive hardening change that reduces the chance of a peer tricking the wallet into opening a channel with unexpected or unsafe settings.

This commit is a small internal cleanup in Electrum's Lightning networking code. It introduces a single `self.config` shortcut so the code always reads settings from the same place instead of sometimes using `self.network.config` and sometimes `self.lnworker.config`. There is no user-facing change and no security fix.