Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WDgZR-00013o-Jj for bitcoin-development@lists.sourceforge.net; Wed, 12 Feb 2014 20:38:13 +0000 Received: from mail-pd0-f180.google.com ([209.85.192.180]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WDgZQ-00086M-C0 for bitcoin-development@lists.sourceforge.net; Wed, 12 Feb 2014 20:38:13 +0000 Received: by mail-pd0-f180.google.com with SMTP id x10so9435289pdj.25 for ; Wed, 12 Feb 2014 12:38:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5XNF7ndIamqZEB3xmbq7xKTzmZg2L25eYZtg3oECjtc=; b=HW+VXB7zUx/0wQfqoUdJBQUHnsUZvwOVbOWSa1/NTCFeDTPjPrlaHG0KVwtAXOQLG9 UzvJoW8Gz2lEpENMmqDEFbC3i9fJiLfBMZkJ5jEdpAoE2vRseByJ64r8ShCfzrUoYIo1 2VpTcVpB+MWVy0lic7IVipo+RWnYRbN+y8QFlcnaVCSwIDimmZ2fJCKw+JVqhYnAu2uA 7vLEjdWI+0IXuzygV17ef7E3INM6uOW/RUFrJwjyP2VSjQVIDUkUzbe4StVV6qsSZ4iU b58WZmEIWXoIzk0EBm9Y1eAw/fjpX5u1QQqYI8keO6BmpYz0VADq/Vsx2NaaUzzyOLrO Ei2w== X-Gm-Message-State: ALoCoQk0Zdvqhhfi52qfhIWZCsTRr6SM+Nv5zYroH5b9F+dXrMt4wnO9zlUwgfGxDfWxQvbWk6XF X-Received: by 10.66.197.164 with SMTP id iv4mr41734114pac.18.1392237486334; Wed, 12 Feb 2014 12:38:06 -0800 (PST) Received: from [192.168.127.144] (50-0-36-81.dsl.dynamic.sonic.net. [50.0.36.81]) by mx.google.com with ESMTPSA id js7sm66684211pbc.35.2014.02.12.12.38.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 12:38:05 -0800 (PST) Message-ID: <52FBD948.906@monetize.io> Date: Wed, 12 Feb 2014 12:27:52 -0800 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <20140210030048.GB31925@savin> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [209.85.192.180 listed in list.dnswl.org] X-Headers-End: 1WDgZQ-00086M-C0 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: Wed, 12 Feb 2014 20:38:13 -0000 On 02/12/2014 08:44 AM, Alan Reiner wrote: > Changing the protocol to use these static IDs is a pretty fundamental > change that would never happen in Bitcoin. But they can still be > useful at the application level to mitigate these issues. Not to mention that it would be potentially very insecure to have consensus depend on data (scriptSigs) which are not hashed in the Merkle structure of a block. Not that anyone on this list has suggested such a change, but I've seen it raised multiple times on the forum.... Mark