Bastien TEINTURIER writes:
> Hey again,
>
> Otherwise Mallory gets two invoices, and wants to know if they're
>> actually the same node. Inv1 has nodeid N1, routehint Bob->C1, Inv2 has
>> nodeid N2, routehint Bob->C2.
>
> I think this attack is interesting. AFAICT my proposal defends against
Rusty had some suggestions about how to improve the protocol messages for
this, namely adding a serial_id to the inputs and outputs, which can then
be reused for deletions.
The serial id can then also be used as the ordering heuristic for
transaction inputs during construction (replacing current
Hey again,
Otherwise Mallory gets two invoices, and wants to know if they're
> actually the same node. Inv1 has nodeid N1, routehint Bob->C1, Inv2 has
> nodeid N2, routehint Bob->C2.
>
I think this attack is interesting. AFAICT my proposal defends against this
because of the way
darosior via Lightning-dev writes:
> Hi Pavol,
>
>> 1) Is c-lightning going to support Sphinx or other form of
>> spontaneous payments?
>
> I think cdecker is working on integrating keysend to his noise plugin
> (https://github.com/lightningd/plugins/pull/68).
The keysend functionality is
I'm a bit confused, I don't know if the implementation work you're
mentioning refers to my proposal
or yours :).
When you say `temporary id`, could you clarify whether you mean a temporary
`node_id` or `scid`?
Firstly, need to brute-force the onion against your N keys.
This is probably the
2) lnd is getting the API you need in the next release (v0.10), that
let you subscribe to HTLC events. See PR
https://github.com/lightningnetwork/lnd/pull/3848. The notification
won't be signed (but the stream uses TLS), but that can easily be
added using the `signmessage` API:
