📅 Original date posted:2014-01-27
📝 Original message:On 01/27/2014 06:11 PM, Jeremy Spilman wrote:
>> SCAN TO PAY
>> For scan-to-pay, the current landscape looks different. I assume at
>> least 50% of Bitcoin transactions are initiated by a BIP21 URL encoded
>> into a QR-code. Nevertheless, I tried to encode a payment request into
>> the bitcoin URL. I used my existing work on encoding transactions into
>> QR-codes. Steps to encode:
>
> Really interesting work. When using scan-to-pay, after the payer scans the
> QR code with the protobuf PaymentRequest (not a URL to download the
> PaymentRequest) are they using their own connectivity to submit the
> Payment response?
>
> How about putting a Bluetooth address in the payment_url inside the
> PaymentDetails message for the smartphone to send back the Payment
> response and get PaymentAck?
That's exactly what I have prototyped. I am putting a Bluetooth MAC
address into the payment_url. Have a look at the TAP TO PAY paragraph
for details, its mostly the same mechanism.
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:12:42
in reply to nevent1q…7g67
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:12:42Event JSON
{
"id": "f510b8f89c19e54bf297ea24a53f97c3b2d1a917f7f5afd4c4517c33f53d1a4c",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686150762,
"kind": 1,
"tags": [
[
"e",
"e58bd7fc71e0b34db5ffe731162734e74d81715bfe40046de10c0268ccbf9fd4",
"",
"root"
],
[
"e",
"0425efce8e00a25e5e011da08bfa4e3d3ff85470778721951b6b135e8ede2532",
"",
"reply"
],
[
"p",
"7e57666cff7c86f9410d33d4d34ef3e5105395b3c74af472541dbeeb743f9de3"
]
],
"content": "📅 Original date posted:2014-01-27\n📝 Original message:On 01/27/2014 06:11 PM, Jeremy Spilman wrote:\n\n\u003e\u003e SCAN TO PAY\n\u003e\u003e For scan-to-pay, the current landscape looks different. I assume at\n\u003e\u003e least 50% of Bitcoin transactions are initiated by a BIP21 URL encoded\n\u003e\u003e into a QR-code. Nevertheless, I tried to encode a payment request into\n\u003e\u003e the bitcoin URL. I used my existing work on encoding transactions into\n\u003e\u003e QR-codes. Steps to encode:\n\u003e \n\u003e Really interesting work. When using scan-to-pay, after the payer scans the \n\u003e QR code with the protobuf PaymentRequest (not a URL to download the \n\u003e PaymentRequest) are they using their own connectivity to submit the \n\u003e Payment response?\n\u003e\n\u003e How about putting a Bluetooth address in the payment_url inside the\n\u003e PaymentDetails message for the smartphone to send back the Payment\n\u003e response and get PaymentAck?\n\nThat's exactly what I have prototyped. I am putting a Bluetooth MAC\naddress into the payment_url. Have a look at the TAP TO PAY paragraph\nfor details, its mostly the same mechanism.",
"sig": "f0acbdb082a3237f506f05488d38065d8a1ac6c6470ba69bdd404a3b5d56521581ea8c21a214d3bacbfdd2b7cfa6676acd69be2fbd07554072ce2f3b003c23ee"
}