Topic: [POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com - page 279. (Read 465769 times)

Check the miner stats page (just added).  I've hidden the per-coin values (with an option to show), as they're just a TON of data, and what people really care about is bitcoins earned.  In its default place is the most recent 10 payouts for your address


I'm not sure what you mean by synchronize.  The profitability switcher switches all of the endpoints at once (give or take latency times, etc).  The stats are dumped from endpoints in batches to the main servers to handle aggregation/etc.  This happens every few seconds (10-15), and is the same delay as with the original servers (just the wafflepool.com endpoint).

Essentially the endpoints behave identically to the original endpoint, just with better geolocation.

Stats should be damn-near realtime (just like before).  All of the new endpoints are redundant as well (4x stratum servers per new endpoint).  Should something happen like the last few days (stratum server being non-responsive), we have watchdogs in place that will restart it within a minute (this will be sped up soon).

If that didn't answer your question, let me know a bit more of what you meant, so I can be of more help

Hahaha! I was going to ask that, but thought I'd let someone else open that can of worms! Considering the difference in profitability on the middlecoin servers, I'm curious to know as well.

Hi there!

Just a question from experience at middlepool: Does the new endpoints synchronize?
I'm asking because when middlepool put up a new EU endpoint, it behaved differently from the original endpoints - which was rather annoying profit wise.

Thanks for the great work on the pool so far

Don't know who created this, but it works pretty well (although slightly unstable)...

http://waffles.wilschrader.com/

On that note though, it would be nice to see historical payout data. Maybe presented the same was as the found blocks table? Not something I would look at often, but faster/easier than opening my wallet.

Is possible to obtain something to calculate or to know my earned bitcoins per day?

Testing west, thanks!

Alrighty, without further delay, the new stratum endpoints are in BETA.

These aren't being posted anywhere but in this thread, as they may fail at any time, and hopefully you guys in here will be smart enough to setup backup servers (use our normal server or someone else).

Ideally, set one of these as your primary for testing, and make sure it works for a few minutes before leaving it running for a long time (just make sure shares are tracked, etc).
stratum+tcp://useast.wafflepool.com:3333 (New York)
stratum+tcp://uswest.wafflepool.com:3333 (California)
stratum+tcp://eu.wafflepool.com:3333 (Netherlands)

These all have a ton of added protection against what we've seen over the last few days (some miners could connect, some couldn't), which was an issue with our load balancing.

Our existing server is in the same datacenter as the new USEast endpoint, so if all goes well over the next couple days, I'll put up some large notices on the site about the new endpoints, and start proxying connections from the existing location to the new useast (when that happens, people will see a short disconnect/drop in service).  But again, this is a few days out.  I'd much rather be careful with the new stuff

Capacity wise, our existing boxes would have capped out (guessing based on load) at around 3-4 GH/s.  The new boxes should be able to handle 5+ per zone with no real problem (again, this is what testing is for), so we have a ton of room for growth, and with the new configuration, adding more boxes shouldn't take much time at all (just blockchain catchup + DNS changes).

Again, these are in BETA.  If you have any issues, report back here or email me ([email protected]) and I'll get it straightened out.

I have a similar problem. One of mine computers is connected and second cannot connect...

No, there are definitely connection issues once again.

Several of my rigs are connected fine and staying connected. But two of them simply won't connect.

Poolwaffle, can you look into this? This has been happening a fair bit over the past few days for a number of users.

120 seconds sounds about right.  I am averaging about 2% rejects - where a good chunk are "Share is above target" - I haven't actually observed any other reject reason other then on the rare times 2 blocks are found within a second or two of each other.  I don't use classic intensity values - I use a tuned in xintensity on all my R9 290s that is a bit below 20 but above 19 in 2 power intensity terms, and response time for work is usually pretty low.  I have definitely observed several times the pool changing my vardiff, and then within the next 5 seconds rejecting a bunch of shares.

Are you sure there is a 30 second window?

This isn't exactly a big deal, but is a bit of an annoyance.

Overall, thanks for the awesome pool.

