public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Justus Ranvier <justusranvier@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
Date: Tue, 24 Jun 2014 15:33:41 +0000	[thread overview]
Message-ID: <53A99A55.1020506@gmail.com> (raw)
In-Reply-To: <CA+s+GJBT9u+LMqTfrTwUQrGbnrqj2u==1kmx17uQyY8899O8sw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

-----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.


- -- 
Support online privacy by using email encryption whenever possible.
Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJTqZpVAAoJEMP3uyY4RQ21E48H/0XNYBzR8QZjfku/MeL5IbwL
A56jrlWe2EZTabwfKdGx12L5oeBXe3DOeLsTizqIu0vijcl7qQryU49AjrVe91Rx
OdEi4lmaiXdkM3lWeWUxLoLLHR1B+1f8T18Mrnzo+yasyrywPb+6H79VN5KERdA2
5yHYCZyHXdNoXpzyf38GC2PdYJmAZdrRfAGyC5+OXSwE3XLhpRBrSBh/mrx0ct5M
ghkCKtsmJCJJ6sR2TbFxaj71kPp0J0tp8JVvjVEqC2uB4Ih0NY+79kz8L81TaNmw
ol1o6p7TypIk7QRQ4ES3Fq0ALh2aQ/tX4rc0GC0ed+xLi+dHJ2wGBI37HoyGIyg=
=Nn9X
-----END PGP SIGNATURE-----

[-- Attachment #2: 0x38450DB5.asc --]
[-- Type: application/pgp-keys, Size: 12464 bytes --]

  parent reply	other threads:[~2014-06-24 15:37 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 [this message]
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=53A99A55.1020506@gmail.com \
    --to=justusranvier@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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