There have been some recent changes to the stratum code in the tpruvot yiimp - yaamp branch for handling decred. I wonder is this has has a knock on effect on the sha256 stability? It's wasn't behaving like that a month ago.
Also would be interesting to see what sort of profitability ratings you get on hashpower.co for comparison. It wouldn't be fair to compare against zpool at this point due to the sha256 drop outs (hashpower seems stable at the moment), but they mine a similar set of fast coins, so would help determine whether it's worth pointing a large amount of hash at the sha256 port. I don't mine BTC directly anymore as 65 GH/s no longer cuts it since the difficulty skyrocketed!
The problem did start not terribly long ago. I notice my antminer's green light turn off... no beeps... but I think its seeing a USB disconnect on the controller board. I have my S3 on a user set diff of 1000. When I get my S7, ill manually set it the same way to be sure that it is indeed a problem with setting that difficulty. Take this next one with a grain of salt, because I am either mining on a satellite connection, or most-likely a cellular connection which is my main. Less lag... anyways, yeah... grain of salt.... Another thing I noticed with other algos; I have to request a diff for each one. I keep noticing when I am running a diff assigned to me; it keeps getting higher and higher till I get maybe one or two hashes submitted before the next block; and it really hits me when I see my daily averages. After I finally find a good diff to set the new algo to, I see the normal share every few seconds as well as a more linear and consistent earnings chart. By far compared to working with other pools; this one has me in. I am still getting a reasonable expected and consistent profit with SHA256 gear; dispite the issues im having with what I ultimately believe to be my s3's main controller... or power surges in my rural area. I have killed a many of PSU on antminers and gridseed units. Most of them were fried from surges. Just a few fried from me running them at 95%+ of their capable output wattage. |
|
|
|
Hello , please tell me why you do not do DASH Withdraws ?
It has been discussed many times. They can only pay out as much as we mine here. So if we have LOT of people requesting DASH as a payout; we need to mine enough to TX it to them; and payments get delayed until enough DASH is mined to pay out the next round of TX... The pool doesn't buy/exchange to other coins to distribute; we only distribute mined coins; or whats sent to the exchange for BTC. This cuts down on fees drastically. Crackfoo will correct me if I am wrong in my thoughts/knowledge. |
|
|
|
I'll try and hang in there for 24 hours and see whats up
Awesome! Thanks for sharing. Ill be sure to comment my numbers as well when I hook up my S7 the first month or two. After it does good on its own for that time; Ill roll it into my main mining account because I wont care too much about seeing its profitability separate from my other devices. I just need to resist the urge to point it at CK's solo pool  With my 5TH rentals; I was typically seeing ~.018 to .028/day ± which spanned lucky and unlucky.... Which seems to line up pretty close to what you are saying; after factoring in the fact that nicehash's speed throttler is always plus or minus from the requested hashrate. Typically I saw .023/day with counting the earnings yet to be paid out. My S3 consistently is bringing around .0018-.002 a day; and when the pool is lucky; it gets close to .003; but those days are few and far between. All of my earnings are shown in BTC by the way =) |
|
|
|
I have one of my s7's on there as a test. Even with the issues; that would be excellent to know what it is bringing in each day; roughly. Its a real-world number; not a calculation based off fictitious info... kind-of what i'm after. I am working a deal with a guy that bought an S7, but he only ran it for 3-6 days because of the noise and he wants to punt it my way for a nice price. I am one of the lucky blokes that has a free connection to a 20A circuit; so I am trying to utilize it as much as possible but still have enough power to run the rest of the stuff I use everyday. I know by the math my circuit can just barely handle every bit of equipment I plan to run including the S7 But as far as real-world profitability; I will be using that to judge how long it will take to get enough generated to buy a bulk of power storage and finally hook up the stock of solar panels I have access to; to keep it running "off the grid" so to speak. I am working on a crazy design for a nearly-zero cost power generation system that isn't "solar dependent" and incorporates things like generators on petroleum products or HHO, power backup banks, etc.... But I would be taking things a step further by making my own petroleum to burn from debris and natural resources that are definitely abundant in my area. If you want to know more on this; look on youtube on how to build a still to manufacture your own crude. Its mind-numbingly simple, and opens peoples eyes as to why oil collects where it does; where it comes from, etc. Just takes the effort. With a proper plan in place; running my farm will be a nice manner of living if the whole cryptocurrency thing doesn't die a horrible death. I am also one of the people that is eagerly waiting for Tesla to begin selling the home-battery systems. That would cut the costs of the power storage side of my system significantly. |
|
|
|
|
Question; is anyone here using a single antminer S7 on this pool by itself? If so; whats the average daily, weekly or monthly earnings? A conservative or real number is fine; I am just wanting to compare to my estimates I have in my head after lots of math back and forth; plus after testing with multiple rentals beforehand..... Even better if you have a link to your wallet page to view TX history and compare to my test runs.
Thanks!
|
|
|
|
@crackfoo have you considered adding etherium? It's price has done some huge leaps and bounds today.... I've seen that some people would like less frequent payouts, to reduce the amount of tx's in wallets.
how often would you like to get paid and/or how much would you prefer the minim to be?
Cheers!
maybe a password flag for maximum payout frequency per day I.E> PO=3 (3 payouts/day), or PO=0.5(one payout every 2 days) if no flag set; keep current payout schedule. Trying to get my head around this bit of code  https://github.com/tpruvot/yiimp/blob/yiimp/web/yaamp/core/backend/stats.phpEDIT: not sure this really explains some of the issues we are seeing, but it is an example of an arbitary use of that magic missing 20%. A bit further up in the code, seems someone finds it strange too (strange calculation commented out): $pool_rate = yaamp_pool_rate($algo);
$stats->hashrate = $pool_rate; //round(($stats->hashrate*(100-$percent) + $pool_rate*$percent) / 100);
$pool_rate_bad = yaamp_pool_rate_bad($algo);
$stats->hashrate_bad = $pool_rate_bad; //round(($stats->hashrate_bad*(100-$percent) + $pool_rate_bad*$percent) / 100); So at this point it looks like a statistical reporting error somewhere I think this is what I have been mentioning before =) |
|
|
|
Same with X11 mining ... no response
Mine hasnt switched to X11; been popping between qubit, X13 and X15 mostly. X15 seems to be working fine; X13 is all crazy to hell; mostly no response from stratum or a million nonce changes in 2 seconds time. scrypt seems to have come back; and the other issue with scrypt is resolved; the stratum was sending work restarts faster than my diff level would submit a share. (low diff coin most likely). sha256 dropped off for a moment but came back as well. But for sure; something is foul with X13. every time my pc switches to it theres barely any accepted shares. Crackfoo: is there any way we can "opt out" of rental? such as a password flag like r=yes/no ? |
|
|
|
|
anyone else being sent a million nonce change requests from x13? And Scrypt seemed to stop sending my pc data...
|
|
|
|
|
yes; but when all coins/shares are coming out under your pool hashrate.... there is a missing percentage in the end.
100% in == 100% out in the end.
it's consistently lower; not varying.
If I am putting half of the pools hashrate into mining the coins; I should get half minus the 2% no matter what coins are mined.
I understand it will give more or less hashrate between coins while mining; but in that case I should have at least one coin that has a higher percentage than the others.
Instead; (guessing) my coin reward varies on the total pool hashrate up on the top right pane (not pictured); not my input hashrate on left.
If I can see what parts of my hashrate are pointed towards what coins; and a percentage thereof; it would be easier to track down where that percentage is missing from.
|
|
|
|
for all my rentals they have usually rented at 0.0044-0.0048 or so; spending ~26mBTC. Generating 19-21mBTC after the rental is up.... which is close to the amount the share reports are off by; and thats also with an extra S3 running that consistently generated 2.2mBTC/day.
The hashrate reporting is almost nominal; within a few percent; so I know those per-share hashrate calcs are good =)
sorry you pay 26 mBTC for earn 19-21? yes. Each time I calculated based on profitability reports from the pool through the day; the estimates should have been to earn 1-3mBTC after 24 hours. They obviously kept falling way short. Even on a days when rental was a lot cheaper than the previous day. I have a nagging suspicion it has to do with the major difference between pool hashrate % and share reward % that I can see on my zpool wallet page. I expected to loose out from the start; so I wasn't disappointed if I did loose coin; its not that much of a loss to help the pool try and see if there truly is an issue with the calculations somewhere. I just dont have any way else to explain away the difference between pool hashrate % (on left side where total share amount from each algo is displayed), and the share value of the coins on the right pane where it lists found blocks and credit for them. Example:  |
|
|
|
|
for all my rentals they have usually rented at 0.0044-0.0048 or so; spending ~26mBTC. Generating 19-21mBTC after the rental is up.... which is close to the amount the share reports are off by; and thats also with an extra S3 running that consistently generated 2.2mBTC/day.
The hashrate reporting is almost nominal; within a few percent; so I know those per-share hashrate calcs are good =)
|
|
|
|
|
Ive been commenting on, and still seeing the same issue: using SHA256 on my wallet I am shown as ~1.5% of the pools hashrate; but on each coins mined; I am barely seeing above 1% share credit. This is from a single S3 @ ~420Gh avg.
~80-90% credit on shares is what it seems to be when all is said and done.
Which kind of equals up to the problems I was having with rentals; renting several times for 24 hrs and not meeting the goals that were expected when calculating the profitability several times per day during that rental.. Being close to 25% of the pool hashrate; and only seeing shares close to 18-20% the entire time. I even did a large hashrate rental to be as close to 50% as possible of the pool average hashrate (renting 55Th); and only seeing 40-45% share credit.
This goes far past the 2% pool share and the NH rental fees.....
All tests were done independently; on different days, for a minimum of 24 hours to be sure its not a fluke of bad luck. Its been consistent.
Note; all rentals are from nicehash; not zpool =)
any thoughts? Anyone else seeing the same thing?
|
|
|
|
The other thing I have noticed, is once the GPU has switched to scrypt, it never seems to switch off it. Restarting the script and it chooses another algortihm. I think I will disable it for now.
for my this happens on Lyra2Re.... So I either choose to run Lyra, or not depending on how well the last half day has been. |
|
|
|
I am trying to mine on zpool.ca , but on scrypt I get diff to low, why is that? is there any other port high diff?
Thanks
My guess is possibly a miner app out of spec; that's generally been 99% of my difficulty error issues. The other would be one with nicehash, but that shouldn't happen if you follow all their directions about testing the pool. use password: d=128,scrypt notice how nicehash has a difficulty window you must be within; change my line above to a difficulty # within that range.... should work. |
|
|
|
I am trying to mine on zpool.ca , but on scrypt I get diff to low, why is that? is there any other port high diff?
Thanks
My guess is possibly a miner app out of spec; that's generally been 99% of my difficulty error issues. The other would be one with nicehash, but that shouldn't happen if you follow all their directions about testing the pool. use password: d=128,scrypt |
|
|
|
|
wow. Luck be on our side I guess!
Just making sure its all accounted for =)
|
|
|
|
crackfoo.... im not complaining... but this "spike" cant be from the amount of mining hardware I have... or luck... its too out of place.... See screenshot. I took it at roughly 17:00PST 9MBTC is quite a bit in that short time period. Any thoughts?  |
|
|
|
|
Yeah, Ive been doing a test nicehash rental to see what to expect to get at given hashrates and what I will need to hook up to hit my profit goals... just using a calculator on the spot can be misleading because luck always has a hand in such things. Saves me a step of hooking too much up at once, or not enough =)
It just kind of felt like anywhere from 5-10% of the expected share count was missing.... while trying to monitor as fairly and as accurate as possible....
Typically when I am renting; I see maybe a difference between nicehash's pane, and pool reported speed at +-0.1TH for a 5TH rental.... which a small difference is to be accepted since I am guessing the pool bases the speed mostly off the shares' freq/size ratio... But when looking at a 25TH pool; and 5TH of that is my theoretical share size; seemed low.
|
|
|
|
|
I think the SHA256 share % vs pool hashrate is pretty far off.
Running ~20TH; pool reports 45; share value ~35%...
5Th; ~1/5 pool reported hashrate; share value ~13%
maybe a math error somewhere in the code? (browser FF, shouldnt make a difference for this I would think)
|
|
|
|
|
Ive got a site suggestion:
Could you somehow display the hashrate being pointed at each coin in the display somewhere?
Maybe something along the lines of:
When you are in the wallet pane, clicking the algorythm at the right will have it expand and show the hashrate directed by your account at each coin...
Or have it down where the rest of the hashrates are displayed.
Seemed like a nice idea anyways =)
|
|
|
|
|
Show Posts
