From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Cc: bitcoingrant@gmx.com
Subject: Re: [Bitcoin-development] Modularizing Bitcoin
Date: Sun, 26 May 2013 23:53:57 +0000 [thread overview]
Message-ID: <201305262354.02856.luke@dashjr.org> (raw)
In-Reply-To: <20130516100206.82680@gmx.com>
On Thursday, May 16, 2013 10:02:05 AM bitcoingrant@gmx.com wrote:
> One of the main goals will be to separate the wallet from the node, as we
> have already done with mining.
How is this different from what Electrum has already done?
Luke
next prev parent reply other threads:[~2013-05-26 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 10:02 [Bitcoin-development] Modularizing Bitcoin bitcoingrant
2013-05-16 10:27 ` Addy Yeow
2013-05-16 16:43 ` Brenton Camac
2013-05-16 19:35 ` Mike Hearn
2013-05-20 5:16 ` Quinn Harris
2013-05-26 23:53 ` Luke-Jr [this message]
2013-05-16 10:48 bitcoingrant
2013-05-16 10:55 ` Addy Yeow
2013-05-26 23:57 ` Luke-Jr
2013-05-26 21:46 Ron
2013-05-27 2:57 Tamas Blummer
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=201305262354.02856.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=bitcoingrant@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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