Electrum

test_lnmsg: add bolt 12 merkle tree test vector

lnmsg: fix parsing of nested complex types where the leaf objects

were consuming too much from the fd.

Co-Authored-By: f321x <f@f321x.com>

lnmsg: validate point primitive field

Validate points to be valid ECPubkeys in lnmsg._read_primitive_field.
There are failing bolt12 test vectors that contain offers with invalid
points.

lnmsg: add new primitive type `bip340sig`, add tlv merkle root calculation and schnorr-sign over tlvs,
implicit en/decode utf8 fields, schnorr signature verification.

Co-Authored-By: f321x <f@f321x.com>

common_qt: move submarine swap support code from qt gui to common_qt as SubmarineSwapMixin

This covers the functionality for swap use during payments (so, change-to-ln and
submarine-payments) present in gui/qt/confirm_tx_dialog, not the 'standalone' swap.

This is in preparation for adding the same functionality to qml.

- move swap support code from TxEditor to SubmarineSwapMixin
- don't require wallet instance at construction, allow late setting of wallet

swaps: add initialize/destroy methods to SwapServerTransport, to simplify consumer side, adds
a done callback so the transport can be used once ready or failure can be handled.

qt: move wait_for_swap_transport to SwapManager

swaps: encapsulate swap transport ongoing_connection_attempt future into transport

qt: refactor message for change-to-lightning swap to backend submarine_swaps.py

qt/send_tab: drop redundant invoice_list.update() after broadcast

The full invoice-list rebuild after a successful broadcast is
unnecessary: the set_broadcasting(PR_BROADCAST) call immediately after
fires the invoice_status callback for any touched invoices, and
main_window.on_event_invoice_status updates the affected rows
incrementally via refresh_item / delete_item. Tx ingestion also sets
need_update, which causes update_tabs() to refresh.

On wallets with many invoices this rebuild iterated all unpaid
invoices and called get_invoice_status() per entry on the GUI thread,
contributing to the post-broadcast freeze fixed in the previous commit.

wallet: cache paid-invoice keys to avoid prevout rescan

On wallets with many outgoing invoices that share output scriptpubkeys,
broadcasting a new transaction froze the GUI for several seconds — up
to a minute on bigger wallets. The hot loops in set_broadcasting() and
_update_onchain_invoice_paid_detection() iterate every invoice touched
by the new tx's outputs, which is large when scriptpubkeys are shared
via _invoices_from_scriptpubkey_map. For each touched invoice they call
_is_onchain_invoice_paid(), which scans all of the invoice's output
scripthashes against _prevouts_by_scripthash and does a get_tx_height
per prevout. Both inner dimensions blow up together when invoices share
inputs/outputs across many past payments.

Add _paid_invoice_keys: Set[str], an in-memory cache of outgoing
invoice ids known to be PR_PAID, maintained incrementally:

- populated at wallet load by _prepare_onchain_invoice_paid_detection
- updated in _update_onchain_invoice_paid_detection (discard then
recompute, so reorgs still demote PAID->UNPAID)
- updated in save_invoice, delete_invoice, clear_invoices
- new on_event_invoice_status listener keeps it in sync with
LN-driven transitions from LNWallet.set_invoice_status

get_invoice_status() short-circuits to PR_PAID on cache hit, skipping
the prevout scan. set_broadcasting() skips already-paid invoices
entirely — broadcasting_status has no effect on a paid invoice and the
callback churn is what made the GUI freeze.

(trivial) move StorageEncryptionVersion and StorageReadWriteError to stored_dict.py

storage: add get_path method

lnpeer: add fixme for unsafe zeroconf behaviour

there is a later check in Channel.update_funded_state
added in https://github.com/spesmilo/electrum/pull/9624
but it only validates the funding_tx once it's already 3 blocks deep

lnchan: if funding tx is coinbase tx, wait for maturity

ref https://github.com/lightning/bolts/commit/17ab3f0dfef50ab98c326a56cb4d109e6f733ab8

onion_messages: filter correct feature when creating paths

Filter channels/peers in `get_blinded_paths_to_me` depending on
the context (onion message or blinded payment path). Raise
according exceptions when no channel/peer is available.

onion_message: pathfinding: ignore amount contraints

Ignore channel amount constraints when doing pathfinding for an
onion message. Onion messages don't need to move funds so pathfinding
shouldn't penalize channels based on fake payment amounts.

onion_message: use trampoline nodes for onion messages

onion_message: handle missing remote update

Handle missing remote channel_update when creating payinfo
for blinded path by skipping the affected channel.

onion_message: add invoice buffer to payinfo cltv delta

Add the 3 block invoice cltv delta buffer to the blinded payinfo's
cltv_expiry_delta to prevent issues where the sender sets the expiry
to exactly local_height + cltv_expiry_delta and blocks get mined
during forwarding.

Modify the 'stored_at' syntax, so that it includes the full path

This may prevent collisions. More importantly, it also makes
it possible to cache the subdict of 'registered_names' that
is relevant to a given StoredDict, so that we do not need to
walk the path on every conversion. (performance optimization,
not part of this commit)

This is a backport from the levelDB branch

onion_message: factor out payinfo creation from get_blinded_paths_to_me

Separates the payinfo creation from get_blinded_paths_to_me into a separate
function.

plugin: nwc: regularly re-broadcast info event

I noticed with my long running NWC deamon that after a
couple days some clients relying on the info event being
available stopped working. Alby e.g. shows
"Error: no info event (kind 13194) returned from relay".
After restarting the daemon it works again for some days.
It seems that relays drop the info events after some days,
even though they are not ephemeral and don't have an expiry tag.
So rebroadcasting them once a day should make the server more
reliable.

plugin: nwc: give NWCServer its own taskgroup

It seemed weird to pass the taskgroup of the plugin into
the NWCServer, this looks a bit cleaner. It also allows
to get multiple tasks of the NWCServer cancelled by cancelling
the NWCServers taskgroup.

simplify prev

tx_from_any: make sanitization optional

re.sub is expensive (calls re.sub), it is not necessary
to call it when instantiating transactions from the wallet file.