[POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com

[comeonalready]

As client.reconnect is part of the stratum mining protocol for a reason, and it does have some valid uses, and that removing it is at best a quick hack, the protocol at this point seems to need to be extended so that responsible mining server operators can validate their server identity to mining clients, and public/private key encryption/authentication challenges would be the most readily available and accepted method of accomplishing this goal.  But, discretion should be left to pool operators and not mining clients as to how often authentication challenges occur, so all identity validation transactions should be initiated by the pool, and challenge-enabled clients could participate only if desired, ignore/discard requests if not capable, and not interfere with server operation if the stratum server software is not so equipped, and not be able to warp authentication attempts into any sort of denial of service attack by continually asking the server to authenticate itself.

Mining pool server operators would have to publish their public key, which clients would have to include in their miner configuration files or on the command line, in addition to the usual pool host name, username, and password values.  (Or could optionally choose to exclude public key if they are uninterested in authenticating servers for any reason, and could be enabled on a pool by pool basis in configurations using multiple backup servers.)

The proposed future protocol could look something like this:

mining.subscribe with usual parameters as normal (sent from client)

client.doauthenticate (new) including a randomized request id (sent only from authentication enabled servers, ignored/discarded by already existing and/or incompatible clients)  Upon receipt, client could create a new temporary random public/private key pair if a server public key is included by the user in their pool configuration.

mining.authenticate (new) including that same request id in the clear plus randomized challenge text and client temporary public key both encrypted together with server public key. (sent only by compatible clients, and only in response to client.doauthenticate, should be ignored by servers that did not request an authentication with included request id, should be ignored/discarded by servers that do not support authentication, and never sent by clients respecting the extended protocol unless first requested by server)  Upon receipt, server would decrypt with server private key, extract challenge text and client temporary public key, and reencrypt the decrypted challenge text with client temporary public key)

client.authenticate (new) including that same request id (sent only from authentication enabled servers in response to mining.authenticate, ignored/discarded by already existing and/or incompatible clients)  Upon receipt, client would decrypt with its temporary private key, and validate that the challenge text is the same as sent earlier.

The rest as normal (with authentication enabled clients not receiving authentication waiting for some period before closing the stratum connection and trying again later)

mining.authorize / mining.notify / etc. with all the usual parameters as normal so as to enable any combination of older and newer clients and servers to continue communicating properly with each other.

And every so often the server should send client.doauthenticate messages again, on a schedule as determined by the pool server operator, so as in order to balance server load and efficiency, as often as possible without causing any degradation to the primary purpose of the mining pool server.  If at any point the client cannot authenticate that the server is who is claims to be, it should close the stratum connection, and try to reestablish it again from the very beginning.

At this point, some of you might wish to point out that then your miners will be left sitting idle, but if you have backup servers configured for your miners, authentication for each of them would be performed independently in parallel (at least in cgminer derivatives), and should your primary ever not properly authenticate, but your backup does authenticate, then your miner will start working on the backup pool.

Any suggestions, corrections, and/or glaring omissions on my part?

[1714244761]

1714244761

[Rock6.3]

My 15 minute WafflePool average hash rate is declining while my BAMT rig shows it is going at full speed, is there a pool problem?

[Rock6.3]

I just rebooted the main miner and it connected to my failover pool.

WafflePool appears to be down.

[ClemsonBTC]

Pool is down to 7.16GH/s and my hashrate is almost non-existant.. Did pool crash? I'm on USEast FWIW.

[utahjohn]

@COMEON
This would require co-operation with pool operators and miner devs, fwd your ideas to kalroth gmail and see if he can help implement this new strategy.

[libbyporit]

CGMiner reports all WafflePool servers are down.

[toxic0n]

Both uswest.wafflepool.com and useast.wafflepool.com are down for me

[poolwaffle]

Working on it right now, looks like a DDOS on all of our endpoints.  None of our servers have network connectivity currently.  Contacting support to see whats happening.

[utahjohn]

Both uswest.wafflepool.com and useast.wafflepool.com are down for me

ALL of my pools are reporting 0 shares yet cgminer still submitting shares.

I am using combination of failover and quota for several pools.

EDIT: multipool.us still accepting shares from my miner 3 others not alive

Checked logfile, no redirect shown

Just checked multipool frontend ... new news from them

