<oembed><type>rich</type><version>1.0</version><author_name>npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_name><author_url>https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-09-12&#xA;📝 Original message:This is the discussion post corresponding to this PR:&#xA;https://github.com/bitcoin/bips/pull/106&#xA;&#xA;&#34;Amend BIP72 by an &#34;h&#34; parameter, which contains a hash of the&#xA;PaymentRequest message that is fetched via the &#34;r&#34; parameter.&#xA;&#xA;The hash is meant to link the trust anchor (e.g. the QR code) to the&#xA;payment request message in a secure way. This will solve the problem&#xA;several apps are comparing address+amount fields as a workaround&#xA;instead, preventing some advanced BIP70 usecases. When these apps read a&#xA;matching hash, they need not compare any of the other fields.&#xA;&#xA;Thanks to Julian Haight for helping with the standard.&#34;</html></oembed>