<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2023-10-03T21:45:55Z</updated>
  <generator>https://njump.me</generator>

  <title>Nostr notes by Tony Giorgio PM [ARCHIVE]</title>
  <author>
    <name>Tony Giorgio PM [ARCHIVE]</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://njump.me/npub1erc4qwsluhd7utrc028243jyv5veflq32hjpfzgvxvh8uh4h34tsv60a6n.rss" />
  <link href="https://njump.me/npub1erc4qwsluhd7utrc028243jyv5veflq32hjpfzgvxvh8uh4h34tsv60a6n" />
  <id>https://njump.me/npub1erc4qwsluhd7utrc028243jyv5veflq32hjpfzgvxvh8uh4h34tsv60a6n</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://njump.me/nevent1qqsq8kskdc0tvgegdss2d9m47chmc6xs0n0tpxnyfvpdhq35xcc8a0gzyry0z5p6rljahm3v0paga2kxg3j3n98uz927g9yfpsejulj7k7x4wwygsva</id>
    
      <title type="html">📅 Original date posted:2023-09-26 🗒️ Summary of this ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsq8kskdc0tvgegdss2d9m47chmc6xs0n0tpxnyfvpdhq35xcc8a0gzyry0z5p6rljahm3v0paga2kxg3j3n98uz927g9yfpsejulj7k7x4wwygsva" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsfx68jcnnm7p0nyu5pdd5e4nz7q9wc629gj76yr35um8jmdj7phps442uf9&#39;&gt;nevent1q…2uf9&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;📅 Original date posted:2023-09-26&lt;br/&gt;🗒️ Summary of this message: The sender discusses the concept of decorrelated payments and suggests that the research on Payment Splitting &amp;amp; Switching (PSS) could help with this. PSS allows for route and amount changes without the sender&amp;#39;s knowledge, which could mitigate probing and jamming attacks. The sender provides a link to the research write-up for more information.&lt;br/&gt;📝 Original message:&lt;br/&gt;Gijs,&lt;br/&gt;&lt;br/&gt;I love the concept, will have to look at it more. One thought I have had &lt;br/&gt;on this subject is that it can also help decorrelated payments on an &lt;br/&gt;amount analysis level. It&amp;#39;s a step up after we have PTLC&amp;#39;s and more &lt;br/&gt;timing analysis protections. Curious if you see that as being a &lt;br/&gt;possibility with this research write up we did last year:&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://lightningprivacy.com/en/routing-analysis#splintered-payments&#34;&gt;https://lightningprivacy.com/en/routing-analysis#splintered-payments&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Tony Giorgio&lt;br/&gt;&lt;br/&gt;On 9/22/23 09:53, Gijs van Dam wrote:&lt;br/&gt;&amp;gt; Good afternoon list,&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; I have touched on Link MPP over alternative routes before [0]. The &lt;br/&gt;&amp;gt; idea is that a node inside a payment route finds an alternative route &lt;br/&gt;&amp;gt; to the next node via one (or more) intermediary nodes. ZmnSCPxj and &lt;br/&gt;&amp;gt; Christian Decker were kind enough to discuss the topic with me a bit &lt;br/&gt;&amp;gt; more, and since it seemed feasible I went ahead and made a proof of &lt;br/&gt;&amp;gt; concept by developing a core-lighting plugin called Payment Splitting &lt;br/&gt;&amp;gt; &amp;amp; Switching (PSS) [1]. There is also a screencast showing the plugin &lt;br/&gt;&amp;gt; in action. [2]&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; The plugin works as follows. The plugin announces its support for PSS &lt;br/&gt;&amp;gt; at `init`. If Alice and Bob both support PSS, and Alice receives a &lt;br/&gt;&amp;gt; payment to be relayed to Bob, she can decide to split up the payment &lt;br/&gt;&amp;gt; into multiple parts. One part will follow the original route and use &lt;br/&gt;&amp;gt; the original onion, but it will commit to an HTLC that carries an &lt;br/&gt;&amp;gt; amount less than the intended amount. Upon receiving that HTLC Bob &lt;br/&gt;&amp;gt; receives the onion that allows him to forward the payment, but because &lt;br/&gt;&amp;gt; the HTLC carries less than expected, he will wait for another payment &lt;br/&gt;&amp;gt; from Alice. Alice sends that payment like a normal payment to Bob over &lt;br/&gt;&amp;gt; an alternative route, e.g. via a single intermediary node, but &lt;br/&gt;&amp;gt; contingent on the payment hash of the original payment. Bob does a &lt;br/&gt;&amp;gt; little bit of housekeeping to check if the combined HTLCs are enough &lt;br/&gt;&amp;gt; for him to forward the payment, and if so, the payment is forwarded as &lt;br/&gt;&amp;gt; normal.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; My interest in Link MPP and PSS (which is basically Link MPP combined &lt;br/&gt;&amp;gt; with JIT-routing [3]) arose through my research in the Balance &lt;br/&gt;&amp;gt; Discovery Attack (BDA), aka the probing attack. From the perspective &lt;br/&gt;&amp;gt; of that attack it is interesting to note that PSS allows for route &lt;br/&gt;&amp;gt; changes and amount changes *without the sender knowing about it*. So &lt;br/&gt;&amp;gt; when an attacker has to assume that PSS is used, its interpretation of &lt;br/&gt;&amp;gt; information obtained through a BDA changes completely. Using &lt;br/&gt;&amp;gt; real-world data in an LN simulator I saw up to a 62% drop in &lt;br/&gt;&amp;gt; information gain when PSS is deployed compared to earlier work (Alex &lt;br/&gt;&amp;gt; Biryukov et al.) without PSS [4].&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; For details I refer to my preprint on the Cryptology ePrint Archive &lt;br/&gt;&amp;gt; [5]. Any feedback on it would be highly appreciated. I would also love &lt;br/&gt;&amp;gt; to hear your thoughts on what role PSS could play, if any, in &lt;br/&gt;&amp;gt; mitigating probing and/or jamming.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; Because the paper is at times quite technical, I have also written a &lt;br/&gt;&amp;gt; set of blog posts introducing the research. [7][8]&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; Finally, I think PSS would also work with PTLC, but because this post &lt;br/&gt;&amp;gt; is long enough as is, I will leave that for another time.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; Thank you for your time,&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; Gijs van Dam&lt;br/&gt;&amp;gt; &lt;a href=&#34;https://www.gijsvandam.nl&#34;&gt;https://www.gijsvandam.nl&lt;/a&gt;&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; [0]: &lt;br/&gt;&amp;gt; &lt;a href=&#34;https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-August/003144.html&#34;&gt;https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-August/003144.html&lt;/a&gt;&lt;br/&gt;&amp;gt; [1]: &lt;a href=&#34;https://github.com/gijswijs/plugins/tree/master/pss&#34;&gt;https://github.com/gijswijs/plugins/tree/master/pss&lt;/a&gt;&lt;br/&gt;&amp;gt; [2]: &lt;a href=&#34;https://asciinema.org/a/520416&#34;&gt;https://asciinema.org/a/520416&lt;/a&gt;&lt;br/&gt;&amp;gt; [3]: &lt;br/&gt;&amp;gt; &lt;a href=&#34;https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-March/001891.html&#34;&gt;https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-March/001891.html&lt;/a&gt;&lt;br/&gt;&amp;gt; [4]: &lt;a href=&#34;https://link.springer.com/book/9783031182846&#34;&gt;https://link.springer.com/book/9783031182846&lt;/a&gt;&lt;br/&gt;&amp;gt; [5]: &lt;a href=&#34;https://eprint.iacr.org/2023/1360&#34;&gt;https://eprint.iacr.org/2023/1360&lt;/a&gt;&lt;br/&gt;&amp;gt; [7]: &lt;br/&gt;&amp;gt; &lt;a href=&#34;https://www.gijsvandam.nl/post/all-types-of-multi-part-payments-in-lightning-network-explained/&#34;&gt;https://www.gijsvandam.nl/post/all-types-of-multi-part-payments-in-lightning-network-explained/&lt;/a&gt;&lt;br/&gt;&amp;gt; [8]: &lt;br/&gt;&amp;gt; &lt;a href=&#34;https://www.gijsvandam.nl/post/the-effect-of-multi-part-payments-on-the-balance-disovery-attack/&#34;&gt;https://www.gijsvandam.nl/post/the-effect-of-multi-part-payments-on-the-balance-disovery-attack/&lt;/a&gt;&lt;br/&gt;&amp;gt;
    </content>
    <updated>2023-10-18T13:02:07Z</updated>
  </entry>

</feed>