Joost Jager [ARCHIVE] on Nostr: 📅 Original date posted:2019-06-14 📝 Original message: Hi Bastien, > What about ...
📅 Original date posted:2019-06-14
📝 Original message:
Hi Bastien,
> What about having each node add some padding along the way? The erring
> node's padding should be bigger than intermediate nodes' padding (ideally
> using a deterministic construction as you suggest) so details need to be
> fleshed out, but it could mitigate even more the possibility of
> intermediate nodes figuring out their approximate position.
> That also mitigates the risk that a network observer correlates error
> messages between hops (because in the variable-length message that you
> propose, a network observer can easily track an error message across the
> whole payment path).
>
Yes we could also do that. Then even if the same person has two different
nodes in the path, they can't know for sure how many hops were in between.
It would be nice if there is a way to add padding such that hops don't
learn anything about their position, but not sure if that is possible.
Having the error node add padding with a random length between 0 and 20
block sizes (block size is the number of bytes a hop would add in the
backward path), does reveal an upper bound for the distance to the error
node. For example: a node receives a failure with a padding of 3 blocks.
That means that the distance to the error node is between 0 and 3 hops.
Joost
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20190614/ed33e37d/attachment.html>;
📝 Original message:
Hi Bastien,
> What about having each node add some padding along the way? The erring
> node's padding should be bigger than intermediate nodes' padding (ideally
> using a deterministic construction as you suggest) so details need to be
> fleshed out, but it could mitigate even more the possibility of
> intermediate nodes figuring out their approximate position.
> That also mitigates the risk that a network observer correlates error
> messages between hops (because in the variable-length message that you
> propose, a network observer can easily track an error message across the
> whole payment path).
>
Yes we could also do that. Then even if the same person has two different
nodes in the path, they can't know for sure how many hops were in between.
It would be nice if there is a way to add padding such that hops don't
learn anything about their position, but not sure if that is possible.
Having the error node add padding with a random length between 0 and 20
block sizes (block size is the number of bytes a hop would add in the
backward path), does reveal an upper bound for the distance to the error
node. For example: a node receives a failure with a padding of 3 blocks.
That means that the distance to the error node is between 0 and 3 hops.
Joost
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20190614/ed33e37d/attachment.html>;