From mboxrd@z Thu Jan 1 00:00:00 1970 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 <marek@palatinus.cz>) id 1UFqxl-0002K6-UE for bitcoin-development@lists.sourceforge.net; Wed, 13 Mar 2013 19:03:45 +0000 X-ACL-Warn: Received: from mail-ve0-f172.google.com ([209.85.128.172]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UFqxk-0004e7-Lo for bitcoin-development@lists.sourceforge.net; Wed, 13 Mar 2013 19:03:45 +0000 Received: by mail-ve0-f172.google.com with SMTP id cz11so1060320veb.3 for <bitcoin-development@lists.sourceforge.net>; Wed, 13 Mar 2013 12:03:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=fDgZJEMP31Jof68pyauaYkhlaNkR/BotAF4Tlauag8I=; b=eAMFKllWMPSUr2kf32RUhoI+rDOOSLUA4qWh9IwUCDZgaKN8zMeGD2ovMeHQ7RUiRH S6ZLL9vjg/T/Za3zgyDLMTWOkCYsO4PhFP2SPka1CIrilfXAmuZttMM2hzykni9Qi2OD itYHniBPupv6XZ4Hf39kJ0uwzMY2p6LramAWrgaLWGL54St8D620xr9HYKURl+INWY2G Frg8USd3l3DEwtTGS6L0Pw0MFucL/wsqTesR5Rm5BZuEzV6uI1t4Natd8QKfltW3KIg+ vEv6QDBnbzsTufaoT3R3F1q3l8jmRFpPWo12os8Gt8LhEcm18VYD4SGhUJgzBH0Kpywm 0Ikw== X-Received: by 10.58.253.161 with SMTP id ab1mr8717111ved.55.1363199741843; Wed, 13 Mar 2013 11:35:41 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.58.151.73 with HTTP; Wed, 13 Mar 2013 11:35:11 -0700 (PDT) In-Reply-To: <CACh7GpG_4uLUUiwJyZO0FtV2_UHMN-HnJsZZXWpC2jQvzb-jMQ@mail.gmail.com> References: <201303131256.30144.luke@dashjr.org> <CACh7GpE09hqCPL6rtdC6EZzohM5QHb+0SdFoD8MzPSqf7=6hOA@mail.gmail.com> <20130313175825.GA21242@vps7135.xlshosting.net> <CACh7GpG_4uLUUiwJyZO0FtV2_UHMN-HnJsZZXWpC2jQvzb-jMQ@mail.gmail.com> From: slush <slush@centrum.cz> Date: Wed, 13 Mar 2013 19:35:11 +0100 X-Google-Sender-Auth: q02509CuF8bkJ7wG21p3fGDo_vI Message-ID: <CAJna-HjufEdY77uQT13=8Z18wo4jcvLcy093BAk=mXMa7hhRSg@mail.gmail.com> To: Mark Friedenbach <mark@monetize.io> Content-Type: multipart/alternative; boundary=047d7bdc9c105ef88e04d7d2ac08 X-Gm-Message-State: ALoCoQl4Imk8mT5NX+QDV+ClxXLagJBoLjvTXYgKQducr0d7KQfM5S2R1ukApusNTSinR1CZ/1J7 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slush[at]centrum.cz) 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1UFqxk-0004e7-Lo Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] 0.8.1 ideas X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Wed, 13 Mar 2013 19:03:46 -0000 --047d7bdc9c105ef88e04d7d2ac08 Content-Type: text/plain; charset=ISO-8859-1 Agree. I quite like Mark's proposal. Yes, formally it is hard fork. But the step 4) can come very far in the future, when the penetration of <0.8 clients will be mininimal. slush On Wed, Mar 13, 2013 at 7:27 PM, Mark Friedenbach <mark@monetize.io> wrote: > This problem is very clearly a *bug* in the old codebase. So let's be > forward thinking and do what we would do in any other situation: fix the > bug, responsibly notify people and give them time to react, then move on. > Let's not codify the bug in the protocol. > --047d7bdc9c105ef88e04d7d2ac08 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Agree. I quite like Mark's proposal. Yes, formally it is hard fork. But= the step 4) can come very far in the future, when the penetration of <0= .8 clients will be mininimal.<div><br></div><div>slush<br><br><div class=3D= "gmail_quote"> On Wed, Mar 13, 2013 at 7:27 PM, Mark Friedenbach <span dir=3D"ltr"><<a = href=3D"mailto:mark@monetize.io" target=3D"_blank">mark@monetize.io</a>>= </span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .= 8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir=3D"ltr"><div>This problem is very clearly a *bug* in the old codeb= ase. So let's be forward thinking and do what we would do in any other = situation: fix the bug, responsibly notify people and give them time to rea= ct, then move on. Let's not codify the bug in the protocol.<span class= =3D"HOEnZb"><font color=3D"#888888"><br> </font></span></div></div></blockquote></div></div> --047d7bdc9c105ef88e04d7d2ac08--