{"type":"rich","version":"1.0","author_name":"npub13lftpp7g0zz6pjhvjhqqlka53e358xctk4c4fzr52yywt5cqhkvqe273cc","author_url":"https://nostr.ae/npub13lftpp7g0zz6pjhvjhqqlka53e358xctk4c4fzr52yywt5cqhkvqe273cc","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-09-12\n📝 Original message:On 12 Sep 2014, at 11:55 , bitcoin-development-request at lists.sourceforge.net wrote:\n\n\u003e The hash is meant to link the trust anchor (e.g. the QR code) to the\n\u003e payment request message in a secure way. This will solve the problem\n\u003e several apps are comparing address+amount fields as a workaround\n\u003e instead, preventing some advanced BIP70 usecases. When these apps read a\n\u003e matching hash, they need not compare any of the other fields.\n\nSounds like a good plan.\n\nDo you have a list (possibly incomplete) of apps that perform this kind of checking? We’re currently working with some parties in a supply chain to allow a consumer payment on a retail website to automatically pay supply chain parties, the way BIP70 allows with multiple outputs on a transaction. This behaviour would prohibit this use case.\n\n/Mark"}