That shouldn't be happening.  So on the new servers (new endpoints, hopefully up soon), the vardiff will be significantly more stable, but on the existing boxes, we only change vardiff every 120 seconds, and we allow the previous vardiff to be submitted for 30 seconds after a vardiff change before rejecting shares.  Can you try dropping intensity on your miners by 1 and see if the rejected % drops?  We've seen issues with people maxing out intensity, and it submitting shares super late

Also, what % rejects are you getting?

Connected here as well.

No problems here.  Wafflepool is killing it right now, profitability and stability have been great.

Poolwaffle:  I have noticed that a lot of my rejected shares are because "Share is above target" after vardiff switches.  The vardiff varies quite a bit, so I am losing plenty of shares because of this.  Can you add a slight delay to rejecting shares as above target when vardiff just changed?  Having vardiff stabilize more would be nice too - I see switches between 128, 256, 512, and 1024 a lot on my rigs.

mmm can't connect to the pool at the moment... Is it just me or what?

Ahh. I just assumed it was tracked. No worries, no need for any extra work on something small like this!

Along the same lines of less important features, my Blocks Found table seems inaccurate.  It never shows more than 7. Also, I found 4 in the last 12 hours, but it only shows 2 having been found after Feb 1. Again, not an important feature, but I thought I'd point out the issue.

You may be correct here.  I'll have to look into it further to make sure.

Essentially, our per-coin values are tracked at an 8 digit decimal max (0.00000001), which in the case of 42coin too high when divided on a slower miner.  The btc balances (non per-coin) are done with higher precision (and on 42coin, the multiple for price puts us past the 8-decimal problem anyway), but the per-coin is getting truncated.

Essentially, you're getting paid (the btc balance is working), but the display of it isn't there.

Again, I'll check a bit deeper to make sure something isn't wrong here, but from first glance I think its working correctly.

Just a matter of going through all of the coins individually and figuring them out   We don't track them anywhere as it is, we just ask each blockchain for the status of a block (immature, confirmed, etc).

Any chance we can get # of confirms added to the block history table with required? Something like 20/50 or 20 of 50?

Still working on it.  Unfortunately not a super quick switch. Want to make sure its done right and not going to have issues


Everything looks fine here...  Time isn't a thing in confirmations, only number of blocks found.  Mooncoin is (I think) 50 blocks for immature confirmation.  Here's our last 5 blocks:
| coin     | hash                                                             | confirms | status   | value           | ctime               |
+----------+------------------------------------------------------------------+----------+----------+-----------------+---------------------+
| mooncoin | 7ca20dbb0933f4a5e16b6812c200e6b7d1c50b3079c95c5ca3f1b604ee64fab2 |       20 | immature | 1991044.3181645 | 2014-02-04 20:06:45 |
| mooncoin | 5eb71dcfb95c2d8cf8b8198cd972975f8f9bb51e47fa23e9e6cf63f0a7f88191 |       22 | immature | 1989487.2869025 | 2014-02-04 18:20:06 |
| mooncoin | 65a93a4be79502b397e739c3c196351f88be546d3d0818b3613dfef5fc0b9e53 |       27 | immature | 1606469.3227121 | 2014-02-04 13:00:39 |
| mooncoin | 3a0d22fd13a7b7bceb50538258e32821e1f24716527ef135050d6299e2129578 |       37 | immature | 1676856.1210665 | 2014-02-04 02:14:13 |
| mooncoin | bfadf7db22ccd1594339dccbc4ef216778ba2c7905d1e3e532ff545d66c0ef30 |      162 | generate |          248871 | 2014-01-31 04:40:34 |

Which looks to line up with the live stats (7mil unconfirmed).

Some update on the eu.wafflepool.com ?

Great work, and you're rewarded for it with a 1,05 GH mining pool running without disappointments.

Other question, does anybody know how long confirmation time is for Mooncoin? Have a lot their in Unconfirmed for more then a day now. Hopefully they get confirmed quick, it's some good BTC in their.

Hope to hear from you!

Greets,

Daltonganger

I was just wonder because all the other numbers are running, just 42 is all the time 0

Coin   Converted   Confirmed   Unconfirmed   Approx BTC Value
42   0.00000000   0.00000000   0.00000000   0.00000000
alphacoin   0.37126230   0.00747342   0.03114923   0.00000028
bottlecaps   0.00000000   0.00431040   0.00000000   0.00000015
…