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 10:11:48 -0400 [thread overview]
Message-ID: <201110101011.50597.luke@dashjr.org> (raw)
In-Reply-To: <CANEZrP2wyw+951SJxDJyZ0rLNA9UvRJ9a+B7=-jui-w+A0GOWA@mail.gmail.com>
On Monday, October 10, 2011 9:18:07 AM Mike Hearn 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.
>
> Ah, I see. Sounds a bit like the direction Steve is going with poolserverj.
> So your custom software would handle incrementing the extraNonce,
> recalculating the merkle tree/root, and so on?
Yes, does that already. Hard part right now is implementing a stateless TCP/IP
"stack" so it can ignore DDoS sanely.
next prev parent reply other threads:[~2011-10-10 14:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 21:13 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
2011-10-10 13:18 ` Mike Hearn
2011-10-10 14:11 ` Luke-Jr [this message]
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=201110101011.50597.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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