Topic: [POOL] GigaRho Profit-Switching Multipool (Scrypt,x11,sha256,neoscrypt,blake2s) - page 8. (Read 2821 times)

My wallet 16M2N4TEURyAPDa9jznQwpFPZ34UowPUn6  balance is stuck it does not move at all.

yep - all good. Cheers

I'll try putting a couple of the S9's to vardiff and see

Mainly just want them to be stable with temp, and not kicking off a ton of errors - the vardiff has me at 262K on the S9 and it seems to be running fairly smoothly, I assume you manually set yours to 150000. I can try that - I didn't really have a target share rate in mind. Essentially assume that if I am hashing well (solid there), efficiently (also looks ok), and not throwing a bunch of HW errors then I am fine. It's creeping back up into the low 80c on the boards and prefer to keep them in the 70's if possible. As mentioned - on Slush it hashes at 14.5 but temps in mid to low 70c.

We just did an update that applies a more proper standard difficulty to sha256. We are going to monitor this value, see what miners/equipment are connected and fine tune the value to accommodate as many devices as possible. As far as a number for the S9, I've seen many different theories on the matter personally and it has changed a bit depending on tech and year we are in. Long ago it used to be for every Terahash the device uses to multiply that number by 1024. Nicehash recommends d=1,000,000 for 100TH/s (so the scaling is a bit different) and I've seen people suggest d=262,000 for the S9 as also acceptable. There are several different S9 models as far as how much the chips were OC'd by Bitmain which leads to a more personal difficulty recommendation based on how your machine is performing in the state its in.

As far as hardware errors, I've had certain machines whose sisters produce 10x the amount of HW errors as the same model they were shipped with. A lot of it is strictly the machine and usually doesn't affect performance (MH/TH, etc) unless there is more wrong.

Awesome miner is decent for monitoring and applying changes to a vast amount of available miners. They do have online documentation that walks through API access for Antminers, I'll link it here.

Also it does appear your LTC payout went through normally.

Cheers  

Thanks for the updates.

I've set diff 15000 for the S9's now, this gives about 10 shares per minute - not sure if you had a target share rate you want to hit.

Thanks for the quick response - I really appreciate it. I assumed the payout might be timing related. Will have the other L3's up tomorrow.

I am using the native Antminer firmware so perhaps that's part of the issue. I will Look into Awesome miner - been meaning to given the number of rigs I have now (thank you solar power). The S9 is now running in the mid to high 70's which is ok. Do you suggest leaving it on Vardiff and not setting the diff manually? Still throwing quite a few errors on each board (a few hundred a day if I extrapolate). I realize HW errors are normal but the first tray a few days ago was well above that. Good thing is that it appears stable and overall error rate is 0.0006% so probably not something to worry about. Let me look into Awesome miner - have no idea how to enable API access but suspect their documentation will walk me through that.

Hello,

After looking at your account, it appears that you have been mining like you said, and around 10pm EST yesterday your balance started to mature into balance ready for payout. There haven't been any scheduled payouts since the time your balance began to mature and now. Today's payout should be in a couple of hours and include all of your balance (0.097 LTC right now). Due to the nature of the conversion process from found blocks into LTC, it takes a bit of time to confirm pending balances (usually around 24 hrs from each found block). We'll monitor the payout more closely today to ensure everything went properly and resolve anything if need be.

Next to your point about the S9s...currently the sha256 algo is sending a bunch of very small jobs to your machines instead of larger shares due to you using var diff. Originally we had several people using machines on sha256 that were still 50GH/s or so and the lower difficulty was helpful to them. We will be raising the min difficulty soon to help accommodate the S9 and hopefully that should ease some of pressure on the machine. I appreciate your feedback on that, honestly am surprised to hear about 10C hotter. Definitely want to help you fix that if we can.

At the moment I am not aware of anything on our end that would cause the L3 to behave that way when changing LTC address to BTC and password simultaneously. I personally have several L3+s pointed at the pool and have done exactly as you have tried, switching from a LTC address to BTC and back on occasion. If you are using the standard antminer firmware to handle the switch maybe something specific might happen through that? I'd recommend Awesome Miner software to manage and monitor the devices with API access enabled on each device. Keep us posted and we'll look into this further as well.

