It seems several pools haven't figured out how best to operate with GoldCoin's 51% protection. It appears to be working quite well.
I wonder if in the long run most folks will prefer to solo mine.
it has nothing to do with the 51% its the lag on a block find.
Actually it does have to do with the 51% defense, 0.7.1.5 has code built in such that you can find acceptable blocks 45 seconds EARLIER than 0.7.1.4 and below, as the client will permit blocks to have a maximum timestamp of 45 seconds into the future.
In otherwords 0.7.1.5 gets less rejects..
I'm sorry about the lag .. it's actually a built-in wait() in the client..
It cannot be avoided at the moment because the client's functions are almost all interdependent.. This is a flaw inherent to bitcoin's single threaded codebase.
The output of any given function is usually the input of another, so I can't simply put the checkblock/acceptblock into a seperate thread.. as the function that called it will end up waiting anyways.
Anyhow, the main issue here is with your cron schedule.
Perhaps if you went into greater detail I could help you with it.
Alternatively you can go back to 0.7.1.4 but lose the advantage.
I plan to rewrite the codebase from scratch and make it multithreaded myself, in approximately 2 weeks.
It'll probably take a month or so to get done though..
It's up to you..
Honestly since we have the 51% defense in place.. it makes little difference whether our hashrate is 5mh/s or 30mh/s or 100GH/s
So do what you like
