diff options
author | Gregory Maxwell <gmaxwell@gmail.com> | 2014-04-09 08:54:25 -0700 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2014-04-09 15:54:33 +0000 |
commit | 97f9cbaf25588ed9dece004e9a1352727d67c64c (patch) | |
tree | 3a83c29e676633560296271bfc1fffe875818d5c | |
parent | 8d871ce8d5d17f0844a64f1fb18bc4801d73f453 (diff) | |
download | pi-bitcoindev-97f9cbaf25588ed9dece004e9a1352727d67c64c.tar.gz pi-bitcoindev-97f9cbaf25588ed9dece004e9a1352727d67c64c.zip |
Re: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets
-rw-r--r-- | 27/c234e6e3f36fa180afa815fa8c3fc3d430dc3f | 84 |
1 files changed, 84 insertions, 0 deletions
diff --git a/27/c234e6e3f36fa180afa815fa8c3fc3d430dc3f b/27/c234e6e3f36fa180afa815fa8c3fc3d430dc3f new file mode 100644 index 000000000..b7896bfb0 --- /dev/null +++ b/27/c234e6e3f36fa180afa815fa8c3fc3d430dc3f @@ -0,0 +1,84 @@ +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 <gmaxwell@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>; + 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: <CAAt2M18z_Qkqat1OETiXAz0QQey4+y5J6=pC7nkoJfyfrpj3=A@mail.gmail.com> +References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com> + <CAAt2M18z_Qkqat1OETiXAz0QQey4+y5J6=pC7nkoJfyfrpj3=A@mail.gmail.com> +Date: Wed, 9 Apr 2014 08:54:25 -0700 +Message-ID: <CAAS2fgScWkentFy7Ak0bpYVLsOFL+xkwPm5QRu9ENeX9oCtPug@mail.gmail.com> +From: Gregory Maxwell <gmaxwell@gmail.com> +To: Natanael <natanael.l@gmail.com> +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 <bitcoin-development@lists.sourceforge.net> +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: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Wed, 09 Apr 2014 15:54:33 -0000 + +On Wed, Apr 9, 2014 at 8:41 AM, Natanael <natanael.l@gmail.com> 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). + + |