I've been using this a little bit lately, makes keeping an eye on things much simpler and switching pools an easy task (instead of managing sprawling config files). Haven't had a chance to play with the multi-algo functionality yet but looking forward to doing so. Plus the dev is a nice guy who is real responsive on IRC. Recommended!

Any nodes? 

I've only been mining with Hashcows and hanging out in their IRC channel for 6 months, what do I know?  


Exactly, so I'm still not sure what point you are trying to make, but I've stopped trying to understand now.

I give up.  

Happy mining/trading/moaning!

You realise a few things though right?

1) Hashcows is not a new pool, its one of the most established, popular and successful scrypt multipools out there.
2) They only need to buy enough 365Coin to cover the BTC that would have otherwise been paid out to the users who have requested 365Coin payouts instead. This isn't going to be a vast sum right now, there are only a few people taking 365Coin instead of BTC. There will be no problems buying this 365Coin with current levels of market liquidity.
3) Scrypt alts you mined are traded according to Hashcows trading strategy, this doesn't change whether you take BTC, 365, BC or any other coin for that matter. The only time Hashcows trading strategy is irrelevant is when you are keeping the alts for yourself, which is one of the unique features of this particular multipool. Their trading strategy is designed to maximise your ultimate final payout, whether thats BTC or anything else.
4) They have no reason for interest in pumping or dumping 365Coin. They just pay out in the currency you have chosen.

I think you're looking for conspiracy or problems where there are none.

What are you talking about? No payout for a week from where? Who will pump dump with your money?  

You need to clarify what you are talking about.

You mine just like any other Hashcows multipool user, with scrypt - but at payout time, your BTC revenue is converted into 365Coin and paid out to you.

Agree First Keccak coin on Hashcows 

Only a few of us on the official pool right now, its kind of like augmented solo mining

I just moved my hash over to the official 365coin mining pool.

Don't let up on the voting guys!  

I don't get what was so difficult.

All I did was rename the old QT (and my wallet.dat, though this wasn't necessary), pasted the new QT into the same folder as the old one, and ran it like normal, using the the same data folders and files.

Everything worked as it did before. I did not lose any coins. My old wallet.dat wasn't replaced. I didn't have to import any keys. It just worked.

Today nearmiss has taken steps to solve email deliverability issues, so if you've had problems with password reset emails in the past, please give it another try!

This is often the case when mining on Hashcows. I've mined there since Nov and experience the same thing. If your cgminer is reporting the right hashrate and shares accepted, and you have solid WU, then there's nothing to worry about.

Just checking in with a reminder to read the most recent 15-30 pages of this thread before asking any questions, raising any concerns, causing any FUD, etc. Most of the answers are already here.  Happy mining.

Nearmiss has slightly more experience than the blackcoinpool.com operators at running a profitable multipool.  Could almost guarantee you'll make more paying out from hashco.ws in BC than blackcoinpool.com. They had a great time a few days ago, but funnily enough, that was while BC was on a tear upwards in price. 

Thanks  (and thanks for not stealing any Bitcoin from those exchanges either  )

Go back through that dude's post history too. At least 75% of his posts are shrieking about one thing or another.  

If you spot a service which hasn't updated (reporting stupidly low diff, for example) then contact them and tell them so! 

The team appreciate the feedback. There have been one or two other reports like this, the first within hours of the heartbleed openssl exploit becoming public knowledge. Nearmiss patched the server against the vulnerability as early as possible today. If anyone else has similar issues, please email support@hashco.ws with full info to help nearmiss investigate - but the initial hunch is that it was an opportunistic thing using heartbleed.

Hence the disclaimer at the bottom.

Incidentally, can you point out to me where hashco.ws FAQ talks about stales?  (hint: it doesn't)

When I've asked nearmiss in the past whether we should submit stales to hashco.ws, the answer has been no.

You're obviously free to pursue a life of stale submitting happiness. I will continue to heed good pool etiquette, based on the response I got from the pool owner.