rich1.0npub13lftpp7g0zz6pjhvjhqqlka53e358xctk4c4fzr52yywt5cqhkvqe273cchttps://nostr.ae/npub13lftpp7g0zz6pjhvjhqqlka53e358xctk4c4fzr52yywt5cqhkvqe273ccnjumphttps://nostr.aeπ
Original date posted:2014-09-12
π Original message:On 12 Sep 2014, at 11:55 , bitcoin-development-request at lists.sourceforge.net wrote:
> The hash is meant to link the trust anchor (e.g. the QR code) to the
> payment request message in a secure way. This will solve the problem
> several apps are comparing address+amount fields as a workaround
> instead, preventing some advanced BIP70 usecases. When these apps read a
> matching hash, they need not compare any of the other fields.
Sounds like a good plan.
Do 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.
/Mark