{"type":"rich","version":"1.0","author_name":"npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","author_url":"https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-09-12\n📝 Original message:This is the discussion post corresponding to this PR:\nhttps://github.com/bitcoin/bips/pull/106\n\n\"Amend BIP72 by an \"h\" parameter, which contains a hash of the\nPaymentRequest message that is fetched via the \"r\" parameter.\n\nThe hash is meant to link the trust anchor (e.g. the QR code) to the\npayment request message in a secure way. This will solve the problem\nseveral apps are comparing address+amount fields as a workaround\ninstead, preventing some advanced BIP70 usecases. When these apps read a\nmatching hash, they need not compare any of the other fields.\n\nThanks to Julian Haight for helping with the standard.\""}