<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:&gt; &gt; Likewise, I could attach a payment request to an email and send it to you,&#xA;&gt; &gt; and now you can pay me whenever you want forever.&#xA;&gt; &#xA;&gt; That certainly sounds like a plausible use case.  You do still have&#xA;&gt; the problem that e-mail is an insecure channel, but it&#39;s no worse than&#xA;&gt; exchanging Bitcoin addreses over e-mail as things stand at the&#xA;&gt; moment.&#xA;&#xA;On further reflection, I&#39;m not sure I understand this use case of the&#xA;payment protocol.  Since a PaymentRequest currently contains the&#xA;Outputs that specify the addresses to send to, reusing a&#xA;PaymentRequest like this without using stealth addresses implies&#xA;address reuse.&#xA;&#xA;(Granted there are alternative solutions to stealth addresses, such as&#xA;a BIP32-style derivation.)&#xA;&#xA;roy</html></oembed>