From: shiva sitamraju <shiva@blockonomics•co>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] URI scheme with optional bech32 address
Date: Tue, 25 Sep 2018 12:29:48 +0530 [thread overview]
Message-ID: <CABuOfugx7+mM3doSCNL24J6yot7WNJZ9LP+8hkLAVpu0jDz9TA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
Hi,
I am not sure why this wasn't discussed more but it seemed like a very good
idea to me
https://www.reddit.com/r/Bitcoin/comments/9iivej/its_been_like_a_year_and_bech32_adoption_remains/
QR code is very important for network wide adoption. The problem is bech32
qr code isn't backward compatible and noone is going to show two QR codes.
Everyone is going safe with P2SH address qr code.
Example of proposed URI. I want not sure of technically best encoding, but
this is just for ideas
bitcoin:3BnsWZiTdYVrqiPh2RP3q9Y3ZqvhbCN2it?bech32=bc1q5u92yq20hss4rc99mfu23h4dxkxn4uuyqd5dzy
bitcoin:3BnsWZiTdYVrqiPh2RP3q9Y3ZqvhbCN2it?keyhash=a70aa2014fbc2151e0a5da78a8dead358d3af384
bitcoin:3BnsWZiTdYVrqiPh2RP3q9Y3ZqvhbCN2it?amount=0.123&bech32=bc1q5u92yq20hss4rc99mfu23h4dxkxn4uuyqd5dzy
As merchants/exchanges adopt this QR code, wallets that support bech32 can
chose to autopay to bech32 address (for lower tx fee). This can create a
network effect as more people start using bech32 and when we reach enough
wallet adoption, people can shift to just showing bech32 QR codes
--
Shiva S
CEO @ Blockonomics <https://www.blockonomics.co>
Decentralized and Permissionless Payments
Join us on Telegram <https://t.me/BlockonomicsCo>
View our Welcome Guide
<https://www.blockonomics.co/docs/blockonomics-brochure.pdf>
[-- Attachment #2: Type: text/html, Size: 1994 bytes --]
next reply other threads:[~2018-09-25 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 6:59 shiva sitamraju [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-24 12:05 Federico Tenga
2018-07-24 23:44 ` vv01f
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABuOfugx7+mM3doSCNL24J6yot7WNJZ9LP+8hkLAVpu0jDz9TA@mail.gmail.com \
--to=shiva@blockonomics$(echo .)co \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox