The only thing that was affected by the bug were windows wallets. If you are hosting a pool on a windows server well then that is just silly. Regardless if you had applied the newest patch as direct you would have been all set.
I NEWER use windows, only linux. And I always compile my daemons from source code.
So, your bug is much wider than you think.
Your pool is the only one that is "having a problem". Though I don't even believe it is. All I ask is if you do have an issue, hop on over to IRC and let the community work with you to fix it. I've never even heard of your pool until you said you were closing it down, I've been in IRC more or less all day since launch. If there is a problem, don't sit back and play the victim card. Be proactive, work with us to get to the solution so we can all get back to mining.
It was forked or stuck for me too, on Debian 7 64bit. I deleted everything and started with the nodes from OP. It got stuck on block 32xx and had 7 connections. Nothing happened for 30 minutes so I added dedicatedpool.com as a node and it quickly synced.
Show Posts
