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

[Radikus]

For what it's worth poolwaffle, I thought you would take the high road.  At first you didn't seem to be heading in that direction, but you seem to have changed course.  It's a difficult decision, and I really don't know which road I would take in your position.

With great power comes great responsibility.

[1714239689]

1714239689

[1714239689]

1714239689

[1714239689]

1714239689

[murraypaul]

And part of me still wants you direct 100% to ghash in order to kill the offer for the 15GH/s whale!  Because why should we be forced to back off while he reaps all the rewards!!

Why should he be forced to back off while you reap all the rewards?

[LPCobris]

And part of me still wants you direct 100% to ghash in order to kill the offer for the 15GH/s whale!  Because why should we be forced to back off while he reaps all the rewards!!

Why should he be forced to back off while you reap all the rewards?

Welll you do realize that 15ghash is simply obnoxious for scrypt right?

Im not against a miner that have 100, 200 ou even 500 mhash, but i do have when there is one sucker with 15ghash!!!

LPC

[apit.malay]

got quick question......PW said that we are mining on ghash.io....but i dont mine ltc right now...i am mining doge...so meant i didnt take part in that ghash.io ltc???and the reward for that ltc i cant get it...

[murraypaul]

And part of me still wants you direct 100% to ghash in order to kill the offer for the 15GH/s whale!  Because why should we be forced to back off while he reaps all the rewards!!

Why should he be forced to back off while you reap all the rewards?

Welll you do realize that 15ghash is simply obnoxious for scrypt right?

Im not against a miner that have 100, 200 ou even 500 mhash, but i do have when there is one sucker with 15ghash!!!

It is a game of making money.
They have invested more money in order to make more money.

[comeonalready]

