📅 Original date posted:2018-01-02 📝 Original message:On Mon, Jan 1, 2018 at ...

Ryan Grant [ARCHIVE] /

npub19a2…mwcl

2023-06-07 18:09:11

in reply to nevent1q…s7em

📅 Original date posted:2018-01-02
📝 Original message:On Mon, Jan 1, 2018 at 1:50 PM, James Hilliard via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> I propose that we move the BIP70 protocol implementation into a
> browser extension that can communicate with wallets over a simple IPC
> mechanism [...]

As a reminder, there is a W3C Payments API, currently proceeding along
the W3C Recommendation track, which registers "payment handlers" in
the browser, and selects one to complete a transaction:

https://w3c.github.io/payment-handler/

The purpose of the payments API is to automate all data entry and
handle choices related to common transactions on the Web. Payment
requests will often ask for information that Bitcoin wallets have no
current need to provide, such as a shipping address. If shipping
options or other personally identifying information (such as an email
address and a return payment address) are involved, then it is the
chosen payment type's *handler* that is tasked with negotiating with
the user how to reveal the supposedly necessary information.

https://www.w3.org/TR/payment-request/#the-options-argument

Although it may seem early for wallet makers to consider integration
with a mere W3C Recommendation, it would not be early to choose the
right architecture to build code on, given that this is in the works
for the major browsers. Development can proceed even in browsers that
have not implemented anything, through an HTML5 Javascript polyfill.
A demonstration which includes payment in bitcoins is already
available, although it leaves as an exercise for the reader exactly
how the txid would be made known to the handler (whether manually
input by paste buffer after copying from an external app, or returned
through IPC):

https://web-payments.io/
https://github.com/digitalbazaar/payment-handler-polyfill

>From my brief inspection: not bad. I don't see anything in this spec
that would preclude the workflow of a Bitcoin transaction, whether
on-chain (with the seller's backend marking off confirmations) or
using the Lightning Network. It even allows the seller to offer a
discount on certain payment methods:

https://www.w3.org/TR/payment-request/#dom-paymentdetailsmodifier

Author Public Key

npub19a2m7qm80t7mzhgqfgunswhm5c3q4fkqt89057ugy7u8jdxncf2q06mwcl

Show more details

Published at

2023-06-07 18:09:11

Kind type

1 Short Text Note

Event JSON

{ "id": "57ad204c16b18341c79db2f7efcb6a36ca980a4295ef4465cbe6707a2f8254b0", "pubkey": "2f55bf03677afdb15d004a39383afba6220aa6c059cafa7b8827b87934d3c254", "created_at": 1686161351, "kind": 1, "tags": [ [ "e", "662531daf1604e88b3b1837ace53291dc7f6e8db933d10fca54ffd94364e49b5", "", "root" ], [ "e", "bd6453edf00db1c51d75b141eedb54bc50b90ae363a2f81f2a6907e5706a9b71", "", "reply" ], [ "p", "78cadd65bb98ff2b50ae825fa100352d7f102e41ec5caad2e4d2e99e00df1394" ] ], "content": "📅 Original date posted:2018-01-02\n📝 Original message:On Mon, Jan 1, 2018 at 1:50 PM, James Hilliard via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e I propose that we move the BIP70 protocol implementation into a\n\u003e browser extension that can communicate with wallets over a simple IPC\n\u003e mechanism [...]\n\nAs a reminder, there is a W3C Payments API, currently proceeding along\nthe W3C Recommendation track, which registers \"payment handlers\" in\nthe browser, and selects one to complete a transaction:\n\n https://w3c.github.io/payment-handler/\n\nThe purpose of the payments API is to automate all data entry and\nhandle choices related to common transactions on the Web. Payment\nrequests will often ask for information that Bitcoin wallets have no\ncurrent need to provide, such as a shipping address. If shipping\noptions or other personally identifying information (such as an email\naddress and a return payment address) are involved, then it is the\nchosen payment type's *handler* that is tasked with negotiating with\nthe user how to reveal the supposedly necessary information.\n\n https://www.w3.org/TR/payment-request/#the-options-argument\n\nAlthough it may seem early for wallet makers to consider integration\nwith a mere W3C Recommendation, it would not be early to choose the\nright architecture to build code on, given that this is in the works\nfor the major browsers. Development can proceed even in browsers that\nhave not implemented anything, through an HTML5 Javascript polyfill.\nA demonstration which includes payment in bitcoins is already\navailable, although it leaves as an exercise for the reader exactly\nhow the txid would be made known to the handler (whether manually\ninput by paste buffer after copying from an external app, or returned\nthrough IPC):\n\n https://web-payments.io/\n https://github.com/digitalbazaar/payment-handler-polyfill\n\n\u003eFrom my brief inspection: not bad. I don't see anything in this spec\nthat would preclude the workflow of a Bitcoin transaction, whether\non-chain (with the seller's backend marking off confirmations) or\nusing the Lightning Network. It even allows the seller to offer a\ndiscount on certain payment methods:\n\n https://www.w3.org/TR/payment-request/#dom-paymentdetailsmodifier", "sig": "c6a116cc27330cc1449cd1d5c1a718c4fbe864bafd53c090512ad913e057702292bf5383b87c1e4c39524c4be9c9a445a4a452d89ee4f5cafc2db5fa77727479" }