From: "Jorge Timón" <jtimon@monetize•io>
To: Justus Ranvier <justusranvier@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
Date: Tue, 24 Jun 2014 18:40:16 +0200 [thread overview]
Message-ID: <CAC1+kJPycskhv7m=ygEO1htryWRju4bdzWOFfZ3cEu_uKX2k2w@mail.gmail.com> (raw)
In-Reply-To: <53A99A55.1020506@gmail.com>
On 6/24/14, Justus Ranvier <justusranvier@gmail•com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 06/24/2014 09:07 AM, Wladimir wrote:
>> My main argument for the split is that full nodes and wallets have
>> completely different usage scenarios:
>>
>> - A wallet should be online as little as possible, ideally only
>> when you do transactions or want to check for them.
>>
>> - A full node should be online 24/7 or it is virtually useless to
>> the network.
>
> I think btcd has done this right.
>
> A wallet is a daemon that runs constantly in the background, just like
> the full node.
>
> The GUI (which is distinct from the wallet) runs as little as
> possible. Presumably there's no need for a 1:1 relationship between
> wallets and GUIs.
I think he means that the wallet shouldn't be running as much as it is
currently doing.
But yes, I think you're right about wallets and GUIs not necessarily
mapping 1:1.
next prev parent reply other threads:[~2014-06-24 16:40 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
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 [this message]
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='CAC1+kJPycskhv7m=ygEO1htryWRju4bdzWOFfZ3cEu_uKX2k2w@mail.gmail.com' \
--to=jtimon@monetize$(echo .)io \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=justusranvier@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