Quote from: zing96 on July 12, 2014, 02:30:10 PM

Quote from: nanoprobe on July 12, 2014, 02:14:26 PM

Quote from: Madcat71 on July 12, 2014, 10:30:35 AM

Quote from: zing96 on July 12, 2014, 03:36:00 AM

Quote from: Liquid71 on July 12, 2014, 03:18:12 AM

Quote from: Cloak1 on July 12, 2014, 12:44:48 AM

Quote from: bangomatic on July 12, 2014, 12:30:25 AM

Quote from: TheDagger on July 11, 2014, 11:31:36 PM

Quote from: bangomatic on July 11, 2014, 11:18:55 PM

Dev's... Please build a dedicated cloak multi-pool. ASAP!

Ok sir!!!

We'll stop PoSA and OneMarket right now Tongue

(that's a joke btw in case anybody decides to misinterpret).

Btw, on a more serious note:

Our previous dedicated multipool was going well but was costing the pool owner $150 in server costs and 3 hours a day of work.

He was losing money on it when factoring in his time etc.

He'd reopen it if we could get a constant 5 gh/s.

I will put my 36 mh on it Cheesy

Multipool,us+Cryptsy=Cloakcoin

http://coinking.io/?r=13113 also has auto convert feature so you get cloak for whatever coins you mined

For what it's worth, I couldn't mine at CoinKing. My error rate was anywhere between 10% to 20%. I've never had that issue with any other multipool using the same settings. My error rate with the Cloak multipool was less than 1%; usually around 0.5%.

Same problem for me with coinking my GPU´s was getting around 20% in error rate...
Give me a pool that works and i point my 36-40Mhz on it

Are you talking HW errors or rejected shares?

Invalid/rejected shares. HW errors were 0. No settings were changed between CoinKing and Cloak multipool. Yet Cloak multipool had an error rate of less than 1% while CoinKing was near 20%.

I get the same high rejected share rate there too if I use my asic miner. From my experience with the other pool and the guy who ran it this rejected share issue is a diff problem for asics. The other pool operator offered a dedicated port with a higher diff that solved the issue. Until coinking decides to do something on their end this will continue to be a problem IMHO.