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. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
