Take the 2-minute tour ×
Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. It's 100% free, no registration required.

What is needed to create a new pool with merged mining? (Bitcoin, NameCoin, and possibly others)?

I'd like to create a new pool that will

  • Include transaction fees in the payout
  • Charge no pool fees
  • Hosted on Amazon (Low latency)
  • Do merged mining if that doesn't create any inefficiency

I'm mostly interested in software, or general knowledge that will get me started in the right direction.

share|improve this question
    
Dear makerofthings, Did you make anything from this question? Would like to do something similar and maybe we can share our resources? SMS or Call Me: +356 9959 8129 –  Tommy Cox Green Apr 9 '13 at 19:56
add comment

2 Answers

You will need to be running the standard client with some special configuration - server=1 along with rpcuser and rpcpassword set. After that, you need to build your pool server to communicate with it through Bitcoin API and handle everything else. Last part is not too Bitcoin-specific and will consume a lot of your development time (I would know, I tried it ;) ).

share|improve this answer
    
Does the pool do the merged mining, or is that from the BitCoin API? Can you recommend any pool software? –  makerofthings7 Dec 6 '12 at 22:34
    
@makerofthings7 Hmm, as far as I remember there is a special application that communicates with both Bitcoin and Namecoin clients to get the appropriate information, then makes a new block for getwork request. I can't really recommend anything, as I haven't really looked into any such software. –  ThePiachu Dec 7 '12 at 9:24
add comment

You need to run both bitcoind and namecoind.

To be able to create namecoin blocks you will need to do merged mining. Either find pool software that does this out of the box, or implement it yourself following the merged mining specification.

Other coins that support merged mining work the same way as namecoin.

With Stratum or getblocktemplate (GBT) there should not be any efficiency problems. With the old getwork protocol you may have a slight drop in efficiency from extra long poll notifications. That's because miners may need additional HTTP requests to get enough work after the long poll. You may want to consider whether you want to do long poll only for bitcoin. But as miners move away from getwork this may not be worth bothering with.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.