Search content
Sort by
Showing 20 of 135 results by wobbzz
The Z9 is not nearly as bad when running at stock clock frequency as the fan only needs to operate at about 50% capacity indoors. If you overclock to 750Mhz you're looking at increased fan speeds which will start to remind you of the S9 days, but it's still not quite as bad. Max fan speed on these is ~6100RPM.
Re: BETI: Bitcoin Exponential Trend Index and technical analysis
jl2012 could you do a quote like this for what 0.5 - 2.5 would be around August 9th 2018? I'm curious how it lines up if this fractal plays out from mid 2012 - 2014:
https://www.tradingview.com/chart/BTCUSD/YRZvdurN-The-target-of-current-bubble-lays-between-40k-and-110k/
not jl, but looking at the graphs it is clear that anything between 0 and 2 is a very short living spike as it is supra-exponential.
In all likelihood by the summer of 2018 the graph would be below zero (or fluctuating around it).
I see your point. However, the spring - winter 2013 double spike could potentially play out again. If we spike now, drop back down to 0, and back up again the timeframe would be pretty close.
Re: BETI: Bitcoin Exponential Trend Index and technical analysis
Date: 10-Dec-2017
BETI: 0.734
VWAP: 14233.61
0.5 11263.50
1.0 18570.36
1.5 30617.35
2.0 50479.48
2.5 83226.60
BETI: 0.734
VWAP: 14233.61
0.5 11263.50
1.0 18570.36
1.5 30617.35
2.0 50479.48
2.5 83226.60
jl2012 could you do a quote like this for what 0.5 - 2.5 would be around August 9th 2018? I'm curious how it lines up if this fractal plays out from mid 2012 - 2014:
https://www.tradingview.com/chart/BTCUSD/YRZvdurN-The-target-of-current-bubble-lays-between-40k-and-110k/
I'll add a reminder about that also from another recent post.
The number that matters about polling the API to see if a miner is OK, is the time since last share accepted "w_lastshareacc:N"
Here's the first worker from my API call
For any single miner, 60 seconds since last share would be the time to send an alert.
So in the above when "STAMP":"1476575097" - "w_lastshareacc:0":"1476575092" is >= 60
For a single miner, 30s is expected to happen, on average, 3 times a day.
60s is expected to happen, on average, about once every 7 years per miner.
See more details here: (and why you may want to use 120s)
https://bitcointalk.org/index.php?topic=789369.msg15998156#msg15998156
Edit: notice that there are 2 fields "w_lastshareacc:N" and "w_lastshare:N"
The "w_lastshareacc:N" field is the important one, since if your miner goes into convulsions and starts sending unacceptable shares, the other field will still update.
The number that matters about polling the API to see if a miner is OK, is the time since last share accepted "w_lastshareacc:N"
Here's the first worker from my API call
Code:
{"STAMP":"1476575097","rows":"10",
"workername:0":"Kano.A6","difficultydefault:0":"0","w_hashrate5m:0":"3178848226102.965820",
"w_hashrate1hr:0":"3113510633059.657227","w_hashrate24hr:0":"2147570918610.853516",
"w_elapsed:0":"2039775","w_lastshare:0":"1476575092","w_lastshareacc:0":"1476575092",
"w_lastdiff:0":"2496.000000","w_diffacc:0":"33527438.000000","w_diffinv:0":"113794.000000",
"w_diffsta:0":"112752.000000","w_diffdup:0":"1042.000000","w_diffhi:0":"0.000000",
"w_diffrej:0":"0.000000","w_shareacc:0":"13441.000000","w_shareinv:0":"46.000000",
"w_sharesta:0":"45.000000","w_sharedup:0":"1.000000","w_sharehi:0":"0.000000",
"w_sharerej:0":"0.000000","w_active_diffacc:0":"199680.000000","w_active_start:0":"1476574811","w_instances:0":"1",
...
"workername:0":"Kano.A6","difficultydefault:0":"0","w_hashrate5m:0":"3178848226102.965820",
"w_hashrate1hr:0":"3113510633059.657227","w_hashrate24hr:0":"2147570918610.853516",
"w_elapsed:0":"2039775","w_lastshare:0":"1476575092","w_lastshareacc:0":"1476575092",
"w_lastdiff:0":"2496.000000","w_diffacc:0":"33527438.000000","w_diffinv:0":"113794.000000",
"w_diffsta:0":"112752.000000","w_diffdup:0":"1042.000000","w_diffhi:0":"0.000000",
"w_diffrej:0":"0.000000","w_shareacc:0":"13441.000000","w_shareinv:0":"46.000000",
"w_sharesta:0":"45.000000","w_sharedup:0":"1.000000","w_sharehi:0":"0.000000",
"w_sharerej:0":"0.000000","w_active_diffacc:0":"199680.000000","w_active_start:0":"1476574811","w_instances:0":"1",
...
For any single miner, 60 seconds since last share would be the time to send an alert.
So in the above when "STAMP":"1476575097" - "w_lastshareacc:0":"1476575092" is >= 60
For a single miner, 30s is expected to happen, on average, 3 times a day.
60s is expected to happen, on average, about once every 7 years per miner.
See more details here: (and why you may want to use 120s)
https://bitcointalk.org/index.php?topic=789369.msg15998156#msg15998156
Edit: notice that there are 2 fields "w_lastshareacc:N" and "w_lastshare:N"
The "w_lastshareacc:N" field is the important one, since if your miner goes into convulsions and starts sending unacceptable shares, the other field will still update.
Thanks Kano. I remember and appreciate your input back in August, however my concern is not entirely that my miner will completely stop. It's that I'll be operating in a reduced capacity for some time and not realize it. This is why I check the hash rate, and not the time since last share. It's my understanding that even if one blade of my miner goes down, I'm still operating at 66% capacity and will be submitting shares. Would time since last share field still be a good indicator in this situation?
Interesting observation of how being offline for one hour affected my hashrate according to Kano:
10/15/2016 13:00:02 - Worker: wobbzz | 5 min: 13.277TH/s | 1 hour: 12.767TH/s | 24 hour: 12.683TH/s
10/15/2016 13:10:02 - Worker: wobbzz | 5 min: 12.460TH/s | 1 hour: 12.682TH/s | 24 hour: 12.680TH/s
10/15/2016 13:20:01 - Worker: wobbzz | 5 min: 13.855TH/s | 1 hour: 12.800TH/s | 24 hour: 12.685TH/s
10/15/2016 13:30:02 - Worker: wobbzz | 5 min: 12.804TH/s | 1 hour: 12.806TH/s | 24 hour: 12.686TH/s <- Last 10min check where I'm hashing at 100%
10/15/2016 13:40:01 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- one blade appears to have failed
10/15/2016 13:50:02 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- continued with 2 blades
wobbzz hashrate is below desired average. <- pushover notification arrived with the next API check below
10/15/2016 14:00:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- miner stopped hashing between 1350 and 1400
10/15/2016 14:10:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- apparently I
10/15/2016 14:20:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- wasn't mining
10/15/2016 14:30:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- for the last
10/15/2016 14:40:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- 24 hours
10/15/2016 14:50:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- Rebooted miner at 1452
10/15/2016 15:00:01 - Worker: wobbzz | 5 min: 10.264TH/s | 1 hour: 4.853TH/s | 24 hour: 12.035TH/s <- 24 hour hashrate credit comes back
10/15/2016 15:10:02 - Worker: wobbzz | 5 min: 12.710TH/s | 1 hour: 5.884TH/s | 24 hour: 12.035TH/s
10/15/2016 15:20:01 - Worker: wobbzz | 5 min: 13.072TH/s | 1 hour: 7.132TH/s | 24 hour: 12.048TH/s
10/15/2016 15:30:02 - Worker: wobbzz | 5 min: 14.233TH/s | 1 hour: 8.092TH/s | 24 hour: 12.055TH/s
10/15/2016 15:40:02 - Worker: wobbzz | 5 min: 12.888TH/s | 1 hour: 8.708TH/s | 24 hour: 12.057TH/s
10/15/2016 15:50:01 - Worker: wobbzz | 5 min: 14.490TH/s | 1 hour: 9.630TH/s | 24 hour: 12.075TH/s
10/15/2016 16:00:02 - Worker: wobbzz | 5 min: 14.228TH/s | 1 hour: 10.234TH/s | 24 hour: 12.084TH/s
10/15/2016 16:10:01 - Worker: wobbzz | 5 min: 13.025TH/s | 1 hour: 10.634TH/s | 24 hour: 12.091TH/s
10/15/2016 16:20:02 - Worker: wobbzz | 5 min: 13.042TH/s | 1 hour: 10.859TH/s | 24 hour: 12.090TH/s
10/15/2016 16:30:01 - Worker: wobbzz | 5 min: 13.065TH/s | 1 hour: 11.138TH/s | 24 hour: 12.093TH/s
10/15/2016 16:40:02 - Worker: wobbzz | 5 min: 12.104TH/s | 1 hour: 11.164TH/s | 24 hour: 12.088TH/s
10/15/2016 16:50:02 - Worker: wobbzz | 5 min: 13.308TH/s | 1 hour: 11.338TH/s | 24 hour: 12.088TH/s
10/15/2016 17:00:01 - Worker: wobbzz | 5 min: 12.559TH/s | 1 hour: 11.612TH/s | 24 hour: 12.096TH/s <- 2 hours later my 1hr hashrate not correct.
I don't fully understand PPLNS and don't have the time to research it right now. Does this seem correct? Would I have been paid out for 2+ blocks if they were found within the window where Kano shows my 24hr hash rate as 0?
not the right spot to look10/15/2016 13:00:02 - Worker: wobbzz | 5 min: 13.277TH/s | 1 hour: 12.767TH/s | 24 hour: 12.683TH/s
10/15/2016 13:10:02 - Worker: wobbzz | 5 min: 12.460TH/s | 1 hour: 12.682TH/s | 24 hour: 12.680TH/s
10/15/2016 13:20:01 - Worker: wobbzz | 5 min: 13.855TH/s | 1 hour: 12.800TH/s | 24 hour: 12.685TH/s
10/15/2016 13:30:02 - Worker: wobbzz | 5 min: 12.804TH/s | 1 hour: 12.806TH/s | 24 hour: 12.686TH/s <- Last 10min check where I'm hashing at 100%
10/15/2016 13:40:01 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- one blade appears to have failed
10/15/2016 13:50:02 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- continued with 2 blades
wobbzz hashrate is below desired average. <- pushover notification arrived with the next API check below
10/15/2016 14:00:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- miner stopped hashing between 1350 and 1400
10/15/2016 14:10:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- apparently I
10/15/2016 14:20:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- wasn't mining
10/15/2016 14:30:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- for the last
10/15/2016 14:40:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- 24 hours
10/15/2016 14:50:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- Rebooted miner at 1452
10/15/2016 15:00:01 - Worker: wobbzz | 5 min: 10.264TH/s | 1 hour: 4.853TH/s | 24 hour: 12.035TH/s <- 24 hour hashrate credit comes back
10/15/2016 15:10:02 - Worker: wobbzz | 5 min: 12.710TH/s | 1 hour: 5.884TH/s | 24 hour: 12.035TH/s
10/15/2016 15:20:01 - Worker: wobbzz | 5 min: 13.072TH/s | 1 hour: 7.132TH/s | 24 hour: 12.048TH/s
10/15/2016 15:30:02 - Worker: wobbzz | 5 min: 14.233TH/s | 1 hour: 8.092TH/s | 24 hour: 12.055TH/s
10/15/2016 15:40:02 - Worker: wobbzz | 5 min: 12.888TH/s | 1 hour: 8.708TH/s | 24 hour: 12.057TH/s
10/15/2016 15:50:01 - Worker: wobbzz | 5 min: 14.490TH/s | 1 hour: 9.630TH/s | 24 hour: 12.075TH/s
10/15/2016 16:00:02 - Worker: wobbzz | 5 min: 14.228TH/s | 1 hour: 10.234TH/s | 24 hour: 12.084TH/s
10/15/2016 16:10:01 - Worker: wobbzz | 5 min: 13.025TH/s | 1 hour: 10.634TH/s | 24 hour: 12.091TH/s
10/15/2016 16:20:02 - Worker: wobbzz | 5 min: 13.042TH/s | 1 hour: 10.859TH/s | 24 hour: 12.090TH/s
10/15/2016 16:30:01 - Worker: wobbzz | 5 min: 13.065TH/s | 1 hour: 11.138TH/s | 24 hour: 12.093TH/s
10/15/2016 16:40:02 - Worker: wobbzz | 5 min: 12.104TH/s | 1 hour: 11.164TH/s | 24 hour: 12.088TH/s
10/15/2016 16:50:02 - Worker: wobbzz | 5 min: 13.308TH/s | 1 hour: 11.338TH/s | 24 hour: 12.088TH/s
10/15/2016 17:00:01 - Worker: wobbzz | 5 min: 12.559TH/s | 1 hour: 11.612TH/s | 24 hour: 12.096TH/s <- 2 hours later my 1hr hashrate not correct.
I don't fully understand PPLNS and don't have the time to research it right now. Does this seem correct? Would I have been paid out for 2+ blocks if they were found within the window where Kano shows my 24hr hash rate as 0?
look here see what you have. notice I had a drop on the left .
I still was paid the drop was short/
There shouldn't be a "right spot to look". I pulled the data from the API, so it should reflect as accurately as the graph. It's raw data.
Interesting observation of how being offline for one hour affected my hashrate according to Kano:
10/15/2016 13:00:02 - Worker: wobbzz | 5 min: 13.277TH/s | 1 hour: 12.767TH/s | 24 hour: 12.683TH/s
10/15/2016 13:10:02 - Worker: wobbzz | 5 min: 12.460TH/s | 1 hour: 12.682TH/s | 24 hour: 12.680TH/s
10/15/2016 13:20:01 - Worker: wobbzz | 5 min: 13.855TH/s | 1 hour: 12.800TH/s | 24 hour: 12.685TH/s
10/15/2016 13:30:02 - Worker: wobbzz | 5 min: 12.804TH/s | 1 hour: 12.806TH/s | 24 hour: 12.686TH/s <- Last 10min check where I'm hashing at 100%
10/15/2016 13:40:01 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- one blade appears to have failed
10/15/2016 13:50:02 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- continued with 2 blades
wobbzz hashrate is below desired average. <- pushover notification arrived with the next API check below
10/15/2016 14:00:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- miner stopped hashing between 1350 and 1400
10/15/2016 14:10:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- apparently I
10/15/2016 14:20:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- wasn't mining
10/15/2016 14:30:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- for the last
10/15/2016 14:40:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- 24 hours
10/15/2016 14:50:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- Rebooted miner at 1452
10/15/2016 15:00:01 - Worker: wobbzz | 5 min: 10.264TH/s | 1 hour: 4.853TH/s | 24 hour: 12.035TH/s <- 24 hour hashrate credit comes back
10/15/2016 15:10:02 - Worker: wobbzz | 5 min: 12.710TH/s | 1 hour: 5.884TH/s | 24 hour: 12.035TH/s
10/15/2016 15:20:01 - Worker: wobbzz | 5 min: 13.072TH/s | 1 hour: 7.132TH/s | 24 hour: 12.048TH/s
10/15/2016 15:30:02 - Worker: wobbzz | 5 min: 14.233TH/s | 1 hour: 8.092TH/s | 24 hour: 12.055TH/s
10/15/2016 15:40:02 - Worker: wobbzz | 5 min: 12.888TH/s | 1 hour: 8.708TH/s | 24 hour: 12.057TH/s
10/15/2016 15:50:01 - Worker: wobbzz | 5 min: 14.490TH/s | 1 hour: 9.630TH/s | 24 hour: 12.075TH/s
10/15/2016 16:00:02 - Worker: wobbzz | 5 min: 14.228TH/s | 1 hour: 10.234TH/s | 24 hour: 12.084TH/s
10/15/2016 16:10:01 - Worker: wobbzz | 5 min: 13.025TH/s | 1 hour: 10.634TH/s | 24 hour: 12.091TH/s
10/15/2016 16:20:02 - Worker: wobbzz | 5 min: 13.042TH/s | 1 hour: 10.859TH/s | 24 hour: 12.090TH/s
10/15/2016 16:30:01 - Worker: wobbzz | 5 min: 13.065TH/s | 1 hour: 11.138TH/s | 24 hour: 12.093TH/s
10/15/2016 16:40:02 - Worker: wobbzz | 5 min: 12.104TH/s | 1 hour: 11.164TH/s | 24 hour: 12.088TH/s
10/15/2016 16:50:02 - Worker: wobbzz | 5 min: 13.308TH/s | 1 hour: 11.338TH/s | 24 hour: 12.088TH/s
10/15/2016 17:00:01 - Worker: wobbzz | 5 min: 12.559TH/s | 1 hour: 11.612TH/s | 24 hour: 12.096TH/s <- 2 hours later my 1hr hashrate not correct.
I don't fully understand PPLNS and don't have the time to research it right now. Does this seem correct? Would I have been paid out for 2+ blocks if they were found within the window where Kano shows my 24hr hash rate as 0?
10/15/2016 13:00:02 - Worker: wobbzz | 5 min: 13.277TH/s | 1 hour: 12.767TH/s | 24 hour: 12.683TH/s
10/15/2016 13:10:02 - Worker: wobbzz | 5 min: 12.460TH/s | 1 hour: 12.682TH/s | 24 hour: 12.680TH/s
10/15/2016 13:20:01 - Worker: wobbzz | 5 min: 13.855TH/s | 1 hour: 12.800TH/s | 24 hour: 12.685TH/s
10/15/2016 13:30:02 - Worker: wobbzz | 5 min: 12.804TH/s | 1 hour: 12.806TH/s | 24 hour: 12.686TH/s <- Last 10min check where I'm hashing at 100%
10/15/2016 13:40:01 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- one blade appears to have failed
10/15/2016 13:50:02 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- continued with 2 blades
wobbzz hashrate is below desired average. <- pushover notification arrived with the next API check below
10/15/2016 14:00:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- miner stopped hashing between 1350 and 1400
10/15/2016 14:10:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- apparently I
10/15/2016 14:20:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- wasn't mining
10/15/2016 14:30:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- for the last
10/15/2016 14:40:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- 24 hours
10/15/2016 14:50:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- Rebooted miner at 1452
10/15/2016 15:00:01 - Worker: wobbzz | 5 min: 10.264TH/s | 1 hour: 4.853TH/s | 24 hour: 12.035TH/s <- 24 hour hashrate credit comes back
10/15/2016 15:10:02 - Worker: wobbzz | 5 min: 12.710TH/s | 1 hour: 5.884TH/s | 24 hour: 12.035TH/s
10/15/2016 15:20:01 - Worker: wobbzz | 5 min: 13.072TH/s | 1 hour: 7.132TH/s | 24 hour: 12.048TH/s
10/15/2016 15:30:02 - Worker: wobbzz | 5 min: 14.233TH/s | 1 hour: 8.092TH/s | 24 hour: 12.055TH/s
10/15/2016 15:40:02 - Worker: wobbzz | 5 min: 12.888TH/s | 1 hour: 8.708TH/s | 24 hour: 12.057TH/s
10/15/2016 15:50:01 - Worker: wobbzz | 5 min: 14.490TH/s | 1 hour: 9.630TH/s | 24 hour: 12.075TH/s
10/15/2016 16:00:02 - Worker: wobbzz | 5 min: 14.228TH/s | 1 hour: 10.234TH/s | 24 hour: 12.084TH/s
10/15/2016 16:10:01 - Worker: wobbzz | 5 min: 13.025TH/s | 1 hour: 10.634TH/s | 24 hour: 12.091TH/s
10/15/2016 16:20:02 - Worker: wobbzz | 5 min: 13.042TH/s | 1 hour: 10.859TH/s | 24 hour: 12.090TH/s
10/15/2016 16:30:01 - Worker: wobbzz | 5 min: 13.065TH/s | 1 hour: 11.138TH/s | 24 hour: 12.093TH/s
10/15/2016 16:40:02 - Worker: wobbzz | 5 min: 12.104TH/s | 1 hour: 11.164TH/s | 24 hour: 12.088TH/s
10/15/2016 16:50:02 - Worker: wobbzz | 5 min: 13.308TH/s | 1 hour: 11.338TH/s | 24 hour: 12.088TH/s
10/15/2016 17:00:01 - Worker: wobbzz | 5 min: 12.559TH/s | 1 hour: 11.612TH/s | 24 hour: 12.096TH/s <- 2 hours later my 1hr hashrate not correct.
I don't fully understand PPLNS and don't have the time to research it right now. Does this seem correct? Would I have been paid out for 2+ blocks if they were found within the window where Kano shows my 24hr hash rate as 0?
Hey guys and gals. I wrote a python script that interacts with the Kano API and sends a pushover notification to my mobile device if my hashrate falls below X. Not sure if it would benefit anyone here.
Here's my code:
https://github.com/wobbzz/kanocheck/blob/master/checkhashrate.py
One limitation is that it uses the same hashrate check for every miner, but this could be easily changed by manually defining your workers in a dictionary.
Here's my code:
https://github.com/wobbzz/kanocheck/blob/master/checkhashrate.py
One limitation is that it uses the same hashrate check for every miner, but this could be easily changed by manually defining your workers in a dictionary.
Blockchain.info says the reward is now 16.6666666 btc lol
Tradeblock shows the correct reward balance in the coinbase tx including fees.
https://tradeblock.com/bitcoin/block/420001
Fkn antpool and their 0 tx last 25BTC block...
1Gz5TCq61UpywQXXef4qGLYTYrFi6d8YWT
The last 25 reward, mined by antpoo, they included exactly 25 btc worth of txns.
You're right, but 0.00000000 in fees lol.
I would Love for us to get the last 25 coin block!
That would be fun. I'm glad we had a nice block party right before the halving.
Block by tich13 with his 14th Kano block! That is our 5th block of the day! 
This block is loaded with .99454968 in fees! Woohoo!
This block is loaded with .99454968 in fees! Woohoo!
WOW... thats a big kahuna of fees!
I cannot imagine.... that there are pools out there that keep tx fees to themselves....
The 2nd tich13 block (419328) was hit on the Juvia shift...that lucky girl!
LOL... I hope she gives me some extra luck at solo.ckpool... I put aside some BTCs to try my luck before halving.
FYI this historic block activated the new CSV soft fork!
https://www.reddit.com/r/Bitcoin/comments/4r9wn1/csv_soft_fork_bip_68112_113_activated_on_block/
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
I gave it a shot and it works great. My S9 has been running for 10 minutes at 14.1th
What were you running before the update?11.7 to 12.3 before. 1 hour since update and at 13.9th, so I'm still happy
What's your clock rate, stabilized temps, and what batch do you have?
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
ah hemmmmm
s9-20160622-650M-for-low-voltage.tar.gz
"birdie" tells me it fixes low hasrate S9's & BEST tip is that it works across all batches but WATCH the temps.
as usual what ever you do:
DO IT AT YOUR OWN RISK !
s9-20160622-650M-for-low-voltage.tar.gz
"birdie" tells me it fixes low hasrate S9's & BEST tip is that it works across all batches but WATCH the temps.
as usual what ever you do:
DO IT AT YOUR OWN RISK !
Where do you download it?
Reference this: https://enforum.bitmain.com/bbs/topics/3554
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
ah hemmmmm
s9-20160622-650M-for-low-voltage.tar.gz
"birdie" tells me it fixes low hasrate S9's & BEST tip is that it works across all batches but WATCH the temps.
as usual what ever you do:
DO IT AT YOUR OWN RISK !
s9-20160622-650M-for-low-voltage.tar.gz
"birdie" tells me it fixes low hasrate S9's & BEST tip is that it works across all batches but WATCH the temps.
as usual what ever you do:
DO IT AT YOUR OWN RISK !
Anyone interested in trying on a B3?
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
Has anyone else seen UPS wackiness such as this? My package was originally planning to be here (the U.S.) today, but delayed a day due to customs stuff... now it seems like it's taking a boat trip around asia.... WTH And UPS is still projecting a delivery of tomorrow on the east coast. LOL
Incheon, Korea, Republic of 06/24/2016 8:13 A.M. Arrival Scan
Shenzhen, China 06/24/2016 3:35 A.M. Departure Scan
06/23/2016 10:45 A.M. The package is awaiting clearing agency review. / Your package was released by the clearing agency.
Osaka, Japan 06/23/2016 10:33 A.M. Arrival Scan
Narita, Japan 06/23/2016 9:12 A.M. Departure Scan
06/23/2016 8:25 A.M. Arrival Scan
Shenzhen, China 06/23/2016 3:07 A.M. Departure Scan
06/23/2016 1:01 A.M. Export Scan
Shenzhen, China 06/22/2016 9:29 P.M. Your package is in transit. We're updating plans to schedule your delivery. / The package will be forwarded to a UPS facility in the destination city.
06/22/2016 5:36 P.M. Your package is in transit. We're updating plans to schedule your delivery.
06/22/2016 1:00 A.M. Arrival Scan
06/22/2016 12:53 A.M. Departure Scan
06/21/2016 12:48 P.M. The package is awaiting clearing agency review. / The package is at the clearing agency awaiting final release.
Shenzhen, China 06/21/2016 11:37 P.M. Origin Scan
06/21/2016 5:06 P.M. Pickup Scan
China 06/21/2016 11:06 P.M. Order Processed: Ready for UPS
And UPS is still projecting a delivery of tomorrow on the east coast. LOLIncheon, Korea, Republic of 06/24/2016 8:13 A.M. Arrival Scan
Shenzhen, China 06/24/2016 3:35 A.M. Departure Scan
06/23/2016 10:45 A.M. The package is awaiting clearing agency review. / Your package was released by the clearing agency.
Osaka, Japan 06/23/2016 10:33 A.M. Arrival Scan
Narita, Japan 06/23/2016 9:12 A.M. Departure Scan
06/23/2016 8:25 A.M. Arrival Scan
Shenzhen, China 06/23/2016 3:07 A.M. Departure Scan
06/23/2016 1:01 A.M. Export Scan
Shenzhen, China 06/22/2016 9:29 P.M. Your package is in transit. We're updating plans to schedule your delivery. / The package will be forwarded to a UPS facility in the destination city.
06/22/2016 5:36 P.M. Your package is in transit. We're updating plans to schedule your delivery.
06/22/2016 1:00 A.M. Arrival Scan
06/22/2016 12:53 A.M. Departure Scan
06/21/2016 12:48 P.M. The package is awaiting clearing agency review. / The package is at the clearing agency awaiting final release.
Shenzhen, China 06/21/2016 11:37 P.M. Origin Scan
06/21/2016 5:06 P.M. Pickup Scan
China 06/21/2016 11:06 P.M. Order Processed: Ready for UPS
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
So confused....
Shenzhen, China 06/24/2016 3:35 A.M. Departure Scan
06/23/2016 10:45 A.M. The package is awaiting clearing agency review. / Your package was released by the clearing agency.
Osaka, Japan 06/23/2016 10:33 A.M. Arrival Scan
Narita, Japan 06/23/2016 9:12 A.M. Departure Scan
06/23/2016 8:25 A.M. Arrival Scan
Shenzhen, China 06/23/2016 3:07 A.M. Departure Scan
06/23/2016 1:01 A.M. Export Scan
Shenzhen, China 06/22/2016 9:29 P.M. Your package is in transit. We're updating plans to schedule your delivery. / The package will be forwarded to a UPS facility in the destination city.
06/22/2016 5:36 P.M. Your package is in transit. We're updating plans to schedule your delivery.
06/22/2016 1:00 A.M. Arrival Scan
06/22/2016 12:53 A.M. Departure Scan
06/21/2016 12:48 P.M. The package is awaiting clearing agency review. / The package is at the clearing agency awaiting final release.
Shenzhen, China 06/21/2016 11:37 P.M. Origin Scan
06/21/2016 5:06 P.M. Pickup Scan
China 06/21/2016 11:06 P.M. Order Processed: Ready for UPS
Shenzhen, China 06/24/2016 3:35 A.M. Departure Scan
06/23/2016 10:45 A.M. The package is awaiting clearing agency review. / Your package was released by the clearing agency.
Osaka, Japan 06/23/2016 10:33 A.M. Arrival Scan
Narita, Japan 06/23/2016 9:12 A.M. Departure Scan
06/23/2016 8:25 A.M. Arrival Scan
Shenzhen, China 06/23/2016 3:07 A.M. Departure Scan
06/23/2016 1:01 A.M. Export Scan
Shenzhen, China 06/22/2016 9:29 P.M. Your package is in transit. We're updating plans to schedule your delivery. / The package will be forwarded to a UPS facility in the destination city.
06/22/2016 5:36 P.M. Your package is in transit. We're updating plans to schedule your delivery.
06/22/2016 1:00 A.M. Arrival Scan
06/22/2016 12:53 A.M. Departure Scan
06/21/2016 12:48 P.M. The package is awaiting clearing agency review. / The package is at the clearing agency awaiting final release.
Shenzhen, China 06/21/2016 11:37 P.M. Origin Scan
06/21/2016 5:06 P.M. Pickup Scan
China 06/21/2016 11:06 P.M. Order Processed: Ready for UPS
Looks like other sites offering them at 1650 and they take PayPal
I may have to jump on that if its not much of a price diff
I may have to jump on that if its not much of a price diff
Got any links? Know anything about their reputability?
nvm, I see mybtcpool mentioned in the other thread...