Hi Rusty,
> 1. query_short_channel_id
> IMPLEMENTATION: trivial
*thumbs up*
> 2. query_channel_range/reply_channel_range
> IMPLEMENTATION: requires channel index by block number, zlib
For the sake of expediency of deployment, if we add a byte (or two) to
denote the encoding/compression scheme,
> I am a bit concerned with the privacy implications of having either a
signed
> invoice
> In particular, I am concerned that it might provide cryptographic evidence
> to the buyer that a certain seller performed the transaction, and/or
> evidence to the seller that a certain buyer performed the t
Hi Rusty,
> The proof-of-payment here is a red herring, I think. If we remove the
> destination awareness, the privacy issues seem greatly reduced.
>
Red herring = "something that misleads or distracts from a relevant or
important issue"[1]? Do you mean the proof-of-payment is irrelevant for
the p
