📅 Original date posted:2014-09-12
📝 Original message:On 09/12/2014 12:11 PM, Mark van Cuijk wrote:
> 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.
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.
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:25:40
in reply to nevent1q…vtu8
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:25:40Event JSON
{
"id": "ca3618c1cddefc4fe5c5096093c9469e6acc40bf11841154eff394a384a468a1",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686151540,
"kind": 1,
"tags": [
[
"e",
"5045235f447739204820462b94c541446b82ef26097d3889eeeed0767ae1d197",
"",
"root"
],
[
"e",
"96ab8f9f66a2aa35fb0cdbb08e41eb3591db5dfc07543e7171014c0a0df643ff",
"",
"reply"
],
[
"p",
"8fd2b087c87885a0caec95c00fdbb48e63439b0bb5715488745108e5d300bd98"
]
],
"content": "📅 Original date posted:2014-09-12\n📝 Original message:On 09/12/2014 12:11 PM, Mark van Cuijk wrote:\n\u003e On 12 Sep 2014, at 11:55 , bitcoin-development-request at lists.sourceforge.net wrote:\n\u003e \n\u003e\u003e The hash is meant to link the trust anchor (e.g. the QR code) to the\n\u003e\u003e payment request message in a secure way. This will solve the problem\n\u003e\u003e several apps are comparing address+amount fields as a workaround\n\u003e\u003e instead, preventing some advanced BIP70 usecases. When these apps read a\n\u003e\u003e matching hash, they need not compare any of the other fields.\n\u003e \n\u003e Sounds like a good plan.\n\u003e \n\u003e 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.\n\nHard to say, but here is my last assertion:\n\n- Bitcoin Wallet\n- Hive Bitcoin Wallet (checked by source)\n- countless (\u003e 300) forks/clones of Bitcoin Wallet\n\nSince you're planning an advanced BIP70 usecase, you'll also have to\ndeal with the many wallets that don't support BIP70 at all.",
"sig": "474c557449c7a5afdf03374822e11c7702c2c1a0339c8fcdb3cc945f6ba3171c146dae52dd8706dcd956dadc6f3fcd1ef4a8ead7fac5b5f70fdd757b4cba01ef"
}