{"type":"rich","version":"1.0","author_name":"npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","author_url":"https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2012-11-28\n📝 Original message:RE: Changing SignedInvoice's invoice field to 'bytes serialized_invoice':\n\nGood Idea, I agree it will avoid potential issues. I think it then\nmakes sense to pull the pki_type and pki_data into SignedInvoice, too,\nand specify that the signature is on the SHA256-HMAC of pki_type,\npki_data, and serialized_invoice (being careful to combine them in a\nway that is secure).\n\nRE: Changing Payment to include just merchant_data and not the entire Invoice:\n\nAgreed, good idea.\n\n\nRE: Mr. Stanish's suggestion to punt all of this and wait for a Grand\nUnified Solution:\n\nNo, we have problems that need a solution right now. And, having\nwritten one (I was the lead author of the ISO/IEC 14772-1\ninternational standard) I'm very pessimistic about your chances for\nanything like IFEX to actually be adopted.\n\n-- \n--\nGavin Andresen"}