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

[comeonalready]

He'll be back. He's currently raping the ghash.io 2x reward down to 1.25 single handed... pretty sweet.

And just how is his mining at ghash.io equivalent to rape?  Would you please care to explain using some analogy including Hitler?

[1714307062]

1714307062

[1714307062]

1714307062

[1714307062]

1714307062

[comeonalready]

Now thats the whale is gone, can you please change the diff again?

at least for now, until he's back.

The difficulty was changed to 512 in order to improve the efficiency of the servers.  I don't like much it either, but that is the way is it for now.  poolwaffle would likely reduce the difficulty if situations permit, but currently they do not.

You would know this too if you searched the thread.  Search is your friend.

[maxpowerzz92]

I don't know if it's a coincidence, but our btc per MH has improved since the whale left.

[turkandjaydee]

Now thats the whale is gone, can you please change the diff again?

at least for now, until he's back.

The difficulty was changed to 512 in order to improve the efficiency of the servers.  I don't like much it either, but that is the way is it for now.  poolwaffle would likely reduce the difficulty if situations permit, but currently they do not.

You would know this too if you searched the thread.  Search is your friend.

I though the diff changed because the pool cant handle the whale,
now that it is gone, why not?

[elpsycongro]

Now thats the whale is gone, can you please change the diff again?

at least for now, until he's back.

The difficulty was changed to 512 in order to improve the efficiency of the servers.  I don't like much it either, but that is the way is it for now.  poolwaffle would likely reduce the difficulty if situations permit, but currently they do not.

You would know this too if you searched the thread.  Search is your friend.

I though the diff changed because the pool cant handle the whale,
now that it is gone, why not?

because the whale will be back soon , he comes and goes all the time , he cant predict when he will be back and the last thing we want is servers crashing.

[drexel232]

He'll be back. He's currently raping the ghash.io 2x reward down to 1.25 single handed... pretty sweet.

Yes, incredibly uncool. lol.

[drexel232]

He'll be back. He's currently raping the ghash.io 2x reward down to 1.25 single handed... pretty sweet.

And just how is his mining at ghash.io equivalent to rape?  Would you please care to explain using some analogy including Hitler?

Check out the ghash.io promo and I think you would understand 

[phzi]

because the whale will be back soon , he comes and goes all the time , he cant predict when he will be back and the last thing we want is servers crashing.

No... actually, "the whale" is a proportionately small load for the stratum server.  It's small miners that overload the server at lower difficulties.  If you want to bitch at someone about the 512 fixed diff, you should really be complaining about the people mining at <1MH and causing the majority of server load...

He'll be back. He's currently raping the ghash.io 2x reward down to 1.25 single handed... pretty sweet.

And just how is his mining at ghash.io equivalent to rape?  Would you please care to explain using some analogy including Hitler?

Check out the ghash.io promo and I think you would understand 

GHash has been sitting above 25GH fairly consistently, with or without sfire mining there.

[drexel232]

GHash has been sitting above 25GH fairly consistently, with or without sfire mining there.

Well that's just incredibly insightful. Waffle ensures no 2x reward for a very, very long time. Without them, we were getting plenty of 2x rewards.

[luthan]

GHash has been sitting above 25GH fairly consistently, with or without sfire mining there.

false, sfire is the one that put ghash over 25.  there was a hickup yesterday on ghash, where it didnt find a block for 30 minutes or so.  sfire switched back to wafflepool, ghash went below 25.

obviously, even with 1.25x, sfire deems ghash to be more profitable at this particular point.

[drexel232]

GHash has been sitting above 25GH fairly consistently, with or without sfire mining there.

false, sfire is the one that put ghash over 25.  there was a hickup yesterday on ghash, where it didnt find a block for 30 minutes or so.  sfire switched back to wafflepool, ghash went below 25.

obviously, even with 1.25x, sfire deems ghash to be more profitable at this particular point.

Can't blame a pool for seeking profits, but does not change the uncool factor for 2x lover's like me. lol. Only 2 days left, well, closer to 3.

[Starscream]

GHash has been sitting above 25GH fairly consistently, with or without sfire mining there.

That's not correct. I am following the pool on an hourly basis and I can tell you in all certainty that whoever this 20GH guy is, he's the one that gets GHash.IO above 25GH/s to 45GH/s +/-.

