From: Gavin Andresen <gavinandresen@gmail•com>
To: "Michael Grønager" <gronager@ceptacle•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP-13
Date: Wed, 22 Feb 2012 11:40:19 -0500 [thread overview]
Message-ID: <CABsx9T2tSK7mZ8+wQwCG08+1pudiOxsEqeA=uVYtYNYu0nhFLA@mail.gmail.com> (raw)
In-Reply-To: <F78AEBDF-F314-4245-B453-8D23C709D226@ceptacle.com>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
>
> However, the definitions en base58.h are:
>
> PUBKEY_ADDRESS = 0, (00000000)
> SCRIPT_ADDRESS = 5, (00000101)
> PUBKEY_ADDRESS_TEST = 111, (01101111) !!!
> SCRIPT_ADDRESS_TEST = 196, (11000100) !!!
>
> [as a side note litecoin is 48 (00110000) and namecoin is 52 (00110100)]
>
> So there is no logic ?? I have searched the mailing list and the forum for
> discussions on this but found it hard to find any. If I overlooked
> something please direct me.
>
PUBKEY_ADDRESS_TEST is/was supposed to change (the logic for it being 111
was "eleven is Gavin's favorite number"), but I have higher priority things
to do than make all the necessary code changes to upgrade testnet wallets
(unfortunately the address:account mappings in the wallet store the address
base58-encoded) and the testnet faucet and get theymos to change the
blockexplorer.com/testnet site to change the version number and publicize
the change so anybody else who has created testnet infrastructure changes.
If you'd like to spearhead that effort, be my guest, but it is not as
trivial as just changing the definition.
Luke can explain why SCRIPT_ADDRESS_TEST is 196, my memory is fuzzy about
that (it always decodes to the same digit in base58 maye?)
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 1618 bytes --]
next prev parent reply other threads:[~2012-02-22 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 11:17 Michael Grønager
2012-02-20 14:18 ` Luke-Jr
2012-02-20 15:47 ` Michael Grønager
2012-02-20 17:17 ` Gavin Andresen
2012-02-20 21:29 ` Michael Grønager
2012-02-22 16:29 ` Michael Grønager
2012-02-22 16:40 ` Gavin Andresen [this message]
2012-02-22 16: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='CABsx9T2tSK7mZ8+wQwCG08+1pudiOxsEqeA=uVYtYNYu0nhFLA@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gronager@ceptacle$(echo .)com \
/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