From: Natanael <natanael.l@gmail•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets
Date: Wed, 9 Apr 2014 17:41:31 +0200 [thread overview]
Message-ID: <CAAt2M18z_Qkqat1OETiXAz0QQey4+y5J6=pC7nkoJfyfrpj3=A@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
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, 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.
On Wed, Apr 9, 2014 at 5:29 PM, Wladimir <laanwj@gmail•com> wrote:
> Hello,
>
> This is primarily aimed at developers of SPV wallets.
>
> The recently reported decrease in number of full nodes could have several
> reasons, one of them that less people are running Bitcoin Core for the
> wallet because the other wallets are getting ahead in both features and
> useability.
>
> It's great to see innovation in wallets, but it's worrying that the number
> of full nodes decreases.
>
> It may be that lots of people would support the network by running a full
> node, but don't want to go through the trouble of installing bitcoin core
> separately (and get confused because it's a wallet, too).
>
> Hence I'd like to explore the idea of adding an option to popular SPV
> wallets, to spin a bitcoind process in the background. This could be pretty
> much transparent to the user - it would sync in the background, the wallet
> could show statistics about the node, but is not dependent on it.
>
> In exchange the user would get increased (full node level) security, as the
> SPV wallet would have a local trusted node.
>
> Does this sound like a good idea?
>
> Is there any way that Bitcoin Core can help to accomedate this 'embedded'
> usage? Specific Interfaces, special builds - maybe add a walletless bitcoind
> build to gitian - bindings, dlls, etc?
>
> Wladimir
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2014-04-09 15:41 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 15:29 Wladimir
2014-04-09 15:37 ` Tamas Blummer
2014-04-09 15:41 ` Natanael [this message]
2014-04-09 15:54 ` Gregory Maxwell
2014-04-09 16:09 ` Thomas Voegtlin
2014-04-09 19:25 ` Wladimir
2014-04-10 6:04 ` Tamas Blummer
2014-04-10 11:09 ` Wladimir
2014-04-10 11:29 ` Mike Hearn
2014-04-10 11:32 ` Pieter Wuille
2014-04-10 11:43 ` Peter Todd
2014-04-10 11:50 ` Gregory Maxwell
2014-04-10 11:54 ` Peter Todd
2014-04-10 17:30 ` Tier Nolan
2014-04-11 16:54 ` Gregory Maxwell
2014-05-04 21:11 ` Tier Nolan
2014-04-09 17:31 ` Wladimir
2014-04-09 15:42 ` Brian Hoffman
2014-04-09 15:57 ` Gregory Maxwell
2014-04-09 16:09 ` Tamas Blummer
2014-04-09 15:47 ` Mark Friedenbach
2014-04-09 16:27 ` Tamas Blummer
2014-04-09 17:46 ` Peter Todd
2014-04-09 17:50 ` Tamas Blummer
2014-04-09 18:00 ` Mike Hearn
2014-04-09 18:19 ` Wladimir
2014-04-09 18:35 ` Justus Ranvier
2014-04-09 18:46 ` Wladimir
2014-04-09 18:50 ` Gregory Maxwell
2014-04-09 18:58 ` Justus Ranvier
2014-04-09 19:33 ` Gregory Maxwell
2014-04-09 20:12 ` slush
2014-04-09 20:31 ` slush
2014-04-09 20:36 ` Mark Friedenbach
2014-04-09 21:04 ` Gregory Maxwell
2014-04-09 20:37 ` Wladimir
2014-04-09 20:35 ` Wladimir
2014-04-09 20:50 ` slush
2014-04-09 20:55 ` Laszlo Hanyecz
2014-04-10 6:38 ` Mike Hearn
2014-04-10 6:50 ` Wladimir
2014-04-10 7:09 ` Mike Hearn
2014-04-10 9:33 ` Peter Todd
2014-04-10 7:10 ` Tamas Blummer
2014-04-10 9:17 ` Mike Hearn
2014-04-10 9:39 ` Tamas Blummer
2014-04-10 10:40 ` Mike Hearn
2014-04-10 10:44 ` Tamas Blummer
2014-04-10 11:36 ` Peter Todd
2014-04-10 11:45 ` Mike Hearn
2014-04-10 11:52 ` Peter Todd
2014-04-10 9:47 ` Peter Todd
2014-04-09 18:04 ` Peter Todd
[not found] ` <CA+s+GJBpvqqu=XEojyekx5su+JfYLwz+zsbo8L0=5t6s-_b33w@mail.gmail.com>
2014-04-09 17:35 ` [Bitcoin-development] Fwd: " Wladimir
2014-04-09 16:03 ` [Bitcoin-development] " Peter Todd
2014-04-09 17:33 ` Alex Mizrahi
2014-04-09 17:38 ` Wladimir
2014-04-09 17:38 ` Peter Todd
2014-04-09 18:35 ` Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAt2M18z_Qkqat1OETiXAz0QQey4+y5J6=pC7nkoJfyfrpj3=A@mail.gmail.com' \
--to=natanael.l@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox