Erick λ

Add BOLT8 (Transport Layer) to Differential Fuzzing Suite

3

### Description Talking with @nGoline, he suggested expanding bitcoinfuzz's differential fuzzing capabilities to include BOLT8, which handles the transport layer protocol in Lightning Network implementations. ### Rationale - BOLT8 defines...

routerrpc: reject payment to invoice that don't have payment secret or blinded paths

9

This PR introduces the initial phase of enforcing payment secret validation for invoices, as described in issue [#9718](https://github.com/lightningnetwork/lnd/issues/9718). > Reject a payment to invoice that don't have a payment secret....

[feature]: Add Support for P2TR Fallback Addresses and Standardize Multiple Fallback Address Handling in BOLT-11

4

**Is your feature request related to a problem? Please describe.** LND currently does not properly support P2TR (Taproot) fallback addresses in BOLT-11 invoices. Additionally, there's ambiguity in how multiple fallback...

### Background After doing some differential fuzzing between `CLN`, `rust-lightning` and `LND` using `bitcoinfuzz` I noticed that `LND` currently accepts bolt11 invoices with empty routing hints in the `r` field,...

### Background After doing some differential fuzzing between `rust-lightining` and `LND` using `bitcoinfuzz` I noticed that `LND` currently accepts Lightning invoices with invalid UTF-8 in the description field (`d`), violating...

Fix currency UTF-8 test vector to actually test invalid UTF-8 sequences

6

The previous test vector for "Malformed: invalid currency UTF-8" was incorrectly testing invalid length encoding (02 length with 2804 value) rather than testing invalid UTF-8 byte sequences in the currency...

The current BOLT specifications require UTF-8 encoding for text fields (e.g., BOLT11 description field, BOLT12 offer descriptions) but don't explicitly address the handling of null bytes (U+0000). While null bytes...

### Background After doing some differential fuzzing between `CLN`, `rust-lightning`, `LND` and `Eclair` using `bitcoinfuzz` I noticed that `Eclair` (`LND` too) currently accepts bolt11 invoices with empty routing hints in...

Eclair/Lightning-kmp incorrectly parses BOLT12 offer with invalid Bech32 encoding

3

Eclair and lightning-kmp is successfully parsing and extracting data from a BOLT12 offer string that contains invalid `Bech32` encoding, while rust-lightning rejects it with a parsing error. bitcoin-kmp's `Bech32` validation...

test: add test for offer parsing with empty paths and valid issuer

3

Verifies that offers with empty paths are accepted as long as the `issuer_id` is set. Follow-up: #4018