From: "Luke-Jr" <luke@dashjr•org>
To: Pieter Wuille <pieter.wuille@cs•kuleuven.be>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Version bytes "2.0"
Date: Mon, 12 Dec 2011 16:02:11 -0500 [thread overview]
Message-ID: <201112121602.12806.luke@dashjr.org> (raw)
In-Reply-To: <20111212205559.GA16665@ulyssis.org>
On Monday, December 12, 2011 3:56:01 PM Pieter Wuille wrote:
> 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.
Or both: use this proposal for 20-byte base58 for now, and overhaul it in the
future (maybe when the block chain forks?).
> 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)
Looks good here.
> 12: mainnet private keys ('Q', 'R' or 'S', instead of 128, '5')
> 204: testnet private keys ('7', instead of 239, '8' and '9')
These are 32-byte, so have no reason IMO to follow the 20-byte proposal.
Since a lot of services are already using version 128 ('5') for bitcoin
private keys, and 128 is "reserved" in the 20-byte proposal, I think it's fair
to leave it alone (for now).
next prev parent reply other threads:[~2011-12-12 21:02 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
2011-12-12 21:02 ` Luke-Jr [this message]
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=201112121602.12806.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pieter.wuille@cs$(echo .)kuleuven.be \
/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