From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXxVl-0006rU-Av for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 18:46:13 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.181 as permitted sender) client-ip=209.85.213.181; envelope-from=laanwj@gmail.com; helo=mail-ig0-f181.google.com; Received: from mail-ig0-f181.google.com ([209.85.213.181]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXxVk-000136-CZ for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 18:46:13 +0000 Received: by mail-ig0-f181.google.com with SMTP id h18so2789795igc.8 for ; Wed, 09 Apr 2014 11:46:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.33.65 with SMTP id h1mr2067204icd.72.1397069167051; Wed, 09 Apr 2014 11:46:07 -0700 (PDT) Received: by 10.64.70.131 with HTTP; Wed, 9 Apr 2014 11:46:06 -0700 (PDT) In-Reply-To: <534592E2.7040800@gmail.com> References: <53456B99.9010207@monetize.io> <00b77560-d7ed-4ed4-a4e5-eb1f00467a06@email.android.com> <0509477C-89F9-47C7-8820-29ACAD4A4A8E@bitsofproof.com> <534592E2.7040800@gmail.com> Date: Wed, 9 Apr 2014 20:46:06 +0200 Message-ID: From: Wladimir To: Justus Ranvier Content-Type: multipart/alternative; boundary=bcaec51827b86dcb6104f6a083b8 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: 1WXxVk-000136-CZ Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets 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, 09 Apr 2014 18:46:13 -0000 --bcaec51827b86dcb6104f6a083b8 Content-Type: text/plain; charset=UTF-8 On Wed, Apr 9, 2014 at 8:35 PM, Justus Ranvier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/09/2014 06:19 PM, Wladimir wrote: > > If no one wants to volunteer resources to support the network > > anymore, we'll have failed. > > If the security of the network depends on a broken incentive model, > then fix the design of the network so that economics works for you > instead of against you. > My solution would be quick to implement and could help increase the number of nodes in the short term. It will also smooth the way towards splitting off the wallet from Bitcoin Core, by giving people a choice what wallet they use with their full node. That doesn't preclude looking for longer-term solutions that change the incentive structure, but that is much more difficult and risky. I don't believe it's a matter of 'fixing that instead' in a few hours, though I nevertheless look forward to your pull request. Wladimir --bcaec51827b86dcb6104f6a083b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Wed, Apr 9, 2014 at 8:35 PM, Justus Ranvier &l= t;justusranvie= r@gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/09/2014 06:19 PM, Wladimir wrote:
> If no one wants to volunteer resources to support the network
> anymore, we'll have failed.

If the security of the network depends on a broken incentive model, then fix the design of the network so that economics works for you
instead of against you.

My solution would be quick= to implement and could help increase the number of nodes in the short term= . It will also smooth the way towards splitting off the wallet from Bitcoin= Core, by giving people a choice what wallet they use with their full node.=

That doesn't preclude looking for longer-term= solutions that change the incentive structure, but that is much more diffi= cult and risky. I don't believe it's a matter of 'fixing that i= nstead' in a few hours, though I nevertheless look forward to your pull= request.

Wladimir

--bcaec51827b86dcb6104f6a083b8--