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 1VyK7a-00016e-I6 for bitcoin-development@lists.sourceforge.net; Wed, 01 Jan 2014 11:37:58 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.45 as permitted sender) client-ip=209.85.214.45; envelope-from=laanwj@gmail.com; helo=mail-bk0-f45.google.com; Received: from mail-bk0-f45.google.com ([209.85.214.45]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VyK7Z-0006wx-Lb for bitcoin-development@lists.sourceforge.net; Wed, 01 Jan 2014 11:37:58 +0000 Received: by mail-bk0-f45.google.com with SMTP id mx13so4300736bkb.32 for ; Wed, 01 Jan 2014 03:37:51 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.204.81.7 with SMTP id v7mr24760566bkk.3.1388576271156; Wed, 01 Jan 2014 03:37:51 -0800 (PST) Received: by 10.204.69.197 with HTTP; Wed, 1 Jan 2014 03:37:51 -0800 (PST) In-Reply-To: References: <52A3C8A5.7010606@gmail.com> <1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net> <52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org> <20131212205106.GA4572@netbook.cypherspace.org> <4264e886-48de-40ac-921a-a60502595060@email.android.com> Date: Wed, 1 Jan 2014 12:37:51 +0100 Message-ID: From: Wladimir To: Jeremy Spilman Content-Type: multipart/alternative; boundary=047d7bf0c2c862f56404eee71b81 X-Spam-Score: -0.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 (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1VyK7Z-0006wx-Lb Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org, your thoughts? 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, 01 Jan 2014 11:37:58 -0000 --047d7bf0c2c862f56404eee71b81 Content-Type: text/plain; charset=UTF-8 > > In any case, I think wallet users want to know when an upgrade is > available, and ability to click an 'update' button get a binary they can > trust. It's not a problem unique to bitcoind, deterministic builds are > awesome, but I don't think fully solve it. > Deterministic builds are one part of the equation. Matt Corallo actually did implement auto-updating using gitian updater: https://github.com/bitcoin/bitcoin/pull/1453 It ran into lots of bike shedding and was eventually abandoned, but there is no question whether it is possible with the current build process. Wladimir --047d7bf0c2c862f56404eee71b81 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In any case, I think wallet users want to know when an upgrade is
available, and ability to click an 'update' button get a binary the= y can
trust. It's not a problem unique to bitcoind, deterministic builds are<= br> awesome, but I don't think fully solve it.

Deterministic builds are one part of the equation. Matt Corallo act= ually did implement auto-updating using gitian updater:

It ran into lots of bike shedding and was eventually ab= andoned, but there is no question whether it is possible with the current b= uild process.

Wladimir

--047d7bf0c2c862f56404eee71b81--