And another block!! 537,528
[2018-08-19 16:37:09.793] Possible block solve diff 43364473479640.625000 ! [2018-08-19 16:37:09.872] BLOCK ACCEPTED! [2018-08-19 16:37:10.092] Solved block 537528 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc41x163 [2018-08-19 16:37:10.093] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "76.3P", "hashrate5m": "75.6P", "hashrate1hr": "75.4P", "hashrate1d": "75.3P", "hashrate7d": "68.4P"} [2018-08-19 16:37:10.093] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc41x163:{"hashrate1m": "16.3T", "hashrate5m": "16.8T", "hashrate1hr": "16.6T", "hashrate1d": "16.8T", "hashrate7d": "16.4T"} [2018-08-19 16:45:07.824] Hash for block height 537528 confirms block was CONFIRMED
"diff": 7.6 https://btc.com/block/537528
|
|
|
"reward": 13.05452212 "solvedby": "3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP", "date": "[2018-08-19 13:06:06.954]", "hash": "00000000000000000003d915b92e917128619467996ca7e80ec0f007b47b063d", "shares": 14070794463232, "diff": 220.2 Nice fat reward to partially make up for the luck. [2018-08-19 13:06:06.898] Possible block solve diff 73147499955421.562500 ! [2018-08-19 13:06:06.954] BLOCK ACCEPTED! [2018-08-19 13:06:06.960] Solved block 537499 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc51x27 [2018-08-19 13:06:06.960] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "75.3P", "hashrate5m": "74.6P", "hashrate1hr": "74.6P", "hashrate1d": "75.4P", "hashrate7d": "68.3P"} [2018-08-19 13:06:06.960] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc51x27:{"hashrate1m": "15.8T", "hashrate5m": "15.6T", "hashrate1hr": "16.3T", "hashrate1d": "17T", "hashrate7d": "16.4T"} [2018-08-19 13:09:46.290] Hash for block height 537499 confirms block was CONFIRMED
https://btc.com/block/537499
|
|
|
Big sushi night tonight with lots of guests. We'll see if the mining gods like Japanese...
|
|
|
It's really sweet, the updates have been really great on the website past few months.
Agree, I like the hash grid.. Just hope we get more then 1am & 1pm though It's not doing quite what I asked of Morktadela... but he has so little time he hasn't been able to address my requests.
|
|
|
Hey… we got... graphs!!!
Nice touch on the Status page...
They're still a work in progress but looking pretty good. Again it's thanks to Morktadela.
|
|
|
Block! "solvedby": "3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP", "date": "[2018-08-15 23:15:42.986]", "hash": "00000000000000000011af92a3ae894aea4fe8036b2c142a1c7986d0363adb60", "shares": 10566298511935, "diff": 165.4
Amazingly I had a console with cgminer open at the same time! Pool 0 message: Block 536951 solved by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc17x98 @ ckpool.org!
[2018-08-15 23:15:42.880] Possible block solve diff 15915038266371.863281 ! [2018-08-15 23:15:42.980] BLOCK ACCEPTED! [2018-08-15 23:15:42.991] Solved block 536951 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc17x98 [2018-08-15 23:15:42.991] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "76.2P", "hashrate5m": "75.9P", "hashrate1hr": "75.8P", "hashrate1d": "75.9P", "hashrate7d": "63.3P"} [2018-08-15 23:15:42.991] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc17x98:{"hashrate1m": "12.5T", "hashrate5m": "15.6T", "hashrate1hr": "16.9T", "hashrate1d": "16.9T", "hashrate7d": "16.4T"} [2018-08-15 23:18:15.325] Hash for block height 536951 confirms block was CONFIRMED
https://btc.com/block/536951
|
|
|
How to setup individual Difficulty for my miner?
You wait. The pool can do a better job than you. If you are using cgminer manually you can use the --suggest-diff option. what is the min/max default difficulty of the pool?
1, infinity.
|
|
|
I've tagged a new version - 4.11.0 - the first in a while. Apart from numerous small bugfixes, the main new features are the Dragonmint T1 driver and the coinbase decode option. As you're unlikely to use anything but the latter, I've summarised the basic instructions from the README here: Q: How do I use the --decode function to decode a pool's coinbase? A: You need to have a bitcoind with server functionality and pass it the credentials as the first pool in your config, and pass the pool's address that you wish to decode as the second pool configured. Note the bitcoind NEEDS the http:// prefix. e.g.: ./cgminer -o http://localhost:8332 -u user -p pass -o solo.ckpool.org:3333 -u 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ --decode EDIT: Updated to 4.11.1 for a missing bugfix and included NEWS outlining changelog.
|
|
|
When will an Intel ASIC chip board (functional miner) be available for purchase?
Never. It's not remotely in their business model and they'd be crazy to make it part of their business model.
|
|
|
Block Sunday! [2018-08-12 11:16:18.846] Possible block solve diff 32716984517849.644531 ! [2018-08-12 11:16:18.911] BLOCK ACCEPTED! [2018-08-12 11:16:19.247] Solved block 536423 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0 [2018-08-12 11:16:19.354] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "57.1P", "hashrate5m": "57.1P", "hashrate1hr": "55P", "hashrate1d": "142P", "hashrate7d": "101P"} [2018-08-12 11:16:19.354] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "57.1P", "hashrate5m": "57.1P", "hashrate1hr": "55P", "hashrate1d": "142P", "hashrate7d": "96.6P"} [2018-08-12 11:29:00.074] Hash for block height 536423 confirms block was CONFIRMED
https://btc.com/block/536423
|
|
|
I try to configure some shitcoin algo You're on your own now.
|
|
|
Hello, on some VPSes I cna't change this value. is there way so that the passthrough would be working? so it show only notice, that those values needs to changed (or recommended) ? [2018-08-12 01:23:25.541] ckpassthrough generator starting [2018-08-12 01:23:25.541] ckpassthrough stratifier starting [2018-08-12 01:23:25.541] ckpassthrough connector starting [2018-08-12 01:23:25.541] ckpassthrough connector ready [2018-08-12 01:23:25.542] ckpassthrough stratifier ready [2018-08-12 01:23:25.554] Failed to increase rcvbufsiz to 1048576, increase rmem_max or start ckpassthrough privileged [2018-08-12 01:23:25.554] Failed to increase sendbufsize to 1048576, increase wmem_max or start ckpassthrough privileged Segmentation fault
I also don't quite understand, user and password. can we skip it in the passthough mode? Since I want my rigs to set the username/password themseved? thank you Username and password is ignored in passthrough mode. The segfault is actually a recent bug and nothing to do with those privileges. I haven't had time to go and fix it so you could check out an earlier commit and use that for passthrough instead. A known good commit was 64961e4091b053935e57eabe346f59964c1bbb70 just recompiled at commit you specified commit 64961e4091b053935e57eabe346f59964c1bbb70 Propagate transactions that have reappeared after having been missing for a while to minimise risk of lost transctions in remote work.
not getting error about sysctl value, but still segfault. should I go with even earlier commit? [2018-08-12 02:45:57.565] ckpassthrough generator starting [2018-08-12 02:45:57.565] ckpassthrough stratifier starting [2018-08-12 02:45:57.565] ckpassthrough connector starting [2018-08-12 02:45:57.566] ckpassthrough connector ready [2018-08-12 02:45:57.566] ckpassthrough stratifier ready Segmentation fault Probably. The passthrough has received virtually no attention since I abandoned helping Kano's pool so it's in a sorry state I'm afraid to say since I've had no use or need for it, and no one has funded work on it.
|
|
|
Hello, on some VPSes I cna't change this value. is there way so that the passthrough would be working? so it show only notice, that those values needs to changed (or recommended) ? [2018-08-12 01:23:25.541] ckpassthrough generator starting [2018-08-12 01:23:25.541] ckpassthrough stratifier starting [2018-08-12 01:23:25.541] ckpassthrough connector starting [2018-08-12 01:23:25.541] ckpassthrough connector ready [2018-08-12 01:23:25.542] ckpassthrough stratifier ready [2018-08-12 01:23:25.554] Failed to increase rcvbufsiz to 1048576, increase rmem_max or start ckpassthrough privileged [2018-08-12 01:23:25.554] Failed to increase sendbufsize to 1048576, increase wmem_max or start ckpassthrough privileged Segmentation fault
I also don't quite understand, user and password. can we skip it in the passthough mode? Since I want my rigs to set the username/password themseved? thank you Username and password is ignored in passthrough mode. The segfault is actually a recent bug and nothing to do with those privileges. I haven't had time to go and fix it so you could check out an earlier commit and use that for passthrough instead. A known good commit was 64961e4091b053935e57eabe346f59964c1bbb70
|
|
|
Have we been higher than 360 PH before?
We hit over 500 with that other pool failover, but this looks consistent (and hopefully staying?)
|
|
|
Inno is burning in here?
No idea since I'm not doing any work for them. I hope so?
|
|
|
We have a block!!
"solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V", "date": "[2018-08-08 16:25:26.087]", "hash": "000000000000000000125fbad99dac0f8387d019474a241f83591e4df04c9e10", "shares": 10628422869592, "diff": 178.6 finally and "height": 535814 "solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V", "date": "[2018-08-08 17:47:25.662]", "hash": "00000000000000000014054b25ce24cba0ed0418870e494d16fa3a6f869824b7", "shares": 296254077420, "diff": 5.0 [2018-08-08 16:25:26.051] Possible block solve diff 15319012000641.765625 ! [2018-08-08 16:25:26.068] BLOCK ACCEPTED! [2018-08-08 16:25:26.240] Solved block 535805 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0 [2018-08-08 16:25:26.240] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "109P", "hashrate5m": "112P", "hashrate1hr": "107P", "hashrate1d": "93.3P", "hashrate7d": "76.1P"} [2018-08-08 16:25:26.240] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "109P", "hashrate5m": "112P", "hashrate1hr": "107P", "hashrate1d": "92.3P", "hashrate7d": "68.8P"} [2018-08-08 16:27:31.517] Hash for block height 535805 confirms block was CONFIRMED [2018-08-08 17:47:25.540] Possible block solve diff 14058998550041.402344 ! [2018-08-08 17:47:25.649] BLOCK ACCEPTED! [2018-08-08 17:47:26.189] Solved block 535814 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0 [2018-08-08 17:47:26.326] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "134P", "hashrate5m": "134P", "hashrate1hr": "124P", "hashrate1d": "95.3P", "hashrate7d": "76.5P"} [2018-08-08 17:47:26.326] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "134P", "hashrate5m": "133P", "hashrate1hr": "124P", "hashrate1d": "94.3P", "hashrate7d": "69.3P"} [2018-08-08 17:58:30.239] Hash for block height 535814 confirms block was CONFIRMED
https://btc.com/block/535805https://btc.com/block/535814
|
|
|
Is there any way to make these, T2T, less noisy? I've turned mine right down to efficency setting and still it is running very loud. Update the firmware as well but I think the wife might murder me if I can't make it quieter.
The problem is that even if you mine at subzero temperatures and the miner itself runs cool not needing high fanspeed, the PSU that's built into these still runs its fans flat out and they're those horrible little 40mm fans. Nothing can quieten that part down no matter how low speed you run the miner.
|
|
|
-ck, what would be the best way to change payment address? Just flat out? ramp up small hash then swap everything? Or does it not matter with your pool design?
I've been thinking about this as well. My plan is to run up the my current address until it's in the payout list, then switch my miners to the new address. That shouldn't leave anything on the old address when the next block hits. Just switch everything whenever you want to, but do not lose the keys to the old address for it will likely get a payout at some stage still.
|
|
|
Hello, this is maybe slightly off subject, but I am wondering how to translate on cgminer the command line option "--suggest-diff 32" into an entry in the config file? Thanks!
Also off subject lately... I believe we finally have a block... 535,446 665 1,019,333 12.5 + 0.04192415 BTC 2018-08-06 00:08:45 0000000000000000001b5a52925ad249 aea46122014adb915f8ca3a5f1db5756 10.29T / 5.95T \o/ So, let's do another! [2018-08-06 05:08:31.765] Possible block solve diff 10290370667170.125000 ! [2018-08-06 05:08:31.831] BLOCK ACCEPTED! [2018-08-06 05:08:32.187] Solved block 535446 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc48x35 [2018-08-06 05:08:32.187] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "51.4P", "hashrate5m": "51.2P", "hashrate1hr": "51.1P", "hashrate1d": "51P", "hashrate7d": "46.1P"} [2018-08-06 05:08:32.187] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc48x35:{"hashrate1m": "18.8T", "hashrate5m": "18.3T", "hashrate1hr": "17T", "hashrate1d": "17T", "hashrate7d": "15.5T"} [2018-08-06 05:10:01.953] Hash for block height 535446 confirms block was CONFIRMED
https://btc.com/0000000000000000001b5a52925ad249aea46122014adb915f8ca3a5f1db5756
|
|
|
Holy hot streak batman..another one
[2018-08-02 12:12:06.710] Possible block solve diff 9972879925693.242188 ! [2018-08-02 12:12:06.810] BLOCK ACCEPTED! [2018-08-02 12:12:07.117] Solved block 534838 by 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms119x69 [2018-08-02 12:12:07.117] User 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX:{"hashrate1m": "44.6P", "hashrate5m": "44.1P", "hashrate1hr": "44.6P", "hashrate1d": "43.6P", "hashrate7d": "31.9P"} [2018-08-02 12:12:07.117] Worker 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms119x69:{"hashrate1m": "19.4T", "hashrate5m": "17.3T", "hashrate1hr": "17.1T", "hashrate1d": "17T", "hashrate7d": "14.2T"} [2018-08-02 12:23:30.044] Hash for block height 534838 confirms block was CONFIRMED
https://btc.com/0000000000000000001c393e8ef84a64a0f46c9ca26e89a9737a703b2f075ed2"diff": 4.9
|
|
|
|