📅 Original date posted:2012-11-27
📝 Original message:>
> The SignedReceipt message is useful in the sense that it shows
> confirmation by the merchant, but if you don't get one, you can still
> prove you paid the invoice. So from this perspective perhaps
> SignedReceipt should be renamed to Acceptance or something like that,
> and then the spec should call out that a signed invoice plus accepted
> Bitcoin transactions is mathematically a proof of purchase.
Which is why I find the "SignedReceipt" somewhat superfluous. If you implement a payment system, like bit-pay/wallet you are likely to double that through some sort of e-mail receipt anyway.
Further, the inclusion of x509 is not really needed in the spec - you don't need to sign the invoice with an x509, you can use the payment key. The proof would still be equally binding, and valid also for non holders of x509 (server) certificates (like normal people).
Finally, host certificates does not normally keep in their "purpose" S/MIME Signing. So you are bending the intended use of the x509 certificate anyway.
/M
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Michael Gronager [ARCHIVE] /
npub1nc…gw452
2023-06-07 10:40:54
in reply to nevent1q…290w
Author Public Key
npub1nc78dlt7hp3v5dl32qu3m678h2j0ss374glcjnz8df75xcx7ngpq4gw452Published at
2023-06-07 10:40:54Event JSON
{
"id": "9644741c5d61b2ae41979791f2f7c1392d8f655fe21845c8b93a1c0225f4130e",
"pubkey": "9e3c76fd7eb862ca37f150391debc7baa4f8423eaa3f894c476a7d4360de9a02",
"created_at": 1686134454,
"kind": 1,
"tags": [
[
"e",
"f5f2400f8aa8a7067be3d080f096fd7cbfeecdd6e589c178b85b63a9338150a5",
"",
"root"
],
[
"e",
"db5270427675ec77dd44b72d5f2eefb074ec210b4b0eae9a4460afbce0027888",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2012-11-27\n📝 Original message:\u003e \n\u003e The SignedReceipt message is useful in the sense that it shows\n\u003e confirmation by the merchant, but if you don't get one, you can still\n\u003e prove you paid the invoice. So from this perspective perhaps\n\u003e SignedReceipt should be renamed to Acceptance or something like that,\n\u003e and then the spec should call out that a signed invoice plus accepted\n\u003e Bitcoin transactions is mathematically a proof of purchase.\n\nWhich is why I find the \"SignedReceipt\" somewhat superfluous. If you implement a payment system, like bit-pay/wallet you are likely to double that through some sort of e-mail receipt anyway.\n\nFurther, the inclusion of x509 is not really needed in the spec - you don't need to sign the invoice with an x509, you can use the payment key. The proof would still be equally binding, and valid also for non holders of x509 (server) certificates (like normal people).\nFinally, host certificates does not normally keep in their \"purpose\" S/MIME Signing. So you are bending the intended use of the x509 certificate anyway.\n\n/M\n\n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Monitor your physical, virtual and cloud infrastructure from a single\n\u003e web console. Get in-depth insight into apps, servers, databases, vmware,\n\u003e SAP, cloud infrastructure, etc. Download 30-day Free Trial.\n\u003e Pricing starts from $795 for 25 servers or applications!\n\u003e http://p.sf.net/sfu/zoho_dev2dev_nov\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "2e5d2ac2873d138f7af02e500d894964fa5d31003415b9e4703d409759d607e7eab8148cf8725b9188d49cabc1a2ceb217be00772dcda3e303fba490a71688b6"
}