From: Pieter Wuille <pieter.wuille@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Version bytes "2.0"
Date: Mon, 12 Dec 2011 21:57:54 +0100 [thread overview]
Message-ID: <20111212205753.GB16665@ulyssis.org> (raw)
In-Reply-To: <20111212205559.GA16665@ulyssis.org>
It seems base58 is actually quite terrible for producing nice human-recognizable
addresses, even though base58 is specially intended for human usage. We'll just
have to deal with it, or completely overhaul it and move to a saner encoding.
Luke's proposal is somewhat more drastic than my original one, since it removes
the actual "version" notion from the version bytes, and changes testnet addresses.
However, I think it may be worth it. More data classes have been necessary
before, and new versions haven't. Furthermore, they are far more recognizable to
users, which is something that in particular for OP_EVAL addresses (script hashes)
will be a plus.
Therefore, I'm in favor of the proposal; the new versions would become:
0: mainnet pubkey hashes ('1', as before)
192: testnet pubnet hashes ('2', instead of 111, 'm' and 'n')
5: mainnet script hashes ('3'; for OP_EVAL)
196: testnet script hashes ('2', same as normal testnet addresses)
12: mainnet private keys ('Q', 'R' or 'S', instead of 128, '5')
204: testnet private keys ('7', instead of 239, '8' and '9')
Comments?
--
Pieter
next prev parent reply other threads:[~2011-12-12 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 21:10 Luke-Jr
2011-12-06 21:28 ` Luke-Jr
2011-12-10 18:16 ` Luke-Jr
[not found] ` <20111212205559.GA16665@ulyssis.org>
2011-12-12 20:57 ` Pieter Wuille [this message]
2011-12-12 21:02 ` Luke-Jr
2011-12-13 10:38 ` Mike Hearn
2011-12-13 10:56 ` Wladimir
2011-12-13 11:07 ` Mike Hearn
2011-12-13 11:15 ` Wladimir
2011-12-13 15:43 ` Luke-Jr
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=20111212205753.GB16665@ulyssis.org \
--to=pieter.wuille@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