Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WGUk3-0007ux-46 for bitcoin-development@lists.sourceforge.net; Thu, 20 Feb 2014 14:36:47 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.180 as permitted sender) client-ip=209.85.217.180; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f180.google.com; Received: from mail-lb0-f180.google.com ([209.85.217.180]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WGUk2-00037Q-Be for bitcoin-development@lists.sourceforge.net; Thu, 20 Feb 2014 14:36:47 +0000 Received: by mail-lb0-f180.google.com with SMTP id n15so1345453lbi.25 for ; Thu, 20 Feb 2014 06:36:39 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.228.172 with SMTP id sj12mr1423500lac.32.1392906999715; Thu, 20 Feb 2014 06:36:39 -0800 (PST) Received: by 10.112.189.164 with HTTP; Thu, 20 Feb 2014 06:36:39 -0800 (PST) In-Reply-To: References: <52FBD948.906@monetize.io> <201402122252.31060.luke@dashjr.org> <601EE159-9022-4ADF-80AC-7E1C39E86A65@mac.com> <81A62AB7-9EC6-439E-96CF-F064F0151BB9@mac.com> Date: Thu, 20 Feb 2014 06:36:39 -0800 Message-ID: From: Gregory Maxwell To: Gavin Andresen Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) 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 (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1WGUk2-00037Q-Be Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] [RFC] [BIP proposal] Dealing with malleability 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: Thu, 20 Feb 2014 14:36:47 -0000 On Thu, Feb 20, 2014 at 6:29 AM, Gavin Andresen w= rote: > I think we should get Pieter's proposal done and implemented quickly. I > agree with Mike, it doesn't have to take a long time for the core network= to > fully support this. > > Getting wallets to start generating transaction.version=3D3 might take ye= ars, > but that is OK. Sure I'm all for doing what Pieter suggested=E2=80=94 it's basically the pl= an we've been executing for some time already but with the version check to make it sane to complete. My reserved sounding comments were relative to the proposals to do things with nversion=3D1 transactions, frankly I think thats completely insane. Though while we're on the subject of reservations, I am far from confident that we've uncovered all the possible malleability routes=E2=80=94 that list gained a new, never before discussed entry, when Pieter was writing it a couple weeks ago. We also have no proof of the absence of further algebraic malleability in DSA (though I think its somewhat unlikely, a solid proof of it has been somewhat elusive).