Lunch time, back in about an hour (I'll be watching their stuff remotely - and can disable if needed).

Poolwaffle, I think you should experiment a bit on this ghash.io bonus situation, even if it is only out of intellectual curiosity.  I realized that the 15GH/s whale has the most control of anyone over the current hashrate at ghash.io, and I've noticed that it is staying just below 40GH/s which suggests that he may be lifting his foot off the pedal to do so.  Even if he has to reduce his participation there to 5GH/s, he would still be earning a 33% bonus over his entire 15GH/s under pool hashpower 40GH/s, which is considerably better than the alternative 25%.  So if you push the pool's pedal down a bit, he should be very willing to lift his up a bit.  Of course, you just need to be able to handle some of his hashpower returning here, and not just send more back there as a result.  Sound interesting?  Think of it less like a game of chicken and more of a dance if you prefer.  Just don't let him lead.

And it is quite convenient that cherry picking doge blocks is still an option while this promotion is underway...

[luthan]

is there a chance that this whale we all talk about is just another "multipool" that is too lazy to run his own shit?

[comeonalready]

is there a chance that this whale we all talk about is just another "multipool" that is too lazy to run his own shit?

Doesn't really matter either way.  He still controls a significant amount of hashpower.

[tumatos]

Always the same cryptos mining here, LTC and DOGE... not really Multipool..  

what's your point? I'm making 100x times more btc from these 2 coins than when we switch to mooncoin, flappycoin and those shitty coins.

[CWH]

Just a heads up guys, but WAFFLESTATS will be down probably until morning. I needed to upgrade the AWS EC2 instance and my instances keep getting AN INTERNAL SYSTEM ERROR HAS OCCURED whenever I try and launch a new instance and/or request a spot instance. What was supposed to be a simple: Backup database, stop existing instance, start new instance, reattach database turned into an hour of SYSTEM ERROR SYSTEM ERROR SYSTEM ERROR.

Sorry.

Annnnd, we're back. Sorry about that guys. Also, huge update coming tonight or tomorrow. :-)

WOW!!  AWESOME!!

Nicely done MisterWil.  Woke up to a brand new WaffleStats!

I don't got much, but listen for a *clink* in your tip jar today 

[tumatos]

the level of ungratitude towards poolwaffle work in here almost skyrocketed.

[comeonalready]

Lunch time, back in about an hour (I'll be watching their stuff remotely - and can disable if needed).

Poolwaffle, I think you should experiment a bit on this ghash.io bonus situation, even if it is only out of intellectual curiosity.  I realized that the 15GH/s whale has the most control of anyone over the current hashrate at ghash.io, and I've noticed that it is staying just below 40GH/s which suggests that he may be lifting his foot off the pedal to do so.  Even if he has to reduce his participation there to 5GH/s, he would still be earning a 33% bonus over his entire 15GH/s under pool hashpower 40GH/s, which is considerably better than the alternative 25%.  So if you push the pool's pedal down a bit, he should be very willing to lift his up a bit.  Of course, you just need to be able to handle some of his hashpower returning here, and not just send more back there as a result.  Sound interesting?  Think of it less like a game of chicken and more of a dance if you prefer.  Just don't let him lead.

Poolwaffle, I've noticed that the whale has already shifted 2 GH/s back to wafflepool presumably in an effort to keep the ghash pool hashrate under 40GH/s.  If this is true, you can force him to share more of the ghash bonuses with the pool by sending more hashpower over there, until he has about 10GH/s back here, at which point, he will likely opt for the 25% bonus on all of his hashpower and send it all back there.

My 15GH/s numbers are rough estimates at best.  You know better than anyone how much he has at his disposal.  Experiment and have some fun with this pool for a change!

[richmke]

I don't think you should bother with ghash.io. They are right up against the 40GH/s limit before the bonus is cut.

[Rock6.3]

Farm the 25% bonus please.
Take it all for team Waffle!

[comeonalready]

I don't think you should bother with ghash.io. They are right up against the 40GH/s limit before the bonus is cut.

Clearly, you missed my point entirely..

[MisterWil]

WAFFLEStats V1.0 - Summarizin' and Detailin'
Just going to get right to it:

Summary Tab
This new first page shows a stacked filled area chart for balances. This allows for a much cleaner overview of what you're currently earning than the previous line charts. It also overlays payments (green line), hashrate (red line), and the "payout threshold" which is yellow dashes.
The balances are all a shade of blue to help tone down the number of colors and to prevent overwhelming you with information. They are stacked so your "unsent" balance is now shown automatically.

The good thing about this graph is that you can see everything at a glance, but you can also turn things on and off as you so desire. Clicking the individual items in the legend will show and hide them. As such, I removed the show buttons.

Details Tab
This allows you to see your hashrate and balance/earnings details, as well as your payments. You can select the period for which it should calculate earnings. Anything else you'd like to see here just let me know and I'll try my best to add it.

Charts Tab
This is simply the old page that I left for those that like it more than what I added today. I did add payments to the balances chart.

Options
A much requested feature: NIGHTTIME MODE. This simply allows you to change the page and chart theme to a darker color so it's easier on the eyes. Much eye strain before.

Squashed Bugs and Important Changes
There were several bugs, some of which you only would have noticed were you a hashing whale. The various hashrate values now adjust for kHash, mHash, and gHash. Balances work no matter if you're earning above or below 1000btc.

I had to delete the payments history because it was storing values as local server time instead of UTC time and thus showing incorrectly on the charts. As such, I had to disable payment notifications for everyone. This was to prevent spamming the hell out of people when I turned the site back on. I'll likely re-enable them later today, but if you want to do so sooner, feel free.

Comming Soon
My todo list:

- Add currency conversion values to BTC values using the various exchange API's
- Add individual worker stats
- Cache last email time to addresses in redis to prevent spamming when database becomes unresponsive.
- Add ability to calculate time until you reach a value. For example, on the details page, select the value "0.01", and it will tell you the estimated time until you reach that amount.

That's pretty much it. Sorry for the downtime over the last few days. Database reached new massive sizes and the server had to be upgraded, and Amazon AWS was being unresponsive so I wasn't able to fix things immediately. Everything should be good now.

As always, please, consider donating. AWS is costly: I'm 15 days in to the month and my cost is $63. Holy shit, I didn't realize it was that much. Please, please, consider donating. Every little bit helps. I'll need to pull it down if I can't cover server costs with donations.

Bitcoin Address: 1Pr87ypYdG8eMTNUXR4rT1q2P1VJ7yu1b5

[LPCobris]

WAFFLEStats V1.0 - Summarizin' and Detailin'
Just going to get right to it:

Summary Tab
This new first page shows a stacked filled area chart for balances. This allows for a much cleaner overview of what you're currently earning than the previous line charts. It also overlays payments (green line), hashrate (red line), and the "payout threshold" which is yellow dashes.
The balances are all a shade of blue to help tone down the number of colors and to prevent overwhelming you with information. They are stacked so your "unsent" balance is now shown automatically.

The good thing about this graph is that you can see everything at a glance, but you can also turn things on and off as you so desire. Clicking the individual items in the legend will show and hide them. As such, I removed the show buttons.

Details Tab
This allows you to see your hashrate and balance/earnings details, as well as your payments. You can select the period for which it should calculate earnings. Anything else you'd like to see here just let me know and I'll try my best to add it.

Charts Tab
This is simply the old page that I left for those that like it more than what I added today. I did add payments to the balances chart.

Options
A much requested feature: NIGHTTIME MODE. This simply allows you to change the page and chart theme to a darker color so it's easier on the eyes. Much eye strain before.

Squashed Bugs and Important Changes
There were several bugs, some of which you only would have noticed were you a hashing whale. The various hashrate values now adjust for kHash, mHash, and gHash. Balances work no matter if you're earning above or below 1000btc.

I had to delete the payments history because it was storing values as local server time instead of UTC time and thus showing incorrectly on the charts. As such, I had to disable payment notifications for everyone. This was to prevent spamming the hell out of people when I turned the site back on. I'll likely re-enable them later today, but if you want to do so sooner, feel free.

Comming Soon
My todo list:

- Add currency conversion values to BTC values using the various exchange API's
- Add individual worker stats
- Cache last email time to addresses in redis to prevent spamming when database becomes unresponsive.
- Add ability to calculate time until you reach a value. For example, on the details page, select the value "0.01", and it will tell you the estimated time until you reach that amount.

That's pretty much it. Sorry for the downtime over the last few days. Database reached new massive sizes and the server had to be upgraded, and Amazon AWS was being unresponsive so I wasn't able to fix things immediately. Everything should be good now.

As always, please, consider donating. AWS is costly: I'm 15 days in to the month and my cost is $63. Holy shit, I didn't realize it was that much. Please, please, consider donating. Every little bit helps. I'll need to pull it down if I can't cover server costs with donations.

Bitcoin Address: 1Pr87ypYdG8eMTNUXR4rT1q2P1VJ7yu1b5

Hi M8!
Amaizing job!!

I will give you some Donation!

Also, do you need a hosting plan? I have a Hosting company, PM me with the requirements for the site, we will figure it out!

Best Regards and keep up the good work...

LPC

[MisterWil]

Hi M8!
Amaizing job!!

I will give you some Donation!

Also, do you need a hosting plan? I have a Hosting company, PM me with the requirements for the site, we will figure it out!

Best Regards and keep up the good work...

LPC

It's not so much hosting (well, it is), as it is the mongo database I'm hosting. I started using mongo because, well, it's the "new hotness", and I started this project to play with new technologies. The problem is, I didn't realize at the time that 1) This would get so popular, and 2) Mongo needs to have all data in memory for it to be at all efficient.

