{"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-03-20\n📝 Original message:On Thu, Mar 20, 2014 at 07:31:27PM +0100, Mike Hearn wrote:\n\n\u003e Yes, this overlaps somewhat with the PKI signing in BIP70, but not\n\u003e entirely - you might want to serve unsigned payment requests, but\n\u003e still have confidentiality and authenticity for a local face to face\n\u003e transaction. The signing and encryption does different things\n\nI'm not sure if this what you're getting at, but in a common\nface-to-face scenario, it really doesn't overlap so much (in that the\nPKI in BIP70 isn't really helpful).\n\nIt's not unusual, in a face-to-face transaction at a bricks-and-mortar\nestablishment, that you know neither the legal name of the entity\nrunning the establishment, nor any electronic identifier (domain name,\nemail address) that might be presented to you in an X.509 certificate,\neven if such a certificate is presented in the PaymentRequest.\n\nIn many cases I want/need to simply be assured that I am paying \"the\nperson/organisation which operates that machine behind the counter,\nright there\".\n\nIn many ways I'll miss the simplicity of BIP21 QR codes for\nface-to-face transactions - because in this use case the payment\nprotocol complicates (and in many cases weakens) the assurance that\nyou really are paying the entity that prepared the QR code.\n\nroy"}