public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: Mike Hearn <mike@plan99.net>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Help wanted: translations
Date: Mon, 10 Oct 2011 09:05:56 -0400	[thread overview]
Message-ID: <201110100905.58725.luke@dashjr.org> (raw)
In-Reply-To: <CANEZrP1tyxE2inhg2adJHTQTxgNmsB30L8c7874CLZUmHyKYAw@mail.gmail.com>

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.



  reply	other threads:[~2011-10-10 13:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 21:13 [Bitcoin-development] Help wanted: translations Gavin Andresen
2011-10-08 21:25 ` Christian Decker
2011-10-08 23:06 ` Martinx - ジェームズ
2011-10-08 23:12 ` Luke-Jr
2011-10-10  4:02   ` Luke-Jr
2011-10-10  9:22   ` Mike Hearn
2011-10-10 13:05     ` Luke-Jr [this message]
2011-10-10 13:18       ` Mike Hearn
2011-10-10 14:11         ` Luke-Jr
2011-10-22 10:51 ` Nils Schneider
2011-10-22 12:26   ` Geir Harald Hansen
2011-10-22 13:28     ` Nils Schneider
2011-10-22 16:14       ` Geir Harald Hansen
2011-10-24 11:24         ` Christian Decker
2011-10-24 18:10           ` John Smith
2011-10-24 18:55             ` Geir Harald Hansen
2011-10-25  5:02               ` John Smith
2011-10-29 21:16                 ` John Smith

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=201110100905.58725.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mike@plan99.net \
    /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