|
Title: Contributing a node ;) Post by: NetTecture on June 05, 2011, 09:05:26 AM Ok, here we go ;)
As I unerstand it, miner clients do not track transactions - they are "stupid" and only process what they are given from a server node, which can be a pool. How do I set up a transaction processing node? Just starting the normal client, possibly as daemon? I ask because I want to really contribute a little more than a small mining farm. I have servers lyin around in a high end data center (no, not related to mining too much - I just run my other business operations there) and could handle some load there. Does it make sense? Title: Re: Contributing a node ;) Post by: TheSeven on June 05, 2011, 09:26:40 AM You could of course just install bitcoin clients on them to support the peer to peer network, but transaction processing and mining are the same thing. So if you want to do transaction processing, you need to have huge hashing power, which you typically don't have in server machines. So you'd need some dumb hashing clients to do that work for you, i.e. set up a mining pool :)
Title: Re: Contributing a node ;) Post by: supa on June 05, 2011, 06:01:10 PM You can dedicate a small amount of usage to transaction processing by setting the official client to generate with a proclimit. Even if it's only 1MH (roughly on thread on an old Athlon X2), you're contributing 1MH to transaction processing. Low-bandwidth and low usage web servers can easily share 1MH and you can nice it/set priority to not interfere with operation. I hope future designs reward transaction processing and not just mining. As you can see, the current design has lent itself to people only mining in pools and not really giving a damn about transactions. |