1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WH20x-00048E-2l
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Feb 2014 02:08:27 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.47 as permitted sender)
client-ip=74.125.82.47; envelope-from=jgarzik@bitpay.com;
helo=mail-wg0-f47.google.com;
Received: from mail-wg0-f47.google.com ([74.125.82.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WH20w-0004oO-0N
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Feb 2014 02:08:27 +0000
Received: by mail-wg0-f47.google.com with SMTP id k14so3050323wgh.2
for <bitcoin-development@lists.sourceforge.net>;
Fri, 21 Feb 2014 18:08:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=B28jAUtLL1XX+iDowfz/HyJqB4nR4rtIyk/0pEo22yU=;
b=BwSeNJ5kUlu0O35SbKS7I2V59cmyq0BBtWSMIZidDHX+M301596ooFzcaROHe2Pq60
9ZF++rNNQd/QublTJVVu5gQ5vvpyqzwls+b8K1cyHO8/4+mueSuFAaRsYikTW2ocA2Zl
Q9HcRfpdT4YOIlBFTxtxRH8TXRoBY6l9W7zER/kAcKXvUG7HkJQWYumcTXLHH3yiBX3M
9tRHEmi0VlQEbPr0QcOn3STxT6GnsVEPZk2s8P6O/YXGcQ+7SIuLpb58+xwkJOtRiDI7
nV7RAJzy4LFgK+hFuyo6/M6NVmZMiBxQD2wEpg1s9zNLtf8avOW8r8rNpIRRFNnWh4rh
kVsg==
X-Gm-Message-State: ALoCoQkcqwbN3gWuvYboLdQ8xAl7vs2f95Dd9myvXGs5XzdMwwjCGBcGgM9K8EqAOYcdSqBmhaJx
MIME-Version: 1.0
X-Received: by 10.195.12.200 with SMTP id es8mr9528749wjd.77.1393034899579;
Fri, 21 Feb 2014 18:08:19 -0800 (PST)
Received: by 10.194.82.197 with HTTP; Fri, 21 Feb 2014 18:08:19 -0800 (PST)
In-Reply-To: <1393031052.6897.89.camel@staypuft>
References: <CAJHLa0OD7w0Rs5ygAE4C14EWm1=x57YHG2kOee1pzxvj3FQ38g@mail.gmail.com>
<1393031052.6897.89.camel@staypuft>
Date: Fri, 21 Feb 2014 21:08:19 -0500
Message-ID: <CAJHLa0OwtCja6XgmyVkiur9VtLdJ5Ra-F4R-ocpThyBVWrNHow@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: "Dustin D. Trammell" <dtrammell@dustintrammell.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WH20w-0004oO-0N
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core trial balloon: splitting
blockchain engine and wallet
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 22 Feb 2014 02:08:27 -0000
On Fri, Feb 21, 2014 at 8:04 PM, Dustin D. Trammell
<dtrammell@dustintrammell.com> wrote:
> 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.
You mean running multiple wallets simultaneously? Agreed.
Multiple wallets, used serially, works fine today. I manage multiple
wallets using symlink replacement.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
