{"type":"rich","version":"1.0","author_name":"npub1ncnj8arudstdxzfhxk7k4nwgkrw3hyw8sgt0wqqmm5hh2c4knmgs2lqt2n","author_url":"https://nostr.ae/npub1ncnj8arudstdxzfhxk7k4nwgkrw3hyw8sgt0wqqmm5hh2c4knmgs2lqt2n","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2018-02-08\n📝 Original message:\nIf using two hashes to deliver the payment while still getting a proof, I'm\nnot sure what that provides above just sending regular lightning payments\nover multiple routes with one hash. Firstly, if there is a second hash, it\nwould presumably be the same for all routes, making them linkable again,\nwhich AMP tries to solve. And secondly, the receiver has no incentive to\nclaim any of the HTLCs before all of them are locked in, because in that\ncase they are releasing the transaction receipt before fully being paid.\n\nOn Thu, Feb 8, 2018 at 8:41 AM, Johan Torås Halseth \u003cjohanth at gmail.com\u003e\nwrote:\n\n\u003e An obvious way to make this compatible with proof-of-payment would be to\n\u003e require two hashes to claim the HTLC: the presage from the invoice payment\n\u003e hash (as today) + the new hash introduced here. This would give the sender\n\u003e a receipt after only one of the HTLCs was claimed. Would require changes to\n\u003e the scripts of course.\n\u003e\n\u003e With Schnorr/EC operations this could probably be made more elegant, as\n\u003e mentioned.\n\u003e\n\u003e - Johan\n\u003e On Wed, Feb 7, 2018 at 18:21, Rusty Russell \u003crusty at rustcorp.com.au\u003e wrote:\n\u003e\n\u003e Olaoluwa Osuntokun \u003claolu32 at gmail.com\u003e writes:\n\u003e \u003e Hi Y'all,\n\u003e \u003e\n\u003e \u003e A common question I've seen concerning Lightning is: \"I have five $2\n\u003e \u003e channels, is it possible for me to *atomically* send $6 to fulfill a\n\u003e \u003e payment?\". The answer to this question is \"yes\", provided that the\n\u003e receiver\n\u003e\n\u003e This is awesome! I'm kicking myself for not proposing it :)\n\u003e\n\u003e Unfortunately, your proposal defines a way to make multipath donations,\n\u003e not multipath payments :(\n\u003e\n\u003e In other words, you've lost proof of payment, which IMHO is critical.\n\u003e\n\u003e Fortunately, this can be fairly trivially fixed when we go to scriptless\n\u003e scripts or other equivalent decorrelation mechanism, when I think this\n\u003e mechanism becomes extremely powerful.\n\u003e\n\u003e \u003e - Potential fee savings for larger payments, contingent on there being a\n\u003e \u003e super-linear component to routed fees. It's possible that with\n\u003e \u003e modifications to the fee schedule, it's actually *cheaper* to send\n\u003e \u003e payments over multiple flows rather than one giant flow.\n\u003e\n\u003e This is a stretch. I'd stick with the increased reliability/privacy\n\u003e arguments which are overwhelmingly compelling IMHO.\n\u003e\n\u003e If I have any important feedback on deeper reading (and after a sccond\n\u003e coffee), I'll send a separate email.\n\u003e\n\u003e Thanks!\n\u003e Rusty.\n\u003e _______________________________________________\n\u003e Lightning-dev mailing list\n\u003e Lightning-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e Lightning-dev mailing list\n\u003e Lightning-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180208/31041639/attachment.html\u003e"}