quick update - since pointing my S9 back at the SHA pool an hour ago it appears to be much more stable. i will keep an eye on it over next few days. may be some of the changes referred to earlier in the thread

Hi,

have two L3's pointed at the pool. Showing a confirmed balance of .08 LTC but no payout - been a few days. LTC -  LYaqF8K9yKMddccdaDbjqi7i5Lp7Tfw9P5

I would love to send my other 4 over your way but need to make sure the payout thing gets resolved.

I would also like to put some of my S9's and T9's on your pool. Not sure why, but your pool seems to be really hard on the S9's. Tons of HW errors and they run about 10c hotter than on Slush. That's a problem. I am using Vardiff (didn't send a d=) and extranonce so that might be it. Would love suggestions as have quite a bit of HW and the initial results look very promising, but not at the expense of frying my SHA equipment . I have one still running on 15pCpgJpRoYv6f1BY2Jsck2zBTBKvFBBRF so maybe you can see something on your end?

Also - last thing. I noticed that if I change my L3's to my BTC address and c=btc they begin to behave badly as well - lots of errors and hot. I obviously left them pointed at the Scrypt port. Any reason this would be happening? I have moved the two back to LTC and they have settled down nicely.

Thanks

Looks like the balance (in BTC) has been credited already.

Pool seems like it's off to a very promising start now.

The balance will be honored. Most of it should have matured into balance ready for payout since it has approximately been disabled for 24hrs. We need to ensure the entire process is stable for that particular coin before it can be re-enabled.

I noticed EA Coin has been removed from rotation now - so the further question is what's going to happen to the EA Coin already credited - is this going to be exchanged manually or just removed from the balances?

As we said on the pool site, a particular exchange is having deposit issues and some coins are affected until they can resolve them. As a precaution we needed to take measures to ensure everything is stable for the pool. We will be monitoring and have already cycled in UNIT and MAY to help sha256. Overall 24hr profitability still appears stable as other coins have great profit.

@GigaRho

What's happening with EA Coin? It was over 50% of all the SHA256 value mined over the past 2 days ... if it can no longer be exchanged that would be a huge hit to the pool profitability.

Actually, now I'm thinking about it 262000 is a stupidly high diff setting for the S9 ... doh

thnaks nazzer and gigarho for views.
if you have a look at the pools stats, it finds block after many minutes and keep the high profitability on almost double than others but then it comes straight down to normal figures. this will give unclear info to newbie.
i am not against the pool but to have a more reliable look and info, pool stats need to be reviewed by admin.
   Name   Amount   Difficulty   Block   Time   Status
   SaveTheOcean (x11)   400 STO   4.499 k   923 589   19m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.227 k   923 588   19m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.576 k   923 587   20m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.3 k           923 585   22m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.198 k   923 584   22m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.544 k   923 582   23m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.27 k   923 579   25m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.019 k   923 578   25m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.919 k   923 576   25m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.63 k   923 566   29m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.351 k   923 565   29m ago   Confirmed
   SaveTheOcean (x11)   400 STO   4.551 k   923 564   30m ago   Confirmed
   
i agree the effort is to find profitable coin but the above does not show that pool is looking for any other coin. it just mines one coin. if i see various profitable coins being found in other pools then it shows this pool need some improvement.

Thanks - variable diff seems to be working for me, the 24h estimated looks to be reasonably accurate.

do keep us posted, as the number of miners increase on your pool a higher diff might be preferable I'm guessing.

Our profitability calculations of the 24hr actual that you see for each algo are (total mined blocks in a 24hr period equivalent to their BTC exchange rate)/(Average total hashrate of that algorithm over 24hrs). Since the denominator of the expression is not Petahashes large, it doesn't diminish the earned results that our pool collectively finds. That being said we also optimize what offerings are available based on what hashrate the pool has online. We care about how our pool is doing and how we can bring each miner a higher result at the end of the day.

Also I should mention, the entire crypto exchange rate conversion number is extremely volatile right now because of the bear market that BTC and other cryptos are experiencing. Some of the altcoins are becoming more resilient and earning more BTC per day because BTC has shrunk >35% in a week.

Finally to your point about only one coin being mined, there are dozens available on the algo but the stratum ensures it finds the most profitable and sends most of the hashrate to the highest if it exceeds a certain percentage above other options. Each day is a different story, different coins have good days and the pool adjusts to meet that.