{"type":"rich","version":"1.0","author_name":"npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrv","author_url":"https://nostr.ae/npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrv","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2012-11-27\n📝 Original message:On Monday 26 November 2012 22:37:31 Gavin Andresen wrote:\n\n\u003e x509chain: one or more DER-encoded X.509 certificates that identifies\n\u003e the merchant. See the \"Certificates\" section below for details.\n\nPersonally, I'd like to see fewer implicit ties to X509.  With X509 as one \noption.  For example, I'd much prefer to see a doorway to the future left open \nlike this:\n\n    message Invoice {\n        repeated bytes issuerIdentityType;\n        repeated bytes issuerIdentityBytes;\n\nor similar, instead of \"x509chain\".\n\nIn particular two additional identification types:\n\n - GnuPG (obviously)\n - Hash based\n\nThe hash-based system would be there as a method of leveraging an existing \ntrusted connection, without needing to get into the nitty-gritty of \ncertificates.  For example, I am paying for something on a web site; I \npresumably already have a secure connection that I trust to that site.  That \nsite can issue me an invoice (which is to be sent to the bitcoin client) _and_ \na hash of the certificate on the same page.\n\nI trust that hash because I received it over a secure connection from a \ntrusted source.  When my bitcoin client pops up with the received invoice, it \nshows me the hash of the invoice, and I can be sure that it is from the web \nsite I thought it was from.\n\nImagine I'm a (very) small business, I have two or three customers.  I want to \nemail one of my customers an invoice.  I don't want to have to get an X509 \ncertificate, and I don't necessarily know how.  However, I can ring my \ncustomer up and say \"I've generated an invoice with my bitcoin client, it is \nhashed A7DE-521X-9977.  Write that down and confirm it when you get my \ninvoice\".  Alternatively, I might attach a file called\ninvoice-A7DE-521X-9977.bitinv to a signed GnuPG email.  The receipient can \neasily confirm I sent it because the filename must match the contents and \nGnuPG protects against tampering.\n\n\n\n\nAndy\n\n-- \nDr Andy Parkins\nandyparkins at gmail.com"}