From: "Dustin D. Trammell" <dtrammell@dustintrammell•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core trial balloon: splitting blockchain engine and wallet
Date: Fri, 21 Feb 2014 19:04:12 -0600 [thread overview]
Message-ID: <1393031052.6897.89.camel@staypuft> (raw)
In-Reply-To: <CAJHLa0OD7w0Rs5ygAE4C14EWm1=x57YHG2kOee1pzxvj3FQ38g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Fri, 2014-02-21 at 01:09 -0500, Jeff Garzik wrote:
> Recent IRC discussion have floated a rough proposal for a wallet
> next-step: Running the Bitcoin Core wallet as a separate process, a
> separate binary, from the blockchain engine. The wallet process would
> communicate with the blockchain engine using existing RPC and P2P
> channels, becoming a real SPV client. This accomplishes a
> longstanding security goal of sandboxing away wallet keys and
> sensitive data from the network-exposed P2P engine, in a separate
> process, among other benefits.
PLEASE.
For those of us that prefer the reference software and also manage
multiple wallets, having to store a copy of the blockchain for each one
eats up disk space quite quickly. If I could run a local blockchain
server (or a local network one, even) and then have whichever wallet I
start up use that instead of maintain its own copy of the blockchain, my
world would be much, much happier.
Sandboxing keys and sensitive wallet data away from the attack surface
introduced by the network interfaces into another separate process is
also a good security move. Don't forget to sanitize your IPC inputs (:
Thanks,
--
Dustin D. Trammell
dtrammell@dustintrammell•com
http://www.dustintrammell.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-22 1:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:09 Jeff Garzik
2014-02-21 6:27 ` Mike Hearn
[not found] ` <CA+s+GJCRqqmoHkmsq+6x9Wm6btKzdXoPjw5Af8zRDEkDE+6+zw@mail.gmail.com>
2014-02-21 6:43 ` [Bitcoin-development] Fwd: " Wladimir
2014-02-21 6:50 ` William Yager
2014-02-21 6:54 ` Wladimir
2014-02-22 1:09 ` Dustin D. Trammell
2014-02-22 6:53 ` Wladimir
2014-02-24 22:16 ` James Hartig
2014-02-21 6:50 ` [Bitcoin-development] " Jeff Garzik
2014-02-21 10:41 ` Mike Hearn
2014-02-21 11:06 ` Peter Todd
2014-02-22 1:04 ` Dustin D. Trammell [this message]
2014-02-22 2:08 ` Jeff Garzik
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=1393031052.6897.89.camel@staypuft \
--to=dtrammell@dustintrammell$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(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