Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qf6GX-0007lu-PI for bitcoin-development@lists.sourceforge.net; Fri, 08 Jul 2011 08:18:25 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=witchspace81@gmail.com; helo=mail-gx0-f175.google.com; Received: from mail-gx0-f175.google.com ([209.85.161.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Qf6GW-0005rq-Tm for bitcoin-development@lists.sourceforge.net; Fri, 08 Jul 2011 08:18:25 +0000 Received: by gxk3 with SMTP id 3so911046gxk.34 for ; Fri, 08 Jul 2011 01:18:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.8.21 with SMTP id l21mr1690831ybi.186.1310113099541; Fri, 08 Jul 2011 01:18:19 -0700 (PDT) Received: by 10.151.150.15 with HTTP; Fri, 8 Jul 2011 01:18:19 -0700 (PDT) In-Reply-To: References: <20110707111557.GA5231@ulyssis.org> <4E16A567.6020309@justmoon.de> Date: Fri, 8 Jul 2011 08:18:19 +0000 Message-ID: From: John Smith To: Stefan Thomas Content-Type: multipart/alternative; boundary=000e0cd514cce9ebec04a78a795f X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (witchspace81[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (witchspace81[at]gmail.com) 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Qf6GW-0005rq-Tm Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Version bytes X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2011 08:18:25 -0000 --000e0cd514cce9ebec04a78a795f Content-Type: text/plain; charset=ISO-8859-1 Sorry, that last message got broken off. On Fri, Jul 8, 2011 at 6:36 AM, Stefan Thomas wrote: > >> Hey Pieter, >> >> > Otherwise, we could reset testnet (not actually reset, just >> > change its addresses a bit), and simply state odd=testnet, even=realnet. >> >> We could use the XOR hack for now and remove it the next time we reset >> testnet. But I do think the 111 is baggage we want to get rid of. Using >> the lsb as a simple flag is much cleaner. >> > I agree it is cleaner, but I think breaking compatiblity with older address (even testnet) is not a good idea right now. It is important to build an image of stability and backward compatibility. So I vote for the XOR 111 hack :) JS --000e0cd514cce9ebec04a78a795f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sorry, that last message got broken off.

On Fri, Jul 8, 2011 at 6:36 AM, Stefan T= homas <moon@justmoon.de> wrote:
Hey Pieter,

> Otherwise, we could reset testnet (not actually reset, just
> change its addresses a bit), and simply state odd=3Dtestnet, even=3Dre= alnet.

We could use the XOR hack for now and remove it the next time we rese= t
testnet. But I do think the 111 is baggage we want to get rid of. Using
the lsb as a simple flag is much cleaner.


I agree it is cleaner, but I think breaking compatiblity with older address= (even testnet) is not a good idea right now. It is important to build an i= mage of stability and backward compatibility.

So I vote for the XOR = 111 hack :)

JS

--000e0cd514cce9ebec04a78a795f--