<oembed><type>rich</type><version>1.0</version><author_name>npub1trckpcxmceskq4cykxgwxm63n8ugrjrpu5mk83c90e4upsf7d9gqf0f95j</author_name><author_url>https://nostr.ae/npub1trckpcxmceskq4cykxgwxm63n8ugrjrpu5mk83c90e4upsf7d9gqf0f95j</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-01-13&#xA;📝 Original message:rOn Mon, Jan 13, 2014 at 08:57:33PM +0100, Mike Hearn wrote:&#xA;&gt; &gt;&#xA;&gt; &gt; On further reflection, I&#39;m not sure I understand this use case of the&#xA;&gt; &gt; payment protocol.  Since a PaymentRequest currently contains the&#xA;&gt; &gt; Outputs that specify the addresses to send to, reusing a&#xA;&gt; &gt; PaymentRequest like this without using stealth addresses implies&#xA;&gt; &gt; address reuse.&#xA;&gt; &#xA;&gt; &#xA;&gt; Yes indeed ...... which is why we&#39;re talking about extending the protocol&#xA;&gt; (in a future version! the first version isn&#39;t even out yet!).&#xA;&#xA;Yes, sorry, I miscontrued the thread here and now see that your&#xA;message was exactly talking about using stealth addresses within the&#xA;payment protocol.&#xA;&#xA;Sorry for the confusion.&#xA;&#xA;roy</html></oembed>