š
Original date posted:2012-10-02
š Original message:I agree we need a payment protocol, but instead of thinking of all of the
things we might possibly want I would like to solve a few boring problems
that we have right now.
Absolutely critical:
+ Bitcoin addresses by themselves are insecure against man-in-the-middle
attacks. We need a payment protocol so if you get a donation link for
"Bitcoin Foundation" in an email message and click on it you can be
reasonably certain that your coins will actually go to the Foundation and
not some hacker at your ISP that modified the email message.
+ After sending payment I should have a receipt that proves I followed the
payee's instructions, so if the payee says they never received the funds I
can prove that it wasn't my fault.
+ Protocol for gathering signatures from multiple devices
(extension/variation of the basic payment protocol, I think).
Not absolutely necessary, but I think v1 should have it anyway:
+ Where-to-send-refund information included with payments, so
overpayments/refunds can be handled efficiently and displayed intelligently
in the customer's wallet.
Everything else I think can wait.
--
--
Gavin Andresen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20121002/1d143bbc/attachment.html>;
Gavin Andresen [ARCHIVE] /
npub1s4ā¦d44kw
2023-06-07 10:33:43
in reply to nevent1qā¦t8kr
Author Public Key
npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kwSeen on
wss://relay.noswhere.comPublished at
2023-06-07 10:33:43Event JSON
{
"id": "e8e2dd5fb98c94c190f313aba7f778e6c9f711ffe04e86f7c6e9b583d176c639",
"pubkey": "857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4",
"created_at": 1686134023,
"kind": 1,
"tags": [
[
"e",
"ddab335ef46118e9900150c98bb33003e3b5c7be19fecd71839a92af65b3300e",
"",
"root"
],
[
"e",
"6dc2c96f4b4593a754b197bacbef0a63d7647adeaabd9d6accd4ebb1c678eed2",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "š
Original date posted:2012-10-02\nš Original message:I agree we need a payment protocol, but instead of thinking of all of the\nthings we might possibly want I would like to solve a few boring problems\nthat we have right now.\n\nAbsolutely critical:\n\n+ Bitcoin addresses by themselves are insecure against man-in-the-middle\nattacks. We need a payment protocol so if you get a donation link for\n\"Bitcoin Foundation\" in an email message and click on it you can be\nreasonably certain that your coins will actually go to the Foundation and\nnot some hacker at your ISP that modified the email message.\n\n+ After sending payment I should have a receipt that proves I followed the\npayee's instructions, so if the payee says they never received the funds I\ncan prove that it wasn't my fault.\n\n+ Protocol for gathering signatures from multiple devices\n(extension/variation of the basic payment protocol, I think).\n\nNot absolutely necessary, but I think v1 should have it anyway:\n\n+ Where-to-send-refund information included with payments, so\noverpayments/refunds can be handled efficiently and displayed intelligently\nin the customer's wallet.\n\n\nEverything else I think can wait.\n\n-- \n--\nGavin Andresen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20121002/1d143bbc/attachment.html\u003e",
"sig": "9a6cd1556f73afa068a5c2e12d212481ae1b1e712b89cd74ad9d86211000f814f9c68073b57cda4be5dcb53c6bf7d34bc3758580dda9f9666b41fe23252c380f"
}