From: Mike Caldwell <mcaldwell@swipeclock.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] BIP 38
Date: Fri, 25 Oct 2013 14:50:10 -0400 [thread overview]
Message-ID: <B09A5DE3EF411243BB3328232CD25A5D998989775B@MAILR023.mail.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
Hey everyone,
I have noticed that there was a recent change to BIP 0038 (Password-Protected Private Key) on the Wiki, which is a proposal I wrote in late 2012. Gregory, it looks to me as though you have made this change, and I'm hoping for your help here. The change suggests that the number was never assigned, and that there has been no discussion regarding the proposal on this list.
I had this number assigned by Amir Taaki in November of 2012, consistent with what I understood the procedure to be at the time by reading BIP 0001 on the Wiki.
First off, I want to confirm that when I send to the list, that there isn't a technical reason it's not getting to everybody. I believe I most recently mentioned BIP 38 to this list on August 17, 2013. (EDIT: seems my prior messages, including an earlier revision of this message, have not made it to the list)
Secondly, in the case that it is deemed that this has never been properly submitted, discussed, or pushed forward, I'd like to propose that this happen, and request help with the formalities where I'm lacking.
I believe BIP 38 is a valuable proposal that is seeing real-world use. BIP 38 allows people to create private keys (including paper wallets) protected by a password, and also allows one party to select the password for paper wallets to be created by another party.
Real-world use includes a working implementation at BitAddress.org, one at Bit2Factor.org, implementation by Mycelium, and others. Also, others are informally using it as a sort of abbreviated escrow scheme where a buyer and seller agree on the buyer maintaining control over the release of funds. In short, it would be terribly confusing to reassign the number BIP 38 after already having had an established meaning for the better part of the year, particularly on what appears to be procedural grounds.
Mike
[-- Attachment #2: Type: text/html, Size: 3998 bytes --]
next reply other threads:[~2013-10-25 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 18:50 Mike Caldwell [this message]
2013-10-25 20:05 ` [Bitcoin-development] BIP 38 Gregory Maxwell
2013-10-25 20:46 ` Mike Caldwell
2013-11-08 15:41 ` Wladimir
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=B09A5DE3EF411243BB3328232CD25A5D998989775B@MAILR023.mail.lan \
--to=mcaldwell@swipeclock.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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