I think I found an error in cgminer version "3.12.0" this is the version bitmaintech is shipping with batch 8 antminer s3. might be on newer batches as well...
the json returned from the "stats" command is invalid.
Bitmain hacked the api output themselves to their custom output. We'll have a look but I suspect it's just due to their forked modified api output. nice, its also not backwards compatible with older versions  |
|
|
|
|
im getting a lot of discarded shares with my new s3s as well. people say they don't matter, but it seems to make a difference...
the s1 seem way more consistent.
one of my s3 bounces around 460hg to 400gh with lots of discarded... 2x more discarded than accepted...
other one stays steady at 450-460gh but with 2x more discarded than accepted shares...
|
|
|
|
new update, works with new version of the s3 now. I found a bug in cgminer 3.12.0, this is the version they are shipping with all the batch 8 s3s, and when you "upgrade" the firmware & cgminer. its returning invalid json for some/all of the API calls, I didn't test all of them. I added a workaround to make the json valid. works with my new batch 8 s3s |
|
|
|
I think I found an error in cgminer version "3.12.0" this is the version bitmaintech is shipping with batch 8 antminer s3. might be on newer batches as well... the json returned from the "stats" command is invalid. this is the json returned. {\"STATUS\":[{\"STATUS\":\"S\",\"When\":1410555313,\"Code\":70,\"Msg\":\"CGMiner stats\",\"Description\":\"cgminer 3.12.0\"}],\"STATS\":[{\"CGMiner\":\"3.12.0\",\"Miner\":\"7.0.0.3\",\"CompileTime\":\"Tue Aug 26 10:43:10 CST 2014\",\"Type\":\"S3\"}{\"STATS\":0,\"ID\":\"BMM0\",\"Elapsed\":149,\"Calls\":0,\"Wait\":0.000000,\"Max\":0.000000,\"Min\":99999999.000000,\"GHS 5s\":459.00,\"GHS av\":469.49,\"baud\":115200,\"miner_count\":2,\"asic_count\":8,\"timeout\":18,\"frequency\":\"225\",\"voltage\":5,\"hwv1\":7,\"hwv2\":0,\"hwv3\":0,\"hwv4\":3,\"fan_num\":2,\"fan1\":2520,\"fan2\":2280,\"fan3\":0,\"fan4\":0,\"fan5\":0,\"fan6\":0,\"fan7\":0,\"fan8\":0,\"fan9\":0,\"fan10\":0,\"fan11\":0,\"fan12\":0,\"fan13\":0,\"fan14\":0,\"fan15\":0,\"fan16\":0,\"temp_num\":2,\"temp1\":43,\"temp2\":41,\"temp3\":0,\"temp4\":0,\"temp5\":0,\"temp6\":0,\"temp7\":0,\"temp8\":0,\"temp9\":0,\"temp10\":0,\"temp11\":0,\"temp12\":0,\"temp13\":0,\"temp14\":0,\"temp15\":0,\"temp16\":0,\"temp_avg\":42,\"temp_max\":44,\"Device Hardware%\":0.0000,\"no_matching_work\":0,\"chain_acn1\":16,\"chain_acn2\":16,\"chain_acn3\":0,\"chain_acn4\":0,\"chain_acn5\":0,\"chain_acn6\":0,\"chain_acn7\":0,\"chain_acn8\":0,\"chain_acn9\":65535,\"chain_acn10\":0,\"chain_acn11\":0,\"chain_acn12\":0,\"chain_acn13\":0,\"chain_acn14\":0,\"chain_acn15\":0,\"chain_acn16\":0,\"chain_acs1\":\"oooooooo oooooooo \",\"chain_acs2\":\"oooooooo oooooooo \",\"chain_acs3\":\"\",\"chain_acs4\":\"\",\"chain_acs5\":\"\",\"chain_acs6\":\"\",\"chain_acs7\":\"\",\"chain_acs8\":\"\",\"chain_acs9\":\"\",\"chain_acs10\":\"\",\"chain_acs11\":\"\",\"chain_acs12\":\"\",\"chain_acs13\":\"\",\"chain_acs14\":\"\",\"chain_acs15\":\"\",\"chain_acs16\":\"\",\"USB Pipe\":\"0\"}],\"id\":1}the error is here: \"STATS\":[{\"CGMiner\":\"3.12.0\",\"Miner\":\"7.0.0.3\",\"CompileTime\":\"Tue Aug 26 10:43:10 CST 2014\",\"Type\":\"S3\"}{\"STATS\":0, its missing a comma between }{ in this part: \"S3\"}{\"STATS\":0 adding the comma makes it valid. i'll add a work around in my app. |
|
|
|
|
are there any stats for people who are selling hashpower?
|
|
|
|
|
is there a way to tell when you're pointing your miners are nice/westhash what they are doing... stats? etc??? also payouts...?
|
|
|
|
|
been running since last update without a random crash. hopefully its fine on your end.
should get my s3s sometime today to test with
|
|
|
|
|
yea I got the BTC back into a different wallet that I want to keep.
thanks for the help. lesson learned.
|
|
|
|
I uninstalled multibit as well. I will try to recover it. its my fault so I'm not mad about it AFAIK an uninstall does not remove the wallet files. E.g. for most windows versions they are in just hit win+r enter the above and hit ok. If a folder opens you might be fine. im pretty sure I had the wallet on my desktop, but I will check that folder right now ahaha thanks man I found it. it was in appdata\roaming\multibit post your BTC addy i'll send ya 20 bucks |
|
|
|
I uninstalled multibit as well. I will try to recover it. its my fault so I'm not mad about it AFAIK an uninstall does not remove the wallet files. E.g. for most windows versions they are in just hit win+r enter the above and hit ok. If a folder opens you might be fine. im pretty sure I had the wallet on my desktop, but I will check that folder right now |
|
|
|
I uninstalled multibit as well. I will try to recover it. its my fault so I'm not mad about it |
|
|
|
|
I might have fucked myself because I deleted multibit and the multibit wallet. I have some NTFS file recovery software. running it now hopefully I can recover the wallet file
|
|
|
|
I do not know how multibit works. However when bitcoin core makes an output, there will most of the time be an unspent output, which is a bitcoin address you are in control of but have never generated yourself. Since bitcoin output has to consist of a number of input, and unless the series of input matches exactly the output, then will there be an output which goes back into your "wallet". If Multibit work the same way then is 1R8iEGbocHrpq4WNYXTAMcBLCq8rMLB3G the unspent output. Are you sure you are not in control of that addy? In bitcoin core is it possible to issue the command "validateaddress" to check if you are in control of that addy. Just my 2 satoshi  ok I'll check it out. never had this behavior before when I sent transactions. |
|
|
|
its change.
your input was >1 btc but each input has to be spend entirely, thus multibit made an extra output for the rest (change). Check your addresses its one of yours.
I don't understand... I made my transaction 1 BTC exactly. |
|
|
|
|
yea I don't know how it happened really... someone got free BTC. I have no idea how that happened or who it went to...
|
|
|
|
|
Show Posts
