|
It's not rape if you yell "Surprise!" first.
|
|
|
|
I wonder why I've never had problems looking at the pool stats with my phone, but now it says "this plug in is not supported"
Pool stats page has been changed slightly to autorefresh every 60 seconds and contains an object now instead of plain text. If you cannot access it, you can use the direct text output with this link: http://solo.ckpool.org/pool/pool.statusI'm curious why people care about the pool stats, they don't affect individual performance/ability to solve a block. Is it just curiosity factor? |
|
|
|
I hope it stays negative all summer, woo!  |
|
|
|
Quick question, can I install the last firmware antMiner_S320150109.bin on any S3 ??
One of my S3 does have the advanced setup tab.
Thanks
The latest firmware should be fine on all S3/S3+ machines. It's probably best to be on the latest, just for the fact you can easily change frequencies. Other than that no boost in performance, but the miners without the advanced tab will have a newer version of cgminer, which helps with some issues for a few pools. Kano and ck are working on an updated cgminer for the S3. They release it for the S1, S3 will come after they do the S2. Hopefully it will help with issues folks have. For example, after a restart my oc'd S3+ runs at 500gh/s and slowly decays to 480gh/s over a day or two. I doubt this has anything to do with the version of cgminer it's running, but updated software may help. |
|
|
|
I had an issue raised on git regarding the S1 API. Seems it may have been a user typing error? Anyone else seen any problem like this that they can reproduce? https://github.com/kanoi/cgminer-binaries/issues/9The API IPv6 changes by someone else were initially problematic but later fixed. So, I wasn't 100% certain if there were still any more IPv4 problems from the changes for the IPv6 code. I have no IPv4 problems with my S1 API running 4.9.1a. Here's cryptoGlance reporting my S1 via API:  |
|
|
|
|
Been running fine since it started up again last night.
It's not antivirus, and I never close core without waiting.
Yes, it could be any number of things, but the error from the log are pretty specific and I'm hoping someone can extract from that what happened.
I do not know how to run in a VM, what would that accomplish?
I always back my wallets up.
|
|
|
|
|
Payment received, thank you.
|
|
|
|
* kano looks up at how long ago he restarted the pool  lol, the restart did it! Got the notice just as I boarded my train this morning. |
|
|
|
but the blockchain is getting more and more centralized, what kills the initial concept o Bitcoin.
Uh, what? Substantiate your claim, provide proof. There are over 6100 full nodes, and more added every day. Making blocks bigger has no correlation with "centralization". |
|
|
|
And I'm really hoping we'll be able to get chips from Bitmain to make S1 refit boards or y'alls money is approximately going to waste.
If we can't get chips from them, though, we'll figure something else out. Hopefully. This project is too good to throw away.
So excited to see this happen! I have one S1 that I run solo, despite it's operating cost, I would love to upgrade it with this hardware once developed. |
|
|
|
PM sent, hope to participate again! Found a mistake in your announcement, though: ... This month's campaign is limited to 40 slots and will run from today through May 31, 2015. ... - The campaign is limited to 30 participants
|
|
|
|
|
I am using the release version, what is unstable about it?
|
|
|
|
You second link is the same one I started this thread with. |
|
|
|
Finally it was about time!
Agreed. This has been an issue for a while. I don't know enough/haven't been around long enough to know one way better than the other, but I can say that I'm glad something is happening and all the back and forth can stop. It works or it doesn't, time to find out. |
|
|
|
I am seeking knowledge trying to determine if the s3s are a viable miner, work diff 515x accepted shares 4243=diff accepted 2,185,145 in five hours and 48 minutes how can it be deterrmined if it's worth running them, power co. vig is 0.15 cents per kwh. How to Calculate Mining Profitability (can google for many more similar links): http://www.coindesk.com/information/mining-profitability/was ther a pool restart
I didn't notice one. |
|
|
|
[2015-05-05 00:57:05] Possible block solve diff 152186319981.488434 !
[2015-05-05 00:57:05] BLOCK ACCEPTED!
[2015-05-05 00:57:05] Solved and confirmed block 354990
"hashrate1m": "520T", "hashrate5m": "1.35P", "hashrate1hr": "460T", "hashrate1d": "25.4T", "hashrate7d": "4.25T", "lastupdate": 1430787761, "workers": 6
Congrats! I saw the winning address starting with "18" like my solo mining address does and I got excited for a second, but just a second. |
|
|
|
Core v0.10.1 crashed on me today, this time with an error window stating fatal internal error, see debug.log. Here is the offending entry, after which Core terminated: 2015-05-05 01:16:34 receive version message: /Satoshi:0.8.1/: version 70001, blocks=308691, us=66.215.192.104:8333, peer=1372
2015-05-05 01:16:34 Added time data, samples 200, offset -3532 (-58 minutes)
2015-05-05 01:16:34 msghand thread interrupt
2015-05-05 01:16:34 Shutdown: In progress...
2015-05-05 01:16:34 StopRPCThreads: Warning: The attempted operation is not supported for the type of object referenced when cancelling acceptorStopNode()
2015-05-05 01:16:34 Corruption: block checksum mismatch
2015-05-05 01:16:34 *** System error while flushing: Database corrupted
GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2015-05-05 01:18:26 Shutdown: In progress...
2015-05-05 01:18:26 StopNode()
2015-05-05 01:18:26 Shutdown: done
2015-05-05 01:19:37 Shutdown: done
2015-05-05 01:19:52 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed
2015-05-05 01:19:52
An hour later I tried restarting Core and got the exact same error while it was starting up and verifying blocks. I am attempting to start it again. What is this error, what caused it, and how do I fix it? Edit: This time it restarted and verified all blocks just fine. Still curious if there's any insight on the initial error(s). |
|
|
|
|
Pooling funds to solo mine a solo pool as a pool of solo miners, good stuff! /popcorn
|
|
|
|
A month has passed since the purchase  Tried powering it down for 10 minutes then restarting? Often clears a few x's. |
|
|
|
Alright, gotta clear the bench for some TypeZero module testing so I have to take down the jerry-rigged Compac prototype. After 9 days 21 hours of operation at 200MHz and 630mV (drawing 700mA from my 5V source) I have 18,700 accepted, 6 rejected and 24 HW errors off an average cgminer-calculated hashrate of 10.97GH/s. This means about a 99.8% efficiency and about 0.32W/GH which I'm okay with those numbers.
Today's tests are for the initial base design for the power systems on the TypeZero. The test build as it is should only go up to 20A on the DC output, but an extension will give me 40A capacity (more if I respec a few parts). I expect the TypeZero systems to draw at most 37A but stock setting will be more like 34A. Of course we'll build it to handle more than that just in case. Hopefully we'll see average efficiencies above 90% (ideally 95%) on this one.
Nice and clean test results, congrats! Looking forward to this project coming to fruition! |
|
|
|
|
Show Posts
