{"type":"rich","version":"1.0","author_name":"npub1trckpcxmceskq4cykxgwxm63n8ugrjrpu5mk83c90e4upsf7d9gqf0f95j","author_url":"https://nostr.ae/npub1trckpcxmceskq4cykxgwxm63n8ugrjrpu5mk83c90e4upsf7d9gqf0f95j","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-01-13\n📝 Original message:\u003e \u003e Likewise, I could attach a payment request to an email and send it to you,\n\u003e \u003e and now you can pay me whenever you want forever.\n\u003e \n\u003e That certainly sounds like a plausible use case.  You do still have\n\u003e the problem that e-mail is an insecure channel, but it's no worse than\n\u003e exchanging Bitcoin addreses over e-mail as things stand at the\n\u003e moment.\n\nOn further reflection, I'm not sure I understand this use case of the\npayment protocol.  Since a PaymentRequest currently contains the\nOutputs that specify the addresses to send to, reusing a\nPaymentRequest like this without using stealth addresses implies\naddress reuse.\n\n(Granted there are alternative solutions to stealth addresses, such as\na BIP32-style derivation.)\n\nroy"}