Pool is either <25GH/s or above 45GH/s (+/-).

[poolwaffle]

The difficulty was changed to 512 in order to improve the efficiency of the servers.  I don't like much it either, but that is the way is it for now.  poolwaffle would likely reduce the difficulty if situations permit, but currently they do not.

You would know this too if you searched the thread.  Search is your friend.

I though the diff changed because the pool cant handle the whale,
now that it is gone, why not?

Very little of it has to do with the "whale" (almost none actually), since his miners almost immediately switch to way above 512 due to the speed (they were at 1024/2048), plus, as soon as we added the d=xxx param in passwords, he immediately put that on them.

The vardiff change happened when everyone switched from MC.  Was just a matter of the server having to keep track of a few hundred miners, and all their recent shares, and mining speeds, and send difficulties out, and then all of a sudden have to handle a few thousand (right now, we're running at about 30k connections/server).  Its just too much to keep track of, and saying "nope, its 512" makes the load acceptable

[phzi]

GHash has been sitting above 25GH fairly consistently, with or without sfire mining there.

false, sfire is the one that put ghash over 25.  there was a hickup yesterday on ghash, where it didnt find a block for 30 minutes or so.  sfire switched back to wafflepool, ghash went below 25.

obviously, even with 1.25x, sfire deems ghash to be more profitable at this particular point.

You aren't watching the GHash offer as closely as I was then... sfire switched back to wafflepool after there was almost 1hr without a block found, ghash then spent a few rounds below 25GH before creeping above 25GH for over 2 hours before sfire put his hashing power back there.  

Everyone rushes to blame the whale... but really, it's ridiculous.

Pool is either <25GH/s or above 45GH/s (+/-).

So wrong... this newb can't even read the stats on the GHash.IO page FFS... At 10:02:01 the pool went over 25GH/s... it stayed there until 12:01:17 (at 1.25x bonus) when sfire moved his hashing power back there and the pool shot up to 45GH.  Small miners pushed it over the 2x bonus mark, and it has nothing to do with sfire.  Yeeesh...

Waffle ensures no 2x reward for a very, very long time. Without them, we were getting plenty of 2x rewards.

What?  Waffle isn't mining on GHash.

[poolwaffle]

You could stop accepting stales when the probability of finding a block for a particular coin falls below a threshold (50%?). This will depend on the coin's diff and pool's hashrate still on it.

Wat?

[ycsi]

The difficulty was changed to 512 in order to improve the efficiency of the servers.  I don't like much it either, but that is the way is it for now.  poolwaffle would likely reduce the difficulty if situations permit, but currently they do not.

You would know this too if you searched the thread.  Search is your friend.

I though the diff changed because the pool cant handle the whale,
now that it is gone, why not?

Very little of it has to do with the "whale" (almost none actually), since his miners almost immediately switch to way above 512 due to the speed (they were at 1024/2048), plus, as soon as we added the d=xxx param in passwords, he immediately put that on them.

The vardiff change happened when everyone switched from MC.  Was just a matter of the server having to keep track of a few hundred miners, and all their recent shares, and mining speeds, and send difficulties out, and then all of a sudden have to handle a few thousand (right now, we're running at about 30k connections/server).  Its just too much to keep track of, and saying "nope, its 512" makes the load acceptable

So, PW, was this a temporary measure until your pool's design is improved to handle more load? Or, it became a permanent "fix"?

[Starscream]

GHash has been sitting above 25GH fairly consistently, with or without sfire mining there.

false, sfire is the one that put ghash over 25.  there was a hickup yesterday on ghash, where it didnt find a block for 30 minutes or so.  sfire switched back to wafflepool, ghash went below 25.

obviously, even with 1.25x, sfire deems ghash to be more profitable at this particular point.

You aren't watching the GHash offer as closely as I was then... sfire switched back to wafflepool after there was almost 1hr without a block found, ghash then spent a few rounds below 25GH before creeping above 25GH for over 2 hours before sfire put his hashing power back there.  

Everyone rushes to blame the whale... but really, it's ridiculous.

Pool is either <25GH/s or above 45GH/s (+/-).

So wrong... this newb can't even read the stats on the GHash.IO page FFS... At 10:02:01 the pool went over 25GH/s... it stayed there until 12:01:17 (at 1.25x bonus) when sfire moved his hashing power back there and the pool shot up to 45GH.  Small miners pushed it over the 2x bonus mark, and it has nothing to do with sfire.  Yeeesh...

Waffle ensures no 2x reward for a very, very long time. Without them, we were getting plenty of 2x rewards.

What?  Waffle isn't mining on GHash.

Before you badmouth someone go fuckin do some homework scrub. Pool was on a few occasions slightly above 25GH/s. And by slightly I mean 32 times in the last 250 blocks (I actually counted it and recoded it), and it was even less than that if you'd actually been following the pool since the promotion changed to 25GH/s. 1 time the pool averaged at 36 and that's when the big guy moved in again recently.

So for you, since you're a bit retarded, 32 times out of 250 means that 12.8% of the time the pool was slightly above 25GH/s.
Rest of the time it was above 45GH/s (42% of the time) or below 25GH/s (45.2% of the time).

So yeah, sometimes the pool bonus gets shitted on by small miners but not nearly as often as it does with the big one.

Seriously, how fucking of a nut job do you need to be to reply with nothing but badmouthing to people who did nothing but respond properly to you even if disagreeing.

[poolwaffle]

The difficulty was changed to 512 in order to improve the efficiency of the servers.  I don't like much it either, but that is the way is it for now.  poolwaffle would likely reduce the difficulty if situations permit, but currently they do not.

You would know this too if you searched the thread.  Search is your friend.

I though the diff changed because the pool cant handle the whale,
now that it is gone, why not?

Very little of it has to do with the "whale" (almost none actually), since his miners almost immediately switch to way above 512 due to the speed (they were at 1024/2048), plus, as soon as we added the d=xxx param in passwords, he immediately put that on them.

The vardiff change happened when everyone switched from MC.  Was just a matter of the server having to keep track of a few hundred miners, and all their recent shares, and mining speeds, and send difficulties out, and then all of a sudden have to handle a few thousand (right now, we're running at about 30k connections/server).  Its just too much to keep track of, and saying "nope, its 512" makes the load acceptable

So, PW, was this a temporary measure until your pool's design is improved to handle more load? Or, it became a permanent "fix"?

Started out as a temporary measure, turned into more of a permanent one (at least so far).  There really isn't a ton of benefit from vardiff with a pool of this size unfortunately, even if it increases load by 5%, you're looking at another 4 servers (1 per geo region), and the only benefit is slightly more accurate stats.

[phzi]

<blah blah blah blah>

I have the full history of rounds and blocks since round 1 from GHash.IO (they have cleared stats twice), and sorry, but I am still correct.  The fact remains, sfire has yet to join GHash.IO when the pool is at a 2x bonus and therefore cause the bump to 1.25x.  The pool had consistently sat above 25GH for over 2 hours, and was showing no signs of decreasing anytime soon, when sfire last moved his power there.

Anyway, who cares... sfire would be equally as justified being pissed that he can't make 2x bonus and have everyone else leave the pool.  Guess their team just isn't as childish as some of the posters here.

---

Back on topic: WafflePool having a decent day today.

PoolWaffle: is there some stuck catcoin?  I seem to have some unconfirmed catcoin that has been sitting around for a while.  Is it just a long maturation time?

And what's up with the mintcoin we had stuck on coinmarket?  Is that just a lost cause that we can clear from the books?

[poolwaffle]

Back on topic: WafflePool having a decent day today.

PoolWaffle: is there some stuck catcoin?  I seem to have some unconfirmed catcoin that has been sitting around for a while.  Is it just a long maturation time?

And what's up with the mintcoin we had stuck on coinmarket?  Is that just a lost cause that we can clear from the books?

I think the catcoin was mined yesterday. If its not handled automatically by tomorrow I'll look into it (might just be confirming still - takes a decent bit to dig in).

As for mintcoin, still holding out hope, the guy keeps posting that he's working on getting the stuck withdrawals fixed (ours is this).  So maybe it will fix itself.  I've been holding off removing them and writing it off for now, cause its going to be a bitch to remove and then re-add.  For now, we'll wait about 1 more weke and then handle it.