On 09/12/2014 12:11 PM, Mark van Cuijk wrote: > On 12 Sep 2014, at 11:55 , bitcoin-development-requ...@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.
Hard to say, but here is my last assertion: - Bitcoin Wallet - Hive Bitcoin Wallet (checked by source) - countless (> 300) forks/clones of Bitcoin Wallet Since you're planning an advanced BIP70 usecase, you'll also have to deal with the many wallets that don't support BIP70 at all. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
