From: Wladimir <laanwj@gmail•com>
To: "Jorge Timón" <jtimon@monetize•io>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
Date: Mon, 23 Jun 2014 12:32:50 +0200 [thread overview]
Message-ID: <CA+s+GJDVBQVu8yH9jLu_rQmk=dsJuMUctT-iK0zzOJRYgE8k9w@mail.gmail.com> (raw)
In-Reply-To: <CAC1+kJNjcPkaHiR8mzofwXE4+4UX5nmxX5Q3rZv37v-K40p1Tw@mail.gmail.com>
On Mon, Jun 23, 2014 at 11:50 AM, Jorge Timón <jtimon@monetize•io> wrote:
> I know there are plans to separate the wallet from the core code and I
> think it's a great idea that will result in cleaner and more modular
> software.
> But it seems like my assumptions on how this would be done may be incorrect.
>
> I was assuming that the wallet would consume data from a trusted
> bitcoind core node using rpc or a better interface like an http rest
> api (see PR #2844).
It's least surprising if the wallet works as a SPV client by default.
Then, users can use it without first setting up a core. Thus the idea
would be to use P2P primarily.
There could be a mode to use a trusted core by RPC for
mempool/conflicted transaction validation and such. But I'm not sure
about this - as we've seen, pure-SPV wallets work pretty well. If you
want it to act as an edge router you can point a SPV wallet at your
trusted core as well.
There are no plans for adding Electrum-like functionality to bitcoind.
There is already Electrum. Let's not reinvent any wheels.
> So the core would take care of the hard consensus stuff, and the
> wallet would maintain its own database with private keys, addresses,
> balances, etc. and would consume some data contained in bitcoind's
> database.
Right, the wallet would keep track of those.
> I also assumed that the interface between wallet and core would
> include queries to the UTXO (see PR #4351) and maybe TXO (see PR
> #3652) for getting the historic balances.
>
> As said, I'm not sure these assumptions are true anymore so I ask.
> Is this the plan?
> Is the plan that the wallet will use the p2p directly and maintain its
> own chain database?
It does not need to keep a full chain database. But it needs its own
record of the chain, headers-only + what concerns the keys in the
wallet.
Wladimir
next prev parent reply other threads:[~2014-06-23 10:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 9:50 Jorge Timón
2014-06-23 10:32 ` Wladimir [this message]
2014-06-23 20:15 ` Jorge Timón
2014-06-24 9:07 ` Wladimir
2014-06-24 9:44 ` Wladimir
2014-06-24 13:24 ` Thomas Voegtlin
2014-06-24 15:33 ` Justus Ranvier
2014-06-24 16:40 ` Jorge Timón
2014-06-25 5:43 ` Wladimir
2014-06-24 9:11 ` Mike Hearn
2014-06-24 9:40 ` Wladimir
2014-06-24 10:12 ` Mike Hearn
2014-06-24 11:29 ` Jorge Timón
2014-06-24 11:48 ` Tamas Blummer
2014-06-24 13:26 ` Jorge Timón
2014-06-24 13:37 ` Pieter Wuille
2014-06-24 11:58 ` Wladimir
2014-06-24 12:16 ` Mike Hearn
2014-06-24 12:41 ` Wladimir
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='CA+s+GJDVBQVu8yH9jLu_rQmk=dsJuMUctT-iK0zzOJRYgE8k9w@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jtimon@monetize$(echo .)io \
/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