On 02/23/2015 04:09 PM, Jan Vornberger wrote:
I'm still concerned that the fact, that Bluetooth is often disabled, is a
problem for the UX. And it's not just a one-time thing as with NFC,
which is - in my experience - also often disabled, but then people turn
it on and leave it on.
It's the
Yeah, you'd be limited to simple usecases. X509 signing or lots of
outputs will make the QR code hard to scan. However, if all you want to
do is send to a custom script (without using P2SH) I invite you to have
a look at
Thanks for references. Yeah, I don't need X509 signing (if I could use
certificates, I wouldn't need to include PR in the URL in the first place).
I presume you used BITCOIN:-payment request instead of
bitcoin:?r=somescheme://payment request to make it more compact.
I also tried to look up
Base43 is the same as any BaseX standard, but using a different alphabet
(43 characters). It's meant to be used for efficiently storing binary
data into QR codes. The alphabet is picked to match the 'Alphanumeric'
input mode of QR codes as closely as possible, but at the same time be
allowed
On 02/26/2015 12:14 PM, Oleg Andreev wrote:
Base43 is the same as any BaseX standard, but using a different alphabet
(43 characters). It's meant to be used for efficiently storing binary
data into QR codes. The alphabet is picked to match the 'Alphanumeric'
input mode of QR codes as closely
On 02/24/2015 11:41 AM, Mike Hearn wrote:
Does this not also require the BT publication of the script for a P2SH
address?
You mean if the URI you're serving is like this?
bitcoin:3aBcD?bt=
Yes it would. I guess then, the server would indicate both the script,
6 matches
Mail list logo
