[2018-09-05 16:56:40.792] Possible block solve diff 242921463739813.062500 !
[2018-09-05 16:56:40.955] BLOCK ACCEPTED!
[2018-09-05 16:56:41.292] Solved block 540068 by 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.testing
[2018-09-05 16:56:41.292] User 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc:{"hashrate1m": "5.15P", "hashrate5m": "5.12P", "hashrate1hr": "5.11P", "hashrate1d": "5.09P", "hashrate7d": "4.96P"}
[2018-09-05 16:56:41.292] Worker 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.testing:{"hashrate1m": "4.49P", "hashrate5m": "4.47P", "hashrate1hr": "4.46P", "hashrate1d": "4.45P", "hashrate7d": "4.31P"}
[2018-09-05 16:57:45.632] Hash for block height 540068 confirms block was CONFIRMED
[2018-09-05 21:19:55.635] Possible block solve diff 16830028369359.824219 !
[2018-09-05 21:19:55.763] BLOCK ACCEPTED!
[2018-09-05 21:19:56.382] Solved block 540093 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0
[2018-09-05 21:19:56.382] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "25.9P", "hashrate5m": "25.6P", "hashrate1hr": "24P", "hashrate1d": "30.9P", "hashrate7d": "26.4P"}
[2018-09-05 21:19:56.382] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "25.6P", "hashrate5m": "25.3P", "hashrate1hr": "23.7P", "hashrate1d": "30.6P", "hashrate7d": "26.2P"}
[2018-09-05 21:33:01.569] Hash for block height 540093 confirms block was CONFIRMED
|
|
|
|
I can use multiple bitcoin addresses? What effect does it have?
It makes your payouts less consistent, less frequent and more variable. In short, it's a bad idea. |
|
|
|
Why would I run it? Want to fund it? |
|
|
|
|
BTW if you're wondering about Kano's replies, I have no idea what he's posting. I've had him on ignore since he started viewing me as enemy no. 1 after I gave him the boot and just delete any posts on this thread. I'm sure he has plenty of other places he can vent. I know he's keen to go out of his way to follow my every move and stalk me and find fault with everything I do, but his posts aren't welcome here.
|
|
|
|
-ck feels much the same about bitmain as most of us.
How would anyone feel about a multibillion dollar company that uses your free software as the cornerstone of their business and have never engaged you on any level? |
|
|
|
I noticed that it shows on btc.com but not blocktrail another shitmain broken product.  I think they own both anyway. Perhaps they're saving money on the site since they're doing a great job at fucking up their IPO due to losing hundreds of millions by buying up shitcoin cash big. Fuckem. |
|
|
|
CK I noticed that the pool no longer announces it's block finds on the explorers it shows at unknown on blocktrail
"The pool" never announced anything. Blocktrail just broke on its own accord  Block explorers detect pools' blocks based on their coinbase signature or address and ours has never changed. |
|
|
|
[2018-09-02 06:55:48.558] Possible block solve diff 8822115452621.472656 !
[2018-09-02 06:55:48.828] BLOCK ACCEPTED!
[2018-09-02 06:55:49.214] Solved block 539609 by 1FXusfoiNV7QTVrAwWd5bnuxxvZ5Hzf7md
[2018-09-02 06:55:49.343] User 1FXusfoiNV7QTVrAwWd5bnuxxvZ5Hzf7md:{"hashrate1m": "3.12P", "hashrate5m": "2.27P", "hashrate1hr": "2.83P", "hashrate1d": "5.13P", "hashrate7d": "6.48P"}
[2018-09-02 06:55:49.348] Worker 1FXusfoiNV7QTVrAwWd5bnuxxvZ5Hzf7md:{"hashrate1m": "3.12P", "hashrate5m": "2.27P", "hashrate1hr": "2.83P", "hashrate1d": "5.13P", "hashrate7d": "6.48P"}
[2018-09-02 06:59:28.793] Hash for block height 539609 confirms block was CONFIRMED
|
|
|
|
And Another Block!!
[2018-08-27 00:01:01.907] Possible block solve diff 20343276697692.789062 !
[2018-08-27 00:01:01.935] BLOCK ACCEPTED!
[2018-08-27 00:01:01.941] Solved block 538630 by 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms28x167
[2018-08-27 00:01:01.941] User 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX:{"hashrate1m": "43.5P", "hashrate5m": "43.4P", "hashrate1hr": "43.8P", "hashrate1d": "43.2P", "hashrate7d": "43.2P"}
[2018-08-27 00:01:01.941] Worker 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms28x167:{"hashrate1m": "16.7T", "hashrate5m": "16.6T", "hashrate1hr": "16.7T", "hashrate1d": "16.2T", "hashrate7d": "16.4T"}
[2018-08-27 00:08:02.987] Hash for block height 538630 confirms block was CONFIRMED
|
|
|
|
[2018-08-26 16:21:06.641] Possible block solve diff 10853082727075.859375 !
[2018-08-26 16:21:06.806] BLOCK ACCEPTED!
[2018-08-26 16:21:07.117] Solved block 538579 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc46x41
[2018-08-26 16:21:07.195] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "76.1P", "hashrate5m": "75.7P", "hashrate1hr": "75P", "hashrate1d": "75.1P", "hashrate7d": "72.3P"}
[2018-08-26 16:21:07.195] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc46x41:{"hashrate1m": "13.8T", "hashrate5m": "15.8T", "hashrate1hr": "16.6T", "hashrate1d": "16.7T", "hashrate7d": "16.7T"}
[2018-08-26 16:30:37.359] Hash for block height 538579 confirms block was CONFIRMED
[2018-08-26 18:58:13.319] Possible block solve diff 17034637612728.335938 !
[2018-08-26 18:58:13.385] BLOCK ACCEPTED!
[2018-08-26 18:58:13.736] Solved block 538597 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc14x138
[2018-08-26 18:58:13.736] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "75.9P", "hashrate5m": "75.5P", "hashrate1hr": "75.1P", "hashrate1d": "75.1P", "hashrate7d": "72.4P"}
[2018-08-26 18:58:13.736] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc14x138:{"hashrate1m": "19.2T", "hashrate5m": "18.7T", "hashrate1hr": "17.5T", "hashrate1d": "17T", "hashrate7d": "16.9T"}
[2018-08-26 19:04:17.442] Hash for block height 538597 confirms block was CONFIRMED
|
|
|
|
I'm looking at adding a DYI
By the way, DYI is Do Yourself In. Please don't. DIY is fine though. |
|
|
|
Optimisitc *woot* while waiting on confirmation... "solvedby": "3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX",
"date": "[2018-08-23 20:30:52.531]",
"hash": "00000000000000000001e4d58afd0f91336954d32a4ef9221cb53c271134a758",
"shares": 3942219355720,
"diff": 61.7
Confirmed! Still time for another today! [2018-08-23 20:30:52.489] Possible block solve diff 148620913403374.968750 !
[2018-08-23 20:30:52.526] BLOCK ACCEPTED!
[2018-08-23 20:30:52.536] Solved block 538158 by 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms32x77
[2018-08-23 20:30:52.536] User 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX:{"hashrate1m": "44.2P", "hashrate5m": "44P", "hashrate1hr": "44P", "hashrate1d": "43.6P", "hashrate7d": "43.3P"}
[2018-08-23 20:30:52.537] Worker 3QRZahE19MNqGFfgHZngUzGFVrmgkrFeuX.ms32x77:{"hashrate1m": "13.8T", "hashrate5m": "14.5T", "hashrate1hr": "16T", "hashrate1d": "16.4T", "hashrate7d": "15.7T"}
[2018-08-23 20:59:25.570] Hash for block height 538158 confirms block was CONFIRMED
|
|
|
|
Only 3 blocks apart! We still haven't had back to back blocks yet. [2018-08-22 17:02:20.907] Possible block solve diff 39027755591568.484375 !
[2018-08-22 17:02:21.005] BLOCK ACCEPTED!
[2018-08-22 17:02:21.010] Solved block 537977 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.30x17
[2018-08-22 17:02:21.011] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "76.3P", "hashrate5m": "75.1P", "hashrate1hr": "75.5P", "hashrate1d": "74.8P", "hashrate7d": "70.3P"}
[2018-08-22 17:02:21.011] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.30x17:{"hashrate1m": "13.8T", "hashrate5m": "15.3T", "hashrate1hr": "15.9T", "hashrate1d": "15.3T", "hashrate7d": "12.5T"}
[2018-08-22 17:02:30.030] Hash for block height 537977 confirms block was CONFIRMED
[2018-08-22 17:33:12.245] Possible block solve diff 6502168937761.557617 !
[2018-08-22 17:33:12.360] BLOCK ACCEPTED!
[2018-08-22 17:33:12.841] Solved block 537980 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc41x147
[2018-08-22 17:33:12.938] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "76.5P", "hashrate5m": "76.3P", "hashrate1hr": "75.6P", "hashrate1d": "74.8P", "hashrate7d": "70.3P"}
[2018-08-22 17:33:12.939] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc41x147:{"hashrate1m": "16.7T", "hashrate5m": "15.2T", "hashrate1hr": "16.2T", "hashrate1d": "16.7T", "hashrate7d": "16.7T"}
[2018-08-22 17:36:50.069] Hash for block height 537980 confirms block was CONFIRMED
|
|
|
|
[2018-08-21 18:09:23.376] Possible block solve diff 6648201862921.397461 !
[2018-08-21 18:09:23.474] BLOCK ACCEPTED!
[2018-08-21 18:09:23.480] Solved block 537830 by 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc43x196
[2018-08-21 18:09:23.480] User 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP:{"hashrate1m": "76.4P", "hashrate5m": "75.2P", "hashrate1hr": "75.4P", "hashrate1d": "73.5P", "hashrate7d": "69.5P"}
[2018-08-21 18:09:23.480] Worker 3Cy7rpWHSzEJ42XRjUkACUdWE3KHiu3puP.xc43x196:{"hashrate1m": "20.6T", "hashrate5m": "18.5T", "hashrate1hr": "17.4T", "hashrate1d": "16.5T", "hashrate7d": "16.6T"}
[2018-08-21 18:14:02.315] Hash for block height 537830 confirms block was CONFIRMED
|
|
|
|
For what it's worth, when I DID have to communicate with the Inno guys (who created the Halong hardware under contract), we constantly argued about how best to tune them and the balanced and efficiency modes are what I invented and they had their own tuning which they were sure was better so I let them have the "factory" option as a tuning setting. It was garbage. Not long after that I stopped being contracted to help on anything to do with their hardware (since I was working indirectly for Halong, NOT Inno.)
This is pretty note worthy. This was for the T2T or back with with DM T1? I only ever worked on the T1, they used the same starting code for T2 - which I only ever tested remotely - and presumably T2T. I've had nothing to do with Inno since then. There's a reason my coding for the hardware was intense for a couple of months and then stopped abruptly. The relationship between myrig, halong and inno is complicated and strained, to say the least, but I'm not informed of all the details and neither do I want to be. Inno did ask me to help "advertise" their hardware, which I refused to do. That's clearly not something I would ever do for any manufacturer anyway. |
|
|
|
It is on factory setting doing 21.8 and about 2085 watts or 95.6 watts a th Please note this means nothing as gear has to settle in and auto tune
the power draw seems to be close to 2100 watts on factory setting not a number i want unless of course gear was doing 28 or 30 th.
I dropped to efficiency and power draw is only 1457 watts more what I like
unit is doing about 17.6 to 18.4 th so 79.03 watts a th at best and 82.78 watts a th at worst. these are meter numbers on a 240 volt circuit putting out 236.8 volts
For what it's worth, when I DID have to communicate with the Inno guys (who created the Halong hardware under contract), we constantly argued about how best to tune them and the balanced and efficiency modes are what I invented and they had their own tuning which they were sure was better so I let them have the "factory" option as a tuning setting. It was garbage. Not long after that I stopped being contracted to help on anything to do with their hardware (since I was working indirectly for Halong, NOT Inno.) |
|
|
|
I've got about 70 Th of power and I'm looking desperately to improve the profitability of my S9's for obvious reasons.
I have no problems with variance. I'm quite patient. It's the returns I'm after.
I don't have the guts to try solo mining with my measly hashrate but I LOVE the idea that IN CASE my little litter finds a high difficulty share, i'm rewarded proportionately higher. From my understanding standard PPLNS does not offer this.
Few questions:
1) Am I right about the fact that standard PPLNS doesn't give you proportionately higher rewards for finding shares of higher difficulty?
2) Does CKPool (not solo) pay out higher if I'm lucky and find shares of higher difficulty? Is it worth the wait in terms of variance?
3) Am I too small a player to be consistently paid? I mean I don't want to wait for blocks on end till the revolving 50 tail enders are paid.
Any input greatly appreciated.
1. Yes 2. But they're so small it's only relevant to minuscule miners. At your size it will even out in no time 3. At 70TH it puts you in the top 50 miners and after mining here for a few days you will be getting payouts with every block. |
|
|
|
What is the probability of finding a block with an S9 13.5T at current difficulty? @-ck I show only 239 blocks found on block trail, not 251. Was the last block found on 7/22? https://www.blocktrail.com/BTC/pool/solockpoolIt seems like the pool finds a block every month and a half on average, would you say that's correct? Thank you, Darco About 1 in 23000 per day. The first blocks did not have the same signature so they're not counted by block explorers. Yes last block was about then. The pool used to find a block that often, but with current difficulty, that is not likely any more. |
|
|
|
|
Show Posts