The database is now hosting ~8gb of data and ~4gb of indexes. I'm sure I could make that more efficient, but, well, at this point it'd be a lot more work than I think it's worth. Because of that amount of data, I need to run it on an AWS server with a LOT of ram, and those are a fair bit more expensive than the other servers I'm running. Every time I've had an issue with the site being slow, it's been because of mongo running out of ram to use.

MongoDB... only once. :-P

[luthan]

It's not so much hosting (well, it is), as it is the mongo database I'm hosting. I started using mongo because, well, it's the "new hotness", and I started this project to play with new technologies. The problem is, I didn't realize at the time that 1) This would get so popular, and 2) Mongo needs to have all data in memory for it to be at all efficient.

The database is now hosting ~8gb of data and ~4gb of indexes. I'm sure I could make that more efficient, but, well, at this point it'd be a lot more work than I think it's worth. Because of that amount of data, I need to run it on an AWS server with a LOT of ram, and those are a fair bit more expensive than the other servers I'm running. Every time I've had an issue with the site being slow, it's been because of mongo running out of ram to use.

MongoDB... only once. :-P

christ, is that just poor design or are mongo databases meant to be used for small stuff?

[MisterWil]

Both, perhaps? I'm only running a single mongodb instance and mongo REALLY shines (apparently) when you replicate it and shard it. So I'm not using it perfectly.

The largest dataset is storing each datapoint at 1 to 5 minute intervals for two weeks. There are currently 27,294,278 data points for 4500 addresses. Each datapoint is 240bytes in size.