Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 901. (Read 4382653 times)

Im not exactly sure as I've never actually hopped myself.  But I'm fairly sure they come onto the pool at the beginning of a block.  And they will stay there until the current block reaches a preset amount of shares.  Once they hit that number of shares, they move on to another pool that is just starting a block.

If they are on Slush's pool, and he finds a block within a couple minutes, I would imagine that they would hang around for the next block to see if they can cash in on that one too, but eventually they will reach that preset number of shares (or possibly preset block running time?) and move on to another pool.

If the hoppers contributed to the total share of the initial 5 minutes, they increased pool's hashrate thus contributed to the success of finding the block.

But where do those hoppers go leaving the pool? solo?

I've actually noticed a bigger difference based on the duration of the round and I'm right around 2ghash.  I'll average about .07 on most rounds, but on shorter round, generally under 5 minutes, I'll average around .03.

The only reason I haven't said anything sooner is because this conversation has come up before.  And it was generally attributed to pool hoppers.

you are right, i don't know how much people mine there and i really don't like him (and his kind)

SMPPS is not hopping-proof and is not sustainable.

Shift- versions of PPLNS and DGM are probably more scalable.

You think too slow. There's more than one 'pool of miners hoppers' out there and slush is being hopped by around 500 - 600 ghps.

You read too fast. He made a Pool of miners ... that mine on Pools ... hopping between them (MINECEPTION). => a pool of hoppers !

The solution hopefully would be using a hop proof algorithm.  Score based pools can still be hopped, tweaking the score isn't going to change that.  It may for a while and then hoppers will adapt.

Given PPLNS, SMPSS, PPS, and DGM are all well tested and hop proof prop and score based pools are an anachronism.

Goat all by himself? No. Slush gets hopped by way more than 200Ghps. There's plenty out there that do it.

https://bitcointalksearch.org/topic/hop-on-slush-pool-73920

Chaang Noi (Goat)'s fault ! He made a pool of hoppers. You can see the variation of MHASH/s on the pool on my post.

There was a long discussion on this and slush is working on a solution (new mining server).

How do you mean "people are poolhopping anyway"? When did they stop?

Yeah, same observation here. Either people are poolhopping anyway, or the algorithm is strongly favoring faster miners.

https://docs.google.com/spreadsheet/oimg?key=0AleWFOjluj4OdGl1YjY4YVZiWll3dlhicDdsYVl1SHc&oid=5&zx=8w3v5l7lvmn1

I have a problem with changes in payout according the duration of the round: on short rounds I use to get about 30% less of what I proportionally should.
See an example below. I mine 24/7 with 1.3 Ghs, so I should average: 49*(1.3/1209)= 0.05268 BTC per block, but if I calculate an average of all my BTC rewards in my statistics I obtain: 0.043032276, that is I am averaging a -18.3% BTC reward. Any comments?

#           Block found           Duration   Total shares   BTC reward   NMC reward   Block #   Validity
11487   2012-03-30 03:37:14   0:14:18   325830   0.04357108   0.06308523   173507    76 confirmations left
11486   2012-03-30 03:22:54   1:55:50   2049226   0.05579438   0.08631229   173505    74 confirmations left
11485   2012-03-30 01:26:59   0:20:21   444290   0.04840072   0.07298376   173489    58 confirmations left
11484   2012-03-30 01:06:33   0:29:37   592232   0.05507896   0.08498093   173487    56 confirmations left
11483   2012-03-30 00:36:51   0:12:00   298967   0.03900470   0.05418858   173483    52 confirmations left
11482   2012-03-30 00:24:47   0:03:21   85851   0.03839825   0.05086773   173482    51 confirmations left
11481   2012-03-30 00:21:20   3:41:41   3792749   0.05622104   0.17270344   173481    50 confirmations left
11480   2012-03-29 20:39:34   0:07:19   175538   0.03599122   0.04882444   173461    30 confirmations left
11479   2012-03-29 20:32:09   1:15:39   1341774   0.05156296   0.08062498   173459    28 confirmations left
11478   2012-03-29 19:16:27   0:46:19   847727   0.05498518   0.08458541   173456    25 confirmations left
11477   2012-03-29 18:30:03   1:09:44   1225158   0.05391265   0.33314514   173451    20 confirmations left
11476   2012-03-29 17:20:14   1:19:02   1381139   0.04807454   0.22228433   173443    12 confirmations left
11475   2012-03-29 16:01:07   1:26:14   1510379   0.05655666   0.08735242   173436    5 confirmations left
11474   2012-03-29 14:34:49   0:35:48   672898   0.05456279   0.08394135   173428    confirmed
11473   2012-03-29 13:58:55   1:39:10   1762674   0.05961002   0.36497923   173423    confirmed
11472   2012-03-29 12:19:39   1:13:45   1305626   0.05087025   0.30891315   173416    confirmed
11471   2012-03-29 11:05:48   5:54:56   5923612   0.06076420   0.93337700   173409    confirmed
11470   2012-03-29 05:10:48   0:59:41   1082071   0.05809960   0.36390045   173369    confirmed
11469   2012-03-29 04:11:05   1:05:38   1150239   0.05352829   0.08526361   173362    confirmed
11468   2012-03-29 03:05:21   1:46:35   1962498   0.05092810   0.24027354   173357    confirmed
11467   2012-03-29 01:18:41   0:12:16   304222   0.03531344   0.09733395   173348    confirmed
11466   2012-03-29 01:06:19   1:02:31   1238456   0.04634882   0.14064172   173345    confirmed
11465   2012-03-29 00:03:44   0:01:20   30763   0.03900759   0.05372267   173341    confirmed

thats the version I'm using too but I'm giving cgminer a try its fixed the cpu bug and upped my hashrate a bit too

my guiminer started having connection problems right around the 16th or 17 also. i fixed it by installing the latest version v2012-02-19

This is very interesting, but some other people come from other pools to my pool exactly because they have no 100% cpu bug with me :-). I mean - there's probably some strange issue inside guiminer which can be triggered by anything like faster/slower responses etc. I didn't changed mining part since March 16 and I even cannot imagine how can I affect this bug by change inside the pool...

Hey Slush did you make any changes to the system around March 16  I'm getting the 100% cpu bug on my miners but only using your pool it started around the 16th or early on the 17th.

See my thread here for more details https://bitcointalksearch.org/topic/100-cpu-bug-on-slushs-pool-74419

I also received notification from server provider that they're changing edge router which suddenly failed (both 10G cards, what a chance?). Traffic is now going over backup router, but I expect some routing issues during the maintenance.

Some kind of attacks are pretty common and all major pool operators have a lot of experience in fighting them :-).

Last year in summer it happened all the time. BTCGuild was attacked, Slush and Deepbit, and probably many other pools. I kept running pressing buttons and redirecting miners. It's been very calm for a long time actually. Best to have back-up pools set up for such cases that automatically take over if one pool goes down.

Off-topic: Could it be that bitmarket.eu has been subject to such an attack yesterday and today, too? It's been down for almost one day showing nothing but a white screen.