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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1RDFYj-0002yd-Jj
for bitcoin-development@lists.sourceforge.net;
Mon, 10 Oct 2011 13:06:21 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RDFYf-0007uV-FJ for bitcoin-development@lists.sourceforge.net;
Mon, 10 Oct 2011 13:06:21 +0000
Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net
[184.4.160.40]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 1C35D20409A;
Mon, 10 Oct 2011 13:06:11 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: Mike Hearn <mike@plan99.net>
Date: Mon, 10 Oct 2011 09:05:56 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; )
References: <CABsx9T2eCpxqzbd0PmWJxCDFLHwOix2BOYp+APQGMZYh_O+R4g@mail.gmail.com>
<201110081912.33356.luke@dashjr.org>
<CANEZrP1tyxE2inhg2adJHTQTxgNmsB30L8c7874CLZUmHyKYAw@mail.gmail.com>
In-Reply-To: <CANEZrP1tyxE2inhg2adJHTQTxgNmsB30L8c7874CLZUmHyKYAw@mail.gmail.com>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201110100905.58725.luke@dashjr.org>
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1RDFYf-0007uV-FJ
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Help wanted: translations
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: Mon, 10 Oct 2011 13:06:21 -0000
On Monday, October 10, 2011 5:22:28 AM Mike Hearn wrote:
> On Sun, Oct 9, 2011 at 1:12 AM, Luke-Jr <luke@dashjr.org> wrote:
> > As I will no longer be using bitcoind for Eligius soon
>
> What will you be using instead? Isn't bitcoind a requirement for running a
> pool?
Writing some custom software designed to more efficiently create work.
To clarify, bitcoind will still serve the purpose of peering with external
nodes and picking out valid transactions to be accepted into blocks; it just
won't be involved in the primary operations of the pool.
|
