Matt Corallo
Matt Corallo
When the user is fetching their current balances after forwarding a payment (before it clears), they'll see a `MaybePreimageClaimableHTLC` and a `MaybeTimeoutClaimableHTLC` but if they sum up their balance using...
One of the most common first-steps in troubleshooting routefinding issues is we ask for the local channel state to determine what the available HTLC bounds are. Thus, we really should...
#2382 noted that in `ChannelManager::peer_connected` the code that used to walk all our channels and send `ChannelAnnouncement` messages in response to peers connecting was made dead code when we moved...
In some cases users will need to access the channelmanager in the event handler, making the current order confusing. See https://github.com/getlipa/ldk-sample-java/pull/1#discussion_r710864480
Should probably avoid needless effort duplication and see what code can be shared with https://github.com/rust-bitcoin/rust-lightning and other rust-bitcoin libraries since everyone having their own lightning implementation means more effort for...
https://github.com/bitcoin/bips/pull/1551 describes a mechanism for mapping human-readable names (in the `Buser@domain` form) to BIP 21 URIs (targeting mostly silent payment addresses and BOLT12 offers). It would be nice if BDK...
As noted previously, `channel_update`s in the onion failure packets are massive gaping fingerprintign vulnerabilities - if a node applies them in a publicly-visible way the err'ing node can easily identify...
As [Human-Readable Names](https://github.com/bitcoin/bips/pull/1551) start getting more traction, having common Bitcoin libraries support the requisite DNS lookups, DNSSEC validation, and BIP 21 parsing would go a long ways towards simplifying wallets....
A BIP 21 QR can contain both an offer and a BOLT 11, the offer should be at lno=, but the current page shows it at lightning=...
Its a bit strange to return a reference to a `Vec` in Rust, when a slice is really intended as the way to do so. Worse, the bindings don't know...