From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXupd-00081L-Fu for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 15:54:33 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.50 as permitted sender) client-ip=209.85.215.50; envelope-from=gmaxwell@gmail.com; helo=mail-la0-f50.google.com; Received: from mail-la0-f50.google.com ([209.85.215.50]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXupc-0000t1-OJ for bitcoin-development@lists.sourceforge.net; Wed, 09 Apr 2014 15:54:33 +0000 Received: by mail-la0-f50.google.com with SMTP id pv20so1309405lab.37 for ; Wed, 09 Apr 2014 08:54:26 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.94.229 with SMTP id df5mr7568273lbb.36.1397058866027; Wed, 09 Apr 2014 08:54:26 -0700 (PDT) Received: by 10.112.89.68 with HTTP; Wed, 9 Apr 2014 08:54:25 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Apr 2014 08:54:25 -0700 Message-ID: From: Gregory Maxwell To: Natanael 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 (gmaxwell[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: 1WXupc-0000t1-OJ 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 15:54:33 -0000 On Wed, Apr 9, 2014 at 8:41 AM, Natanael wrote: > This could probably be done fairly easily by bundling Stratum (it's > not just for pools!) and allowing SPV wallets to ask Bitcoind to start > it (if you don't use it, there's no need to waste the resources), and > then connect to it. The point of using Stratum is that it already is > being used by Electrum, Sadly today Electrum requires more than a full node, it requires a number of large additional indexes over what a full node has and pruning is precluded. I don't think that increasing the resource utilization of the node is a good way to go there for the purposes expressed here. (not that electrum couldn't be used here, but not unmodified without the resource usage increasing route) > and that it might be an easier way to support > SPV clients than creating a new API in bitcoind for it since Stratum > itself already relies on bitcoind to provide it's services. Bitcoin's own P2P protocol is already the API for a ordinary SPV client. So I don't believe any new API would be require, except perhaps for some process management stuff (which also isn't provided for Electrum).