Mar 23 9:54 PM We are still working to recover all the hot wallets lost in yesterday's hard drive crash. The MOON wallet was unfortunately corrupted, we are currently working to restore it but it may be unrecoverable. Shares for MOON will be saved until the wallet is restored or deemed unrecoverable. The MOON port is back up using a new wallet and working properly

[MrNight]

Working on it right now, looks like a DDOS on all of our endpoints.  None of our servers have network connectivity currently.  Contacting support to see whats happening.

EU server not working at this moment for me.

[romang]

This pool has really come a long way congrats.

[GalacticMiningCorp]

I've been waiting for the first real DDOS on wafflepool. Congrats, PW, you've now made the big time!

All joking aside, don't sweat it, it'll get worked out and your hard work is greatly appreciated.

[utahjohn]

This is not just a multipool waffle pool attack ALL of my cryptotroll.com pools are reporting 0 shares submitted, restarting cgminer to see if that restores but I doubt it if DDOS

No luck, waffle is not only one under attack.  multipool.us still accepting shares.

[malodin]

hi all,

total noob here, been mining on wafflepool for the past two weeks, with decent results but have some questions regarding the stalerate, since i am new to this i have not found a guide that explains all the different things in cgminer i.e. thread concurrency and intensity and all that.  I copied my build from a youtube video i am running 6 r9 270x's with a h81btc motherboard etc...  i have been successfully mining for the past two weeks using an intensity level of 20 and a thread concurrency of 24000 this seemed to have worked great for the first week and a half until the stratum change happened, now i have a stalerate of
15m Hashrate   15m Stalerate
2.21 MH/s              2.74%

is this a good number, the stale rate i see jumping all over clear up to 7%

i tried dropping the intensity level down to 17 and my hash rate stayed the same but my "Bitcoins earned (not yet sent): 0.00370838", stopped increasing as fast as it does with the 20.

the last two days i have gone from earning an average of 0.015 to less than 0.010, my most recent payout as you can see is .0079

2014-03-23 16:28:17   0.00797974
2014-03-22 23:08:36   0.01295763
2014-03-21 18:59:12   0.01042906
2014-03-20 18:55:37   0.01317510
2014-03-19 18:28:28   0.01780143


any suggestions would be greatly appreciated

2.21 sounds a bit low; I've got 5 270s (one of which is a 270x) and they run between 2.7 and 3.2 Mhs depending on how generous the hashing gods are feeling.

Definitely switch to Kalroth's cgminer. I did and using xintensity (actually raw intensity) I was able to tune those cards to give me a solid 95 - 110% WUE. A good thread on these cards with xintensity is https://bitcointalk.org/index.php?topic=459419.0

i will try kalroth's cgminer out.  originally when i set this up two weeks ago i was pulling in 2.7Mhs easilly with spikes up to 4.

[utahjohn]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator>tracert pool1.us.multipool.us

Tracing route to pool1.us.multipool.us [162.243.142.31]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  modem.Home [10.42.0.1]
  2    36 ms    20 ms    23 ms  67.41.239.68
  3    19 ms    19 ms    19 ms  slkc-agw1.inet.qwest.net [67.41.234.25]
  4    47 ms    38 ms    37 ms  snj-edge-03.inet.qwest.net [67.14.34.54]
  5    42 ms    38 ms    38 ms  65.113.42.118
  6    40 ms    37 ms    37 ms  ae0-110g.cr1.sjc1.us.nlayer.net [69.22.143.117]

  7    39 ms    58 ms    39 ms  ae1-70g.cr1.pao1.us.nlayer.net [69.22.143.166]
  8    40 ms    39 ms    47 ms  ae1-80g.cr1.sfo1.us.nlayer.net [69.22.143.169]
  9    63 ms    60 ms    60 ms  as14061.ae5-401.cr1.sfo1.us.nlayer.net [69.22.13
0.38]
 10    65 ms    66 ms    65 ms  198.199.99.242
 11    67 ms    60 ms    75 ms  proxy1.us.multipool.us [162.243.142.31]

Trace complete.

C:\Users\Administrator>tracert uswest.wafflepool.com

Tracing route to uswest.wafflepool.com [192.241.211.125]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  modem.Home [10.42.0.1]
  2    20 ms    24 ms    20 ms  67.41.239.68
  3    20 ms    20 ms    26 ms  slkc-agw1.inet.qwest.net [67.41.234.25]
  4    38 ms    38 ms    44 ms  snj-edge-03.inet.qwest.net [67.14.34.54]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *     ^C
