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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YljkU-0002OD-Ue for bitcoin-development@lists.sourceforge.net; Fri, 24 Apr 2015 19:58:54 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.172 as permitted sender) client-ip=209.85.220.172; envelope-from=swansontec@gmail.com; helo=mail-qk0-f172.google.com; Received: from mail-qk0-f172.google.com ([209.85.220.172]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YljkQ-0004Xj-Fc for bitcoin-development@lists.sourceforge.net; Fri, 24 Apr 2015 19:58:54 +0000 Received: by qku63 with SMTP id 63so36805968qku.3 for ; Fri, 24 Apr 2015 12:58:45 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.134.148 with SMTP id 142mr108916qhg.100.1429905525117; Fri, 24 Apr 2015 12:58:45 -0700 (PDT) Received: by 10.140.149.215 with HTTP; Fri, 24 Apr 2015 12:58:45 -0700 (PDT) In-Reply-To: <552FDF73.6010104@sky-ip.org> References: <552EF785.7000207@sky-ip.org> <552FDF73.6010104@sky-ip.org> Date: Fri, 24 Apr 2015 12:58:45 -0700 Message-ID: From: William Swanson To: s7r@sky-ip.org Content-Type: text/plain; charset=UTF-8 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 (swansontec[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: 1YljkQ-0004Xj-Fc Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] 75%/95% threshold for transaction versions 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, 24 Apr 2015 19:58:55 -0000 On Thu, Apr 16, 2015 at 9:12 AM, s7r wrote: > Thanks for your reply. I agree. Allen has a good point in the previous > email too, so the suggestion might not fix anything and complicate things. The BIP 62 approach to malleability isn't the only option. Another approach is to sign the transaction in such a way that the input txid's are allowed to change without invalidating the signatures. That way, if malleability happens, you just adjust you transaction to match and re-broadcast. That proposal is here: https://github.com/scmorse/bitcoin-misc/blob/master/sighash_proposal.md The "Build your own nHashType" thread on this mailing list contains the discussion. I personally prefer this solution, since it nails the problem completely with one simple and obvious change. The BIP 62 approach is more like a game of wac-a-mole. -William