From: Wladimir <laanwj@gmail•com>
To: "Jorge Timón" <jtimon@monetize•io>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
Date: Wed, 25 Jun 2014 07:43:23 +0200 [thread overview]
Message-ID: <CA+s+GJCpUzasKD8KYbweTu25SyXAJAx31TmfYj2iHG2fN62AFA@mail.gmail.com> (raw)
In-Reply-To: <CAC1+kJPycskhv7m=ygEO1htryWRju4bdzWOFfZ3cEu_uKX2k2w@mail.gmail.com>
On Tue, Jun 24, 2014 at 6:40 PM, Jorge Timón <jtimon@monetize•io> wrote:
>
> 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.
I haven't been talking about the GUI at all in this entire
conversation. When I say wallet, I mean the wallet code. There are
very few reasons for running a wallet 24/7. One could be if you're
running an exchange that has to send and receive transactions all the
time.
But that's an exception - in the usual merchant/end-user case you're
mostly receiving transactions and sometimes manually or batched-
sending them. No need to leave the wallet running, exposed to the
network outside those times.
How the wallet GUI (if any) relates to the wallet code is a completely
different topic, and a much less pressing matter. Anything from 'GUI
uses wallet as a library' (multibit, electrum, bitcoin core) to
elaborate client-server protocols (btcd, coinvault?) are acceptable
depending on the use case.
Wladimir
next prev parent reply other threads:[~2014-06-25 5:43 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
2014-06-25 5:43 ` Wladimir [this message]
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+GJCpUzasKD8KYbweTu25SyXAJAx31TmfYj2iHG2fN62AFA@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