📅 Original date posted:2016-08-22
📝 Original message:
On Sun, Aug 21, 2016 at 1:46 PM Rusty Russell <rusty at rustcorp.com.au> wrote:
> > This may not fully solve the problem, since if one presumes that the
> > second-to-last hop is malicious, they can re-create a new onion blob
> > (presuming consistent hashes for each hop, of course).
>
> Great catch. Oops...
>
During the whole payment negotiation process, the sender and receiver can
additionally agree on a shared secret-ish value (possibly the hash of the
contract) that should be included in the per-hop payload for the final hop.
If the portion of the per-hop payload doesn't match identically with this
value, then the payment should be rejected as a prior node has
unsuccessfully attempted re-create the onion packet.
-- Laolu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20160822/1a545f72/attachment.html>;
Olaoluwa Osuntokun [ARCHIVE] /
npub19h…zkvn4
2023-06-09 12:46:28
in reply to nevent1q…4n6w
Author Public Key
npub19helcfnqgk2jrwzjex2aflq6jwfc8zd9uzzkwlgwhve7lykv23mq5zkvn4Published at
2023-06-09 12:46:28Event JSON
{
"id": "d94a6a73f5aa97bb87db16f5058e36a65cba5ec68ab7873dfb73b34462075e5b",
"pubkey": "2df3fc2660459521b852c995d4fc1a93938389a5e085677d0ebb33ef92cc5476",
"created_at": 1686314788,
"kind": 1,
"tags": [
[
"e",
"f166a20039cde752a8ba4e6cccc22d4b2719f9a29840f0c295641243ae59d83f",
"",
"root"
],
[
"e",
"fe950ef3d7bdd62c8a147ab3036c0ca0d4796520be58793cf252b166f2f95ec7",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2016-08-22\n📝 Original message:\nOn Sun, Aug 21, 2016 at 1:46 PM Rusty Russell \u003crusty at rustcorp.com.au\u003e wrote:\n\n\u003e \u003e This may not fully solve the problem, since if one presumes that the\n\u003e \u003e second-to-last hop is malicious, they can re-create a new onion blob\n\u003e \u003e (presuming consistent hashes for each hop, of course).\n\u003e\n\u003e Great catch. Oops...\n\u003e\n\nDuring the whole payment negotiation process, the sender and receiver can\nadditionally agree on a shared secret-ish value (possibly the hash of the\ncontract) that should be included in the per-hop payload for the final hop.\n\nIf the portion of the per-hop payload doesn't match identically with this\nvalue, then the payment should be rejected as a prior node has\nunsuccessfully attempted re-create the onion packet.\n\n\n-- Laolu\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20160822/1a545f72/attachment.html\u003e",
"sig": "72c464e69b7b11d3bf125ee73216fe5ed01dd796f76b323859818a0bd094e446e69ea866d1f85bb37aa3aa3b21b923db2aef96cc5a517ce69de6c2f80950607f"
}