From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 32 HD wallets, accounts should be labels not numbers
Date: Mon, 3 Dec 2012 06:48:34 -0800 (PST) [thread overview]
Message-ID: <1354546114.71509.YahooMailNeo@web121006.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CAPg+sBgU=1Z1KaGXk0xY1mzEZKVRPd7T06X_zcTUd_d4JUsWtw@mail.gmail.com>
ok, also what is the reasoning behind serialising points using a compressed format before going into the hash function? I'm looking at the sec1-v2.pdf and the compression format is a little confusing.
I think the octet string for X is 32 bytes (using q = curve.order) and secp256k1 is a prime field so we follow step 2.2.1
________________________________
From: Pieter Wuille <pieter.wuille@gmail•com>
To: Amir Taaki <zgenjix@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net" <bitcoin-development@lists•sourceforge.net>
Sent: Monday, December 3, 2012 2:54 PM
Subject: Re: [Bitcoin-development] BIP 32 HD wallets, accounts should be labels not numbers
On Mon, Dec 3, 2012 at 2:49 PM, Amir Taaki <zgenjix@yahoo•com> wrote:
Can this be amended? I think it makes much more sense to allow people to input labels not numbers at this level.
>
>General category names for different accounts is much more human than numbers, and you can still use incrementing numbers if you prefer.
>
There is no way to iterate over all strings. The intention is that a wallet application can detect a new account that becomes in use (e.g. during disaster recovery), so the accounts get assigned incrementing numbers.
I wouldn't mind adding the ability to do "non-standard derivations" using arbitrary strings, if this recoverability property is not desired.
--
Pieter
next prev parent reply other threads:[~2012-12-03 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 13:49 Amir Taaki
2012-12-03 13:54 ` Pieter Wuille
2012-12-03 14:48 ` Amir Taaki [this message]
2012-12-03 20:44 ` Pieter Wuille
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=1354546114.71509.YahooMailNeo@web121006.mail.ne1.yahoo.com \
--to=zgenjix@yahoo$(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