LOL...Nice answer from dev...I would expect better one...but out of arguments leads to this...Thank you for this nice talk!
1) Managing the pool is work and Singula has been doing great to support the Cachecoin community
Managing (optimizing settings, updating coin daemon when it is necessary, solving troubles), support (answering a ton of questions from users) ... it is quite a work to run a pool and you need a lot of previous experience to be able to do it.
2) He opened up a second pool, since despite the fact that he provided information what is needed for a pool and offering his help, noone started a second pool. I wanted to, but after having it setup and running for a couple of hours it already got attacked and I do not want to sit in front of the pc 24/7 to watch the log for a php-mpos pool to see if anything is compromised. Keep in mind that this coin needs 520 confirmations until it matures and can be payed out. That is when we reach normal target time 7 days - so for 7 days I am like a bank and need to ensure that nothing is compromised to be able to pay out the miner....So no thank you - thats why I provied a p2pnode which pays out instantly and there are no coins in my wallet on the server.
It is only slightly above 5 days, not 7 days.
3) Singula is still offering anyone help to open up another pool - so if you dont want to mine on the first one - open your own one
True. Either send me a PM, or you may find me at #cachecoin on freenode (around 20:00 to midnight CEST you have quite a high chance to ask me questions interactively, outside of that time I may be still there, but idle
or just append "@catcoin.cz" to my nickname here and send an email.
4) the second pool only has 1.5% fee at the moment, and all fees will be at even again, once the hashrate is distributed
Second pool has basically the same configuration as first one (prop, vardiff, ... ), just the fee is lower to encourage people to move from the first pool
Idea is that the hashrate at both pools should be approximately the same and at the same time the pools together should have less than 50% of the network hashrate (I've set the fee a bit above p2pool nodes, as they have 1% fee, so there would be also a small incentive to join them). I'll start lowering the fees once we approach to this target, ending up probably at fee between 1.0 and 1.5% on both pools.
Current situation is that on the first pool the hashrate is 250 MH/s, second pool about 30 MH/s, p2pool nodes 100 MH/s combined, network hashrate is 420 MH/s, so I estimate also about 50 MH/s worth of solo-miners out there.
Ideal would be to have at most about 20-25% at each of the current pools, with rest of the hashrate being divided between p2pool nodes, solo miners and some other pools (those do not exist yet, though I hope soon some will do...)
So if the people mining do not care about distributing the hashrate to secure a network - the developer(s) and all pool owner(s) are bound to take action to distribute the hashrate and stabilize the network. (Look around about the fears of 51% attacks on bitcoin, think about if one pool has 70% hashrate what it means if that pool fails etc....)
if pool with 70% of the hashrate fails, with no other pools where miners could easily switch, this could endanger the network quite a bit (the cost for someone "outside" to perform a 51% attack will be significantly lowered, as people will need some time to notice the outage and switch to p2pools or solo mining). It is always good to have some redundancy. It is always good to have some redundancy. It is always good to have some redundancy.
