From: Srintuar <srintuar@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP for segwit compatibility URIs
Date: Thu, 18 Oct 2018 19:58:54 -0400 [thread overview]
Message-ID: <CACUQsLJHaX3Wm_ukOFUXPa8dfbpur7_RDKbD=kspxh34+RGeaA@mail.gmail.com> (raw)
In-Reply-To: <CAHGSxGssNaVn_CAK252D_N8hzLFLnBFO8XPJLrCAHVw9+gCLWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
I was inclined towards the shortest possible encoding, even just a single
letter "a", mainly to reduce the amount of bytes required to form a QR
code.That said, "address" is more self-explanatory. Perhaps I will include
some sample QR code sizes for typical use cases, and see if it stays
reasonable.
As multiple keys of the same name would not be supported easily in many
wallets, a delimited is probably preferable.
I will update the BIP proposal and send it again.
[-- Attachment #2: Type: text/html, Size: 616 bytes --]
prev parent reply other threads:[~2018-10-18 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 19:52 Srintuar
2018-10-18 14:20 ` Clark Moody
2018-10-18 16:52 ` vv01f
2018-10-18 22:27 ` Clark Moody
2018-10-18 23:58 ` Srintuar [this message]
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='CACUQsLJHaX3Wm_ukOFUXPa8dfbpur7_RDKbD=kspxh34+RGeaA@mail.gmail.com' \
--to=srintuar@gmail$(echo .)com \
--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