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 dtramm...@dustintrammell.com http://www.dustintrammell.com
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
