From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP-13
Date: Mon, 20 Feb 2012 09:18:37 -0500 [thread overview]
Message-ID: <201202200918.38484.luke@dashjr.org> (raw)
In-Reply-To: <3DA9C79B-D91D-48B2-9469-37BAA037FC50@ceptacle.com>
On Monday, February 20, 2012 6:17:01 AM Michael Grønager wrote:
> Just posted this on the wiki BIP-13 discussion - should I make it into a
> BIP of its own ?
If you must. However, BIP 13 has been pretty much undisputed, and only held
back by BIP 16/17 so far...
> The "version" portion of the address has so far been labeled "network id",
> and indicates from which network and which chain the address can be used
> for.
Where do you see this? It has always been "version" as far as I am aware, and
we discussed formalizing the details of the bits in it a few months back.
In any case, it was certainly originally intended as "version" as can be
observed in Satoshi's reference implementation.
next prev parent reply other threads:[~2012-02-20 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 11:17 [Bitcoin-development] BIP-13 Michael Grønager
2012-02-20 14:18 ` Luke-Jr [this message]
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
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=201202200918.38484.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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