From: Sam Revitch <sam.revitch@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Password-protected private key export format and version bytes
Date: Wed, 17 Aug 2011 11:59:31 -0700 [thread overview]
Message-ID: <4E4C0F93.7000309@gmail.com> (raw)
In-Reply-To: <4E454C66.4010706@gmail.com>
Hello all,
The description of the password-protected export format has been revised
slightly, and now includes multiple algorithms and a parameter byte for
selecting the encryption parameters. As before, the thread is here:
https://bitcointalk.org/index.php?topic=36195.0
Unless there is an existing or other planned use for data class 32, or
another specific objection, I would like to use it for
password-protected private keys. Going by Sipa's description, this
would mean that a password-protected private key for bitcoin is type 32,
and for the testnet, type 79.
Thanks,
-Sam Revitch
prev parent reply other threads:[~2011-08-17 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 15:53 Sam Revitch
2011-08-17 18:59 ` Sam Revitch [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=4E4C0F93.7000309@gmail.com \
--to=sam.revitch@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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