C:\Users\Administrator>


Appears to be a major network problem however if multipool hosted on same data centers what gives?

[Rock6.3]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator>tracert pool1.us.multipool.us

Tracing route to pool1.us.multipool.us [162.243.142.31]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  modem.Home [10.42.0.1]
  2    36 ms    20 ms    23 ms  67.41.239.68
  3    19 ms    19 ms    19 ms  slkc-agw1.inet.qwest.net [67.41.234.25]
  4    47 ms    38 ms    37 ms  snj-edge-03.inet.qwest.net [67.14.34.54]
  5    42 ms    38 ms    38 ms  65.113.42.118
  6    40 ms    37 ms    37 ms  ae0-110g.cr1.sjc1.us.nlayer.net [69.22.143.117]

  7    39 ms    58 ms    39 ms  ae1-70g.cr1.pao1.us.nlayer.net [69.22.143.166]
  8    40 ms    39 ms    47 ms  ae1-80g.cr1.sfo1.us.nlayer.net [69.22.143.169]
  9    63 ms    60 ms    60 ms  as14061.ae5-401.cr1.sfo1.us.nlayer.net [69.22.13
0.38]
 10    65 ms    66 ms    65 ms  198.199.99.242
 11    67 ms    60 ms    75 ms  proxy1.us.multipool.us [162.243.142.31]

Trace complete.

C:\Users\Administrator>tracert uswest.wafflepool.com

Tracing route to uswest.wafflepool.com [192.241.211.125]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  modem.Home [10.42.0.1]
  2    20 ms    24 ms    20 ms  67.41.239.68
  3    20 ms    20 ms    26 ms  slkc-agw1.inet.qwest.net [67.41.234.25]
  4    38 ms    38 ms    44 ms  snj-edge-03.inet.qwest.net [67.14.34.54]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *     ^C
C:\Users\Administrator>


Appears to be a major network problem however if multipool hosted on same data centers what gives?

DDOS attack pointed at wafflepool stratum endpoints.

[wasubii]

I've been waiting for the first real DDOS on wafflepool. Congrats, PW, you've now made the big time!

All joking aside, don't sweat it, it'll get worked out and your hard work is greatly appreciated.

+1

[utahjohn]

cryptotroll.com pools also affected 0 shares accepted on my connection to moon.cryptotroll.com, dmd.cryptotroll.com.
restarted cgminer twice now and only 1 pool out of 4 accepting shares.

hackers SUCK ASS! LOL

at least I'm still showing shares on multipool but their 1.5% sucks when u are small time miner.

Interesting phenomena: when I restart miner I get exactly 1 share accepted to each cryptotroll pool and then nothing but my fallback (multipool) showing shares submitted.

I have changed nothing in my conf file yet

rebooting router see what happens ...

[23:30:24] Accepted 07ba8da9 Diff 33/32 GPU 1 at Pool 1
 [23:30:27] Accepted 05011f54 Diff 51/32 GPU 1 at Pool 1
 [23:30:32] Accepted 06cf3773 Diff 38/32 GPU 0 at Pool 1
 [23:30:34] Accepted 01b47fc8 Diff 150/32 GPU 0 at Pool 1
 [23:30:35] Accepted 07564a8d Diff 35/32 GPU 1 at Pool 1
 [23:30:40] Accepted 059e4a37 Diff 46/32 GPU 0 at Pool 1
 [23:30:43] Accepted 03c2af76 Diff 68/32 GPU 0 at Pool 1
 [23:30:43] Accepted 054bc8b7 Diff 48/32 GPU 1 at Pool 1
 [23:30:44] Accepted 9b4559a2 Diff 422/32 GPU 0 at Pool 1
 [23:31:07] Stratum connection to Pool 1 interrupted
 [23:31:07] Lost 14 shares due to stratum disconnect on Pool 1
 [23:31:16] Stratum connection to Pool 7 interrupted
 [23:31:17] Waiting for work to be available from pools.
 [23:31:17] Setting GPUs to idle performance.
 [23:31:19] Pool 1 not responding!
 [23:31:27] Work available from pools, resuming.
 [23:31:27] Setting GPUs back to maximum performance.
 [23:31:46] Stratum connection to Pool 8 interrupted
 [23:31:46] Stratum connection to Pool 2 interrupted
 [23:31:46] Lost 49 shares due to stratum disconnect on Pool 2
 [23:31:48] Stratum connection to Pool 4 interrupted
 [23:31:56] Waiting for work to be available from pools.
 [23:31:56] Setting GPUs to idle performance.
 [23:31:58] Pool 2 not responding!
 [23:31:58] Stratum connection to Pool 6 interrupted
 [23:32:05] Stratum connection to Pool 3 interrupted
 [23:32:14] Stratum connection to Pool 5 interrupted
 [23:32:14] Pool 5 difficulty changed to 512
 [23:32:14] Pool 5 difficulty changed to 32
 [23:32:14] Pool 6 difficulty changed to 16
 [23:32:15] Pool 7 difficulty changed to 512
 [23:32:15] Pool 7 difficulty changed to 32
 [23:32:17] Pool 3 not responding!
 [23:32:18] Pool 3 difficulty changed to 16
 [23:32:21] Work available from pools, resuming.
 [23:32:21] Setting GPUs back to maximum performance.
 [23:32:21] Accepted 0b1effba Diff 23/16 GPU 1 at Pool 3
 [23:32:22] Accepted 07ef6709 Diff 32/16 GPU 0 at Pool 3
 [23:32:22] Accepted 094fadd5 Diff 27/16 GPU 1 at Pool 3
 [23:32:22] Accepted 0e429be6 Diff 18/16 GPU 1 at Pool 3
 [23:32:23] Accepted 0b32e5ae Diff 23/16 GPU 1 at Pool 3
 [23:32:23] Accepted 088f7708 Diff 30/16 GPU 0 at Pool 3
 [23:32:23] Accepted 09f542b9 Diff 26/16 GPU 1 at Pool 3
 [23:32:24] Accepted 01ecbccd Diff 133/16 GPU 0 at Pool 3
 [23:32:25] Accepted 06329871 Diff 41/16 GPU 0 at Pool 3
 [23:32:27] Accepted 0a94d83a Diff 24/16 GPU 0 at Pool 3
 [23:32:27] Accepted 0253647e Diff 110/16 GPU 0 at Pool 3
 [23:32:27] Accepted 09ebb46e Diff 26/16 GPU 0 at Pool 3
 [23:32:28] Accepted 0a6cb83c Diff 25/16 GPU 1 at Pool 3
 [23:32:29] Accepted 0152ba06 Diff 193/16 GPU 0 at Pool 3
 [23:32:30] Accepted 04d803f6 Diff 53/16 GPU 0 at Pool 3
 [23:32:30] Accepted 0e2c6782 Diff 18/16 GPU 1 at Pool 3
 [23:32:30] Accepted 08b879c6 Diff 29/16 GPU 1 at Pool 3
 [23:32:30] Accepted 0d981f28 Diff 4.82K/16 GPU 1 at Pool 3
 [23:32:30] Accepted d5fa028b Diff 306/16 GPU 0 at Pool 3
 [23:32:30] Accepted 035dd4ae Diff 76/16 GPU 0 at Pool 3
 [23:32:31] Accepted 05001666 Diff 51/16 GPU 1 at Pool 3
 [23:32:33] Accepted 079a6908 Diff 34/16 GPU 1 at Pool 3
 [23:32:33] Accepted 0d249f55 Diff 19/16 GPU 0 at Pool 3
 [23:32:34] Accepted 071ad323 Diff 36/16 GPU 0 at Pool 3
 [23:32:34] Accepted 074a8799 Diff 35/16 GPU 0 at Pool 3
 [23:32:34] Accepted 094b345f Diff 28/16 GPU 0 at Pool 3
 [23:32:35] Accepted 04bdb13e Diff 54/16 GPU 1 at Pool 3
 [23:32:38] Accepted 6f94a241 Diff 587/16 GPU 0 at Pool 3
 [23:32:38] Accepted 85e6d79a Diff 489/16 GPU 0 at Pool 3
 [23:32:39] Accepted 074d5934 Diff 35/16 GPU 0 at Pool 3
 [23:32:40] Accepted 021b7df7 Diff 121/16 GPU 0 at Pool 3
 [23:32:40] Pool 2 difficulty changed to 8
 [23:32:41] Accepted 0ee570fc Diff 17/16 GPU 1 at Pool 3
 [23:32:42] Pool 4 difficulty changed to 512
 [23:32:42] Accepted 0505d79d Diff 51/16 GPU 1 at Pool 3
 [23:32:42] Pool 4 difficulty changed to 32
 [23:32:42] Accepted 0d7f788a Diff 19/16 GPU 1 at Pool 3
 [23:32:42] Accepted 5243188f Diff 797/16 GPU 0 at Pool 3
 [23:32:43] Accepted 0d773bba Diff 19/16 GPU 0 at Pool 3
 [23:32:43] Pool 1 difficulty changed to 512
 [23:32:43] Pool 1 difficulty changed to 32
 [23:32:43] Accepted 056f23bd Diff 47/16 GPU 0 at Pool 3
 [23:32:46] Accepted 099b7983 Diff 27/16 GPU 0 at Pool 3
 [23:32:46] Accepted 0d88f9da Diff 19/16 GPU 1 at Pool 3
 [23:32:48] Accepted 0b0f9e5a Diff 23/16 GPU 1 at Pool 3
 [23:32:48] Accepted 0d50902d Diff 19/16 GPU 0 at Pool 3
 [23:32:48] Accepted 0c4922e4 Diff 21/16 GPU 0 at Pool 3
 [23:32:49] Accepted 0acef9cb Diff 24/16 GPU 0 at Pool 3
 [23:32:49] Accepted 0340b771 Diff 79/16 GPU 1 at Pool 3
 [23:32:49] Accepted 0d94fde4 Diff 19/16 GPU 1 at Pool 3
 [23:32:49] Accepted 05b1317b Diff 45/16 GPU 0 at Pool 3
 [23:32:49] Accepted 08bef7a5 Diff 29/16 GPU 1 at Pool 3
 [23:32:50] Accepted 08e50a07 Diff 29/16 GPU 0 at Pool 3
 [23:32:51] Accepted ca69733e Diff 324/16 GPU 1 at Pool 3
 [23:32:51] Accepted 0cfecb7c Diff 20/16 GPU 0 at Pool 3
 [23:32:52] Accepted 0a3a301f Diff 25/16 GPU 0 at Pool 3
 [23:32:52] Accepted 02e5da93 Diff 88/16 GPU 1 at Pool 3
 [23:32:52] Accepted 08566d25 Diff 31/16 GPU 1 at Pool 3
 [23:32:53] Accepted 0b981a4a Diff 22/16 GPU 0 at Pool 3
 [23:32:53] Accepted 0b481458 Diff 23/16 GPU 0 at Pool 3
 [23:32:53] Accepted 03969a2f Diff 71/16 GPU 1 at Pool 3
 [23:32:53] Accepted 0e909d82 Diff 18/16 GPU 0 at Pool 3
 [23:32:54] Accepted 0424327c Diff 62/16 GPU 0 at Pool 3
 [23:32:56] Accepted 06b6eb08 Diff 38/16 GPU 0 at Pool 3
 [23:32:56] Accepted 0602f3c2 Diff 43/16 GPU 0 at Pool 3
 [23:32:57] Accepted 0c4e9934 Diff 21/16 GPU 0 at Pool 3
 [23:32:58] Accepted 060b0bb0 Diff 42/16 GPU 1 at Pool 3
 [23:33:01] Accepted 058c8c88 Diff 46/16 GPU 0 at Pool 3
 [23:33:01] Accepted 0d0ff232 Diff 20/16 GPU 1 at Pool 3
 [23:33:02] Accepted 02fb7ca8 Diff 86/16 GPU 0 at Pool 3
 [23:33:02] Accepted 037b0da5 Diff 74/16 GPU 0 at Pool 3
 [23:33:04] Accepted 018823c7 Diff 167/16 GPU 1 at Pool 3
 [23:33:08] Accepted 0d248717 Diff 19/16 GPU 1 at Pool 3
 [23:33:09] Accepted 073c84b1 Diff 35/16 GPU 1 at Pool 3
 [23:33:12] Accepted 0724962e Diff 36/32 GPU 0 at Pool 1
 [23:33:15] Accepted 016b926f Diff 180/32 GPU 0 at Pool 1
 [23:33:16] Accepted 059356f2 Diff 46/32 GPU 0 at Pool 1
 [23:33:17] Accepted 04fc52c2 Diff 51/32 GPU 0 at Pool 1
 [23:33:17] Accepted 057cbed8 Diff 47/32 GPU 0 at Pool 1
 [23:33:18] Accepted 015cc617 Diff 188/32 GPU 1 at Pool 1
 [23:33:21] Accepted 03d6b916 Diff 67/32 GPU 1 at Pool 1
 [23:33:23] Accepted 02a6f4f9 Diff 97/32 GPU 0 at Pool 1
 [23:33:25] Accepted 052f5145 Diff 49/32 GPU 0 at Pool 1
 [23:33:29] Accepted 05beb93e Diff 45/32 GPU 1 at Pool 1
 [23:33:32] Accepted 04ca4a83 Diff 53/32 GPU 0 at Pool 1
 [23:33:33] Accepted 03537a73 Diff 77/32 GPU 0 at Pool 1
 [23:33:34] Accepted 066d933e Diff 40/32 GPU 0 at Pool 1
 [23:33:36] Accepted 06e1dbf3 Diff 37/32 GPU 0 at Pool 1
 [23:33:40] Accepted 06a615ac Diff 39/32 GPU 1 at Pool 1
 [23:33:41] Accepted 02eecbb9 Diff 87/32 GPU 1 at Pool 1
 [23:33:41] Accepted 03cf4122 Diff 67/32 GPU 1 at Pool 1
 [23:33:44] Accepted 037a1968 Diff 74/32 GPU 0 at Pool 1
 [23:33:46] Accepted 011fb1c0 Diff 228/32 GPU 0 at Pool 1
 [23:33:47] Accepted 0519b53e Diff 50/32 GPU 0 at Pool 1
 [23:33:48] Accepted 07ef93fb Diff 32/32 GPU 1 at Pool 1
 [23:33:49] Accepted 07ef9bee Diff 32/32 GPU 0 at Pool 1
 [23:33:51] Accepted 0436d291 Diff 61/32 GPU 1 at Pool 1
 [23:33:51] Accepted 015dec4e Diff 187/32 GPU 0 at Pool 1
 [23:33:51] Accepted 0205c424 Diff 127/32 GPU 1 at Pool 1
 [23:33:51] Accepted 01a02103 Diff 157/32 GPU 0 at Pool 1
 [23:33:54] Accepted 02622ca3 Diff 107/32 GPU 1 at Pool 1
 [23:33:55] Accepted 0471a969 Diff 58/32 GPU 0 at Pool 1
 [23:33:59] Accepted 05f11d23 Diff 43/32 GPU 1 at Pool 1
 [23:33:59] Accepted 05e17056 Diff 44/32 GPU 1 at Pool 1
 [23:33:59] Accepted 01a298ea Diff 157/32 GPU 0 at Pool 1
 [23:34:00] Accepted 748f1462 Diff 562/32 GPU 1 at Pool 1
 [23:34:01] Accepted 02eb4e08 Diff 88/32 GPU 0 at Pool 1
 [23:34:03] Accepted 03448681 Diff 78/32 GPU 0 at Pool 1
 [23:34:03] Accepted 01752c8a Diff 176/32 GPU 0 at Pool 1
 [23:34:05] Accepted 071b9ee8 Diff 36/32 GPU 0 at Pool 1
 [23:34:06] Accepted 044b07f5 Diff 60/32 GPU 1 at Pool 1
 [23:34:06] Accepted a9a81c48 Diff 386/32 GPU 1 at Pool 1
 [23:34:08] Accepted 07068ec2 Diff 36/32 GPU 0 at Pool 1
 [23:34:09] Accepted 022283f8 Diff 120/32 GPU 1 at Pool 1

And again only one pool doing any work! wtf is going on

[utahjohn]

@KALROTH
could the patch have anything to do with breaking quota switching of pools? just a thought as I am using quota + failover-only.

Indeed it DOES! I just reverted to 20140309 version and that brought quota back to working so you need to look deeper into the 'Fix' LOL

EDIT: woops I went back to cgminer cklovas 3.7.2 but 'quota" is again working ... instant fix for my particular problem but now am vulnerable to redirect again

EDIT: 20140309 was working fine with quota too.

[wasubii]

Anyone think the Shibe-pack is behind the DDOS attacks?

They are the most agitated by the actions of multipools (what everyone else would refer to as the free market)