Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YEfaF-000761-Ft for bitcoin-development@lists.sourceforge.net; Fri, 23 Jan 2015 14:51:39 +0000 X-ACL-Warn: Received: from mail-ie0-f169.google.com ([209.85.223.169]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YEfaD-00007z-OA for bitcoin-development@lists.sourceforge.net; Fri, 23 Jan 2015 14:51:39 +0000 Received: by mail-ie0-f169.google.com with SMTP id rl12so7508324iec.0 for ; Fri, 23 Jan 2015 06:51:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:content-type; bh=391yEPXpUg+lXv5Flx8g3KN4B/9ZjcUybZFu8fiZaqA=; b=A7wvmtsz+ySChpG/Xm2IVtsIy7xhQLF5QJGOYFkKoORC67hs/+BioutUj1uVCXNYNg 1RA1qUcb0CtmgieBtOpEiOmrwDMsnQR9NhX/bR3ljlTWKJDHkrW1Jh6aIvVDJ/Bve8K7 p6/DwCmvcIdzec8Q7yuiB17u6ZzFJpi0n1rg5Ke6+uI1MClUAl4+o+Q3mhyDonywfMSA 5n4o+w4O+vf+7buu5wfGnl9X2A4jL0LmVR43HykZbDjHBQMiOz2kdSZ3H6xHjnQLKOBd YMZmr/57/c/xZ671jNRBWUF5QBmpiwcUXJuUZFd5jllHiTf+gjycnv4lVF+aoPTZe0Bf Qspg== X-Gm-Message-State: ALoCoQk87G52vwCbYAhOOJ5aVaYnO6j+JdmEvyEiVr7XZ3UsnCuUgMji4U9K1ga6Gmgf4rD495B2 X-Received: by 10.50.30.202 with SMTP id u10mr2204326igh.35.1422024692453; Fri, 23 Jan 2015 06:51:32 -0800 (PST) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.64.31.138 with HTTP; Fri, 23 Jan 2015 06:51:02 -0800 (PST) From: slush Date: Fri, 23 Jan 2015 15:51:02 +0100 X-Google-Sender-Auth: lNHygq8VdVRBxWCZRrmfkWn5fUQ Message-ID: To: "bitcoin-development@lists.sourceforge.net" Content-Type: multipart/alternative; boundary=047d7b874b2ca80398050d52eced 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: 1YEfaD-00007z-OA Subject: [Bitcoin-development] SIGHASH_WITHINPUTVALUE 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, 23 Jan 2015 14:51:39 -0000 --047d7b874b2ca80398050d52eced Content-Type: text/plain; charset=ISO-8859-1 Hi, is any progress or even discussion in this area? https://bitcointalk.org/index.php?topic=181734.0 I don't insist on any specific solution, but this is becoming a real issue as hardware wallets are more widespread. I'm sitting next to TREZOR for 40 minutes already, because it streams and validate some complex transaction. By using proposed solution, such signature would be a matter of few seconds. That's also not just about time/resource/hw cost optimization. I'm talking about possibility of huge simplification of the firmware (=security FTW), because 50% of actual codebase is solving this particular downside of Bitcoin protocol. So, there's real world problem. On which solution can we as a community find a wide agreement? Best, Marek --047d7b874b2ca80398050d52eced Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

is any progress or eve= n discussion in this area?=A0

=

I don't insist on any specific solution, but this i= s becoming a real issue as hardware wallets are more widespread. I'm si= tting next to TREZOR for 40 minutes already, because it streams and validat= e some complex transaction. By using proposed solution, such signature woul= d be a matter of few seconds.

=
That's also not just about time/resource/= hw cost optimization. I'm talking about possibility of huge simplificat= ion of the firmware (=3Dsecurity FTW), because 50% of actual codebase is so= lving this particular downside of Bitcoin protocol.

So, there's real wo= rld problem. On which solution can we as a community find a wide agreement?=

Best,
Marek
--047d7b874b2ca80398050d52eced--