UPDATE! As my script has grown in functionality, I decided to share it on GitHub here: https://github.com/edonkeycoin/gsbitcoinutilsOriginal post follows below... -------------------------------------------------------- I'm on a Mac, so up until recently I used Numbers as the spreadsheet application for mining ROI and other Bitcoin investment worksheets. The thing is that I wanted values in the spreadsheet to automatically update, which Numbers doesn't support. After searching for a solution, I decided to try Google Sheets. It supports automatic currency rate updates, including BTC. It also supports Javascript, so it's easy to access various blockchain info APIs. I've used this functionality to automate my spreadsheets. It's pretty cool to get notification of a mining pool payment, then open the spreadsheet and see the ROI numbers automatically recalculate. This info is probably not news to veteran forum members. Also much of this info can be found by Google searching. But in case anyone finds it helpful, I'm including the formulas and scripts that I'm using for my BTC spreadsheets. First, you can paste the following formula into a cell and it provides the current BTC/dollar rate: =GoogleFinance("CURRENCY:BTCUSD")On reddit a poster indicated that the above value comes from the Coinbase broker prices, but I have not confirmed that. For my purposes the value returned by the above function is close enough. Next, here's some simple scripts that will return information about a given bitcoin address: // Use blockr.io to receive JSON info for a given bitcoin address
function getAddressInfoJson(address)
{
var url = "https://btc.blockr.io/api/v1/address/info/" + address;
var response = UrlFetchApp.fetch(url);
var json = response.getContentText();
var parsed = JSON.parse(json);
var data = parsed.data
return data
}
// Return the total received by a bitcoin address
function walletReceived(address)
{
var data = getAddressInfoJson(address)
return data.totalreceived;
}
// Return the total transactions for a bitcoin address
function walletNumTransactions(address)
{
var data = getAddressInfoJson(address)
return data.nb_txs;
}
// Test the above functions
function test()
{
var address = "18wQtEDmhur2xAd3oE8qgrZbpCDeuMsdQW"
var received = walletReceived(address)
var numTransactions = walletNumTransactions(address)
Logger.log(address + ": ");
Logger.log(" received: " + received);
Logger.log(" transactions: " + numTransactions);
// Blocks if Safari popups blocked
//Browser.msgBox(numTransactions);
}
To use the above scripts, go to the Tools -> Script editor... page and paste the above script code and save it. Then you can go back to the spreadsheet and use the script functions. For example, to get the total received by a given address enter a formula like the following into a cell: =walletReceived("18wQtEDmhur2xAd3oE8qgrZbpCDeuMsdQW")Originally I tried using blockchain.info, because I found a script example using their API. But I started getting errors indicating that the endpoint had been used too much, or something to that effect. So I switched to blockr.io and haven't had a problem. If you want to add a new function to access different information about an address, it's pretty easy to add. Just go to the Script editor, copy one of the functions (renaming it as appropriate) and change it to return the JSON data you're interested in. You can see the list of JSON data items returned by just pasting the following URL (with your Bitcoin address) into a browser: https://btc.blockr.io/api/v1/address/info/18wQtEDmhur2xAd3oE8qgrZbpCDeuMsdQWI realize that Google isn't for everyone, especially sidehack  But if you can get past the potential privacy issues and working with a monster company like Google, the functionality they provide is very convenient.
|
|
|
|
|
+1.2 = edonkey
No, I'm not trying for the mirror image of Phil's guess. Jack (one of the kitten's we're fostering) gave me this guess.
|
|
|
|
|
Not anymore unfortunately. It's trending up.
Looks like 3.4% currently.
|
|
|
|
Posting on page 1000 was something I wanted to do.
@ kano
WTF is the fubly project prior to the one he is working on for the s-9?
You got a link?
I want to post on the 1000th page also! I hope there's room for me too! And block! Great luck today. |
|
|
|
If anyone has noticed any disconnects over the last hour or so, it seems there's some mineor internet problems around the pacific.
I've not noticed the pool hash rate change any more than usual, but a linode monitoring node keeps complaining about node and pool connections.
Very few miners should be affected, however, and they should just be reconnecting pretty much as soon as it happens.
Would this have anything to do with all my S9's going offline? I got out of bed an hour ago and noticed that all my S9's had little xxxxxxx all the way across on all hash boards. I rebooted them all and they're back up, could it be pool connection related somehow? None of my S7-LN were affected. I don't think xxxxx boards have anything to do with the pool. If there was a major disconnect to the pool, then ALL of your miners would be affected, not only s9's. Besides, your s9's would be mining at your backup pool. But I've read here and in some other threads that s9's do have some internal issues. I have only s7's so can't really say what could be the cause in your case. I've seen a problem twice now where one of my S9 boards fell over to all xxx's. It was a different board each time. The issue was temporary and resolved by a restart. In both cases I was on a profit switching multi-pool. I've never seen it happen when mining on Kano. Note that I'm running my S9s in a data center with reliable cooling and power. The chip temp of the hottest running miner's hottest board are around 87. I'm fairly sure that the issue I saw was related to low difficulty specified by the pools during fail over. At least that's what was happening at the time the board fell over. It went from around 90k difficulty to 201 on the failover, then back to 64 on the primary pool, all in the space of a minute. I'm now using a minimum difficulty on all pools in an attempt to work around the problem. Also, I'm back on Kano. My experiments with multi-pools and alts was not exactly stellar. Also there's a script floating around that can be installed on an S9 that restarts the miner if the hash rate falls below a specified value. You might want to ping aarons6 about it if you're interested. I think that the only problem with a restart script is if a board falls over permanently, which has happened to a number of forum members. If that happens then the script would keep restarting the miner every 5 minutes, which would not be helpful. |
|
|
|
|
Was there a server problem at 3:29:14 PDT (10:29 UTC, I think)?
I got a low hash rate warning email and "Connection closed" errors in the proxy log at that time.
|
|
|
|
@edonkey
Perhaps switch to ckproxy (instead of java and/or node) and set a min diff and start diff?
Thanks for the suggestion. But I can set the minimum difficulty with the Stratehm stratum-proxy, so I'm not sure what ckproxy will give me (other than being an awesome lightweight proxy). Also, I'm on an RPi. So I would probably have to build ckproxy. Not a problem, but probably more work than getting Stratehm running. |
|
|
|
I'm still waiting for the second A6, but this first one is producing extremely close to the S7s, with less noise, and it cost less. Uses 1.1KW v. 1.4.
Also awaiting...the R4 does not excite me. We'll see.
Sorry for OT, but does the Avalon require a PC for a controller? I know you were having issues getting one setup a few days ago. Hopefully an A7 can be standalone as I don't want to shell out any more cash for another PC or Raspberry (never owned a Pi). Back on topic. This is a long network block. It would be nice for us to snag it!!!!  you would need a rasp pi if it is like the avalon 4 or avalon 6 Thanks for the info. Was hoping that was not the case. Maybe the 7 will be stand-alone. I don't need anymore hardware than I already have! RPi's are a good investment. I have 3 of them, all of which are involved in mining tasks right now. I rarely have one idle. I have no problem with getting a 4th one if needed for an A7. They're inexpensive anyway. |
|
|
|
...It then gets set to 211 on kano...
...I've got around 24.7 THs... Are you talking "211" for initial diff? or running diff? According to the logs, 211 was set as the initial diff after the zpool disconnect and failing over to kano: 2016-08-25 23:03:15,975 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool zpool in 15.0 seconds.
2016-08-25 23:03:16,015 INFO [192.168.80.101-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.101 subscribed. 1 connections active on pool Kano.
2016-08-25 23:03:16,020 INFO [192.168.80.102-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.102 subscribed. 2 connections active on pool Kano.
2016-08-25 23:03:16,227 WARN [192.168.80.102-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.102. methodName: mining.multi_version, id: 56912, params: [1]
2016-08-25 23:03:16,234 WARN [192.168.80.101-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.101. methodName: mining.multi_version, id: 60712, params: [1]
2016-08-25 23:03:21,962 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 211.0 on pool Kano.
2016-08-25 23:03:21,967 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from s91@192.168.80.101 on Kano. Yeah !!!!
Moments later kano's pool starts rejecting shares at that diff: 2016-08-25 23:03:31,438 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool zpool for 30 seconds.
2016-08-25 23:03:31,447 WARN [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool zpool is UP.
2016-08-25 23:03:31,527 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 64.0 on pool zpool.
2016-08-25 23:03:31,530 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool zpool.
2016-08-25 23:03:35,710 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from s91@192.168.80.101 on Kano. Yeah !!!!
2016-08-25 23:03:37,584 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from s91@192.168.80.101 on Kano. Yeah !!!!
2016-08-25 23:03:38,646 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool zpool.
2016-08-25 23:03:38,824 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Accepted share (diff: 211.0) from s92@192.168.80.102 on Kano. Yeah !!!!
2016-08-25 23:03:46,273 INFO [Pool-Kano-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 211.0) from s91@192.168.80.101 on Kano. Booo !!!!. Error: JsonRpcError [_code=null, message=null, traceback=null]
In around a minute from the disconnect event, the proxy determined that zpool was stable and pointed back at it, so kano's pool never got an opportunity to ramp up. Zpool set the diff back to 64 (ouch) and it starts getting rejects due to "Invalid job id" errors: 2016-08-25 23:04:01,448 WARN [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Pool zpool is STABLE.
2016-08-25 23:04:01,450 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Switching worker connections from pool Kano to pool zpool.
2016-08-25 23:04:01,452 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Close connection 192.168.80.101 since the on-the-fly extranonce change is not supported.
2016-08-25 23:04:01,458 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.168.80.101 closed. 1 connections active on pool Kano. Cause: Change extranonce not supported.
2016-08-25 23:04:01,460 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Close connection 192.168.80.102 since the on-the-fly extranonce change is not supported.
2016-08-25 23:04:01,464 INFO [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.168.80.101:49375.
2016-08-25 23:04:01,471 INFO [TimerExecutorThread-3593]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.168.80.102 closed. 0 connections active on pool Kano. Cause: Change extranonce not supported.
2016-08-25 23:04:01,477 INFO [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.168.80.102:53840.
2016-08-25 23:04:01,517 INFO [192.168.80.101-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.101 subscribed. 1 connections active on pool zpool.
2016-08-25 23:04:01,521 INFO [192.168.80.102-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.168.80.102 subscribed. 2 connections active on pool zpool.
2016-08-25 23:04:03,276 WARN [192.168.80.102-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.102. methodName: mining.multi_version, id: 57067, params: [1]
2016-08-25 23:04:03,278 WARN [192.168.80.101-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection 192.168.80.101. methodName: mining.multi_version, id: 60886, params: [1]
2016-08-25 23:04:06,562 INFO [Pool-zpool-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 64.0) from s91@192.168.80.101 on zpool. Booo !!!!. Error: JsonRpcError [_code=21, message=Invalid job id, traceback=null]
Zpool started accepting shares after setting a diff of 128. Took about 8 minutes to ramp up to the full difficulty (lower than before the disconnect because one blade had fallen over at some point during the above thrashing). Note that I've changed both zpool and kano to have a minimum difficulty of 13722. Hopefully this will help with stability moving forward. |
|
|
|
Looks like my problem started happening at 23:03:15 Pacific time last night.
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
sha is set to a starting diff of 64, so I'm going to jack that up to 2000 as the majority of miners are above that anyway and I'm not going to use a x2 number as I think someone said bitmains get a bit funky when they're on a x2 diff? This should make it a bit easier on re-connecting miners with high hashrates, so they don't have to spit out so many shares at diff 64 before the diff starts to change. Thanks. That sounds like a good change. But I'm probably still going to set a minimum difficulty, just in case. I did some searching and the recommendation is around 1 per 1.8 GHs for an average of 25 shares per minute. I've got around 24.7 THs, so that works out to a minimum difficulty of around 13722. I guess I'll try that. |
|
|
|
|
Looks like my problem started happening at 23:03:15 Pacific time last night.
Near as I can tell from the logs, zpool disconnected, then the proxy failed over to Kano. There's some errors after that saying "Change extranonce not supported". Then there's a ton of rejects on kano, with a bunch of "JsonRpcError" errors that I haven't seen before.
The proxy switches back to zpool at 23:04:01 and gets a bunch of rejects with an "Invalid job id". Maybe that's old work from Kano, and expected during a pool switch.
I think that the blade fell over sometime around here because the hash rate chart for the problematic S9 seems to drop around this time.
I suspect that this problem is due to a massive shift in difficulty. The difficulty was at 93312 on zpool before the disconnect. It then gets set to 211 on kano. Then it's set to 64 on zpool. This is all in the space of a minute. It took about 8 minutes to settle out at 82944 on zpool. The fact that this is lower than before the disconnect reinforces the theory that this is when the blade fell over.
Operating under the theory that this is a Bitmain problem with difficulty swings, what minimum difficulty should I set for about 24 THs?
|
|
|
|
|
I jumped back on the pool yesterday lured by the increased profitability.
It was great until one of my S9 blades fell over again sometime over night. I woke up to the middle blade displaying all x's.
I think it happened around 11 PM Pacific time. At least the graph shows a drop off sometime around then. I'll check the logs to see if I can find an event.
This never happened on Kano.is, where I've mined since June. This is the second time that I've mined on zpool, and the second time that a blade fell over. I've restarted and pointed back at Kano and the middle blade is back and working fine.
I am using the Stratehm stratum-proxy. Doesn't seem to matter.
I have not specified a minimum difficulty. Last time this happened I think I noticed the difficulty being very low (64).
Maybe there's a Bitmain firmware problem that causes a blade to look disconnected if it runs at too low a difficulty and floods the controller with shares. Just a guess. Since Bitmain hasn't released their S9 source, no one can look at it.
Any suggestions for getting my S9s to be stable on zpool would be appreciated.
|
|
|
|
Looks like one of mine has a dead middle board. All x's
Tried lowering frequency to 575 but no luck, it comes up as o's but won't hash, then after a while goes to x's
This is a long shot, but what pool are you pointing at? I mined on Zpool briefly but ran into a problem where the pool was serving up an extremely low difficulty of 64. It would hash for a while then one of the blades would fall over and show all x's. At first I thought it might be frequency related and lowered my rate. I also tried setting a minimum difficulty. But it kept happening. Then several other people with S9s complained about the same thing on the Zpool thread, so I figured it was a pool problem. I gave up and went back to Kano's pool (should never have left) and it's been fine ever sense. I only mine on kano.is with ck's solo as a backup. Units are hosted so its going to be physically checked. These are the latest batch just had them up and running a for around 48 hours. Sorry. I thought it was a long shot. All of this is just reinforcing that Bitmain is to be avoided. Hopefully the A7 will ship soon (as per the rumors). Even if it's more expensive, it could be a better value if it's higher quality. |
|
|
|
|
Are they going to support RPi's as a controller as well? I have no experience with "Orange" Pi's.
In fact I hadn't heard of them before the related A7 posts. Had to google it.
|
|
|
|
Looks like one of mine has a dead middle board. All x's
Tried lowering frequency to 575 but no luck, it comes up as o's but won't hash, then after a while goes to x's
This is a long shot, but what pool are you pointing at? I mined on Zpool briefly but ran into a problem where the pool was serving up an extremely low difficulty of 64. It would hash for a while then one of the blades would fall over and show all x's. At first I thought it might be frequency related and lowered my rate. I also tried setting a minimum difficulty. But it kept happening. Then several other people with S9s complained about the same thing on the Zpool thread, so I figured it was a pool problem. I gave up and went back to Kano's pool (should never have left) and it's been fine ever sense. |
|
|
|
Anyone knows some Antminer S9 Monitors ?? I had M miner Monitor with the S7 but it doesn't recognize the s9  Second Question of same category: I have all my miners with a hosting company and work individually with my miners remotely through a vpn. Is there a dashboard that I can view my critical information without having to remote onto each miner? I'm about to release a product for that, maybe a month and a half more of development. We have monitoring, auto soft and hard reset and other niceties like modem/router reset on bad internet etc. No need for direct access and we will release a cloud dashboard to boot. Here's a screenshot, of a couple of small S5 farms, sorry for the spanish language, that's one of our supported languages and my interface is on that. Interesting. Does it also act as a proxy? |
|
|
|
Thanks, I actually meant 3.2 but typed 3.1 through sheer idiocy ... Either way it's probably too low. It's looking like almost 9% now. Damn... |
|
|
|
I haven't look at it, and I can't stand a language that decides code execution based on invisible characters ... so I avoid python completely ... and no that's not a complaint about your code  Just thought I'd mention that +1 on Python's idiotic reliance on indentation for delineating code blocks. Makes it a pain to copy and insert code from other developers because some (the right thinking ones) use tabs and others (the wrong thinking ones) use spaces. Yeah, I come down on the tab side in that religious war What's wrong with using explicit characters, like braces, for code blocks for crap's sake? But even with pain in the ass of having to entab and normalize text more often than I'd like, I find Python too damn useful for small scale needs. It's great for limited scripts and glue between other tools. More often than not I start writing what I thought would be a simple script in Bash, then I get over some number lines or need to do anything complex then wish I'd used Python. That said I'm glad you're not using Python for this pool. I assume that it's all compiled C, and it shows. I recently started running a proxy and it's really interesting what you see in the logs. Kano.is and the ck solo pool are both rock solid on the connection front. Literally zero disconnects. F2Pool (which I have as a third backup) shows something like 40 disconnects a day. Some other pools that I won't mention seem similarly shaky. Running a proxy has been very eye opening... If you set our pool as your third priority it is normal to have disconnect every half an hour or so because you are not submitting shares so that your connection's priority will be reduced and it may be seen as dead connection by the server as well. So you're saying that if I was submitting shares your pool would appear to suck less. Maybe. But then there's the empty blocks and whatnot. |
|
|
|
|
So a block happened whole 18 minutes ago and no one mentioned it!
Block!
|
|
|
|
|
I also have a space reserved for an A7. I was going to get another S9 but decided not to because of all the recent hardware and warranty problems that people have been seeing. I've been lucky so far with my S9s, but luck tends to run out at some point.
It's really good timing for Avalon from a public relations perspective. But I do worry that whatever they ship, Bitmain will brutally undercut them by dropping the price of the S9. There are definitely folks out there who care more about price than quality, so the cheaper S9s will sell like crazy.
I fear for the difficulty, and all of our ROIs...
|
|
|
|
|
Show Posts
