From: Mike Hearn <mike@plan99•net>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Help wanted: translations
Date: Mon, 10 Oct 2011 15:18:07 +0200 [thread overview]
Message-ID: <CANEZrP2wyw+951SJxDJyZ0rLNA9UvRJ9a+B7=-jui-w+A0GOWA@mail.gmail.com> (raw)
In-Reply-To: <201110100905.58725.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
>
> > > 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?
[-- Attachment #2: Type: text/html, Size: 870 bytes --]
next prev parent reply other threads:[~2011-10-10 13:18 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 [this message]
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='CANEZrP2wyw+951SJxDJyZ0rLNA9UvRJ9a+B7=-jui-w+A0GOWA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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