Good morning list,
I know there have been discussion around how (and if) we should probe the
network to check for the liveliness of a path before sending out the
payment. Currently we issue a payment with a random payment_hash that is
not redeemable by anyone, if the destination (and the path) is
Hi Andrea,
> This saves the receiving node from doing a database lookup
Nodes can and eventually should start using bloom filters to avoid most
database lookups for incoming payment hashes. The false positive rate can be
set to a very low value as the bloom filter doesn't need to transmitted, and
Hi Anton,
I believe all of these will be implemented at some point "soon" within BOLT
rather than as a separate HTTP request.
1. Incoming payment channel request.
At some point after implementing dual-funded channels we will also support
advertising of liquidity providers.
Such liquidity prov
