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. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
