... what would be the bonus for him?
I've wondered about that for a while too! -ck, any easy way to estimate? It's always been a small reward for small miners. It's approximately equal to the minimum payout threshold for the pool so if you were always below threshold, it would start putting you into the next payouts list. I've been tempted to increase it but if I increase it too much that would start biasing towards the biggest miner, taking away from everyone else and we only really have one very big miner. |
|
|
|
Hi ck, I'm getting a strange json error in my logs. Looks like connector.c is not stripping HTTP from the json before it submits to json_load Connector created new client instance
[2018-07-11 14:59:53.478] Connected new client 0 on socket 12 to 0 active clients from 192.168.x.x:59482
[2018-07-11 14:59:53.478] Client sendbufsize detected as 374400
[2018-07-11 14:59:53.478] Client id 2 sent invalid json message POST / HTTP/1.1
Host: 192.168.xx.xx:3333
Authorization: Basic xxxxxxxxxob2FoMTxxxxxIzNDU
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
X-Mining-Extensions: longpoll midstate rollntime submitold
Content-Length: 116
User-Agent: sgminer 5.1.1
{"id": 0, "method": "getblocktemplate", "params": [{"capabilities": ["coinbasetxn", "workid", "coinbase/append"]}]} this is on latest bitbucket update from 2018-6-14. thanks! Andrew Hmm, nope, it looks like your client is sending a http encapsulated request for getblocktemplate instead of a json message and ckpool is simply dumping the entire message as is, rightly saying it's not valid json. Looks like the client is trying to mine with the defunct getblocktemplate mining protocol instead of stratum. It's also a shitcoin miner based on the mining software id it's giving you. |
|
|
|
Still waiting for CG's scotch recommend, we may all need be connoisseurs of his, blend? I'm actually intrigued.
Lagavulin 16yr is my regular go-to. Nikka Coffey Malt is for special occasions. |
|
|
|
Woohoo, but I'm on a flight and can't post the details. "solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V", "date": "[2018-07-10 04:28:09.546]", "hash": "000000000000000000153d8ce87fe60d486ecf7300b49e1bf9e005e85a41209a", "shares": 1319022060187, "diff": 24.6 nice diff http://ckpool.org/blocks/531285.confirmed[2018-07-10 04:28:09.447] Possible block solve diff 13251646224002.972656 !
[2018-07-10 04:28:09.538] BLOCK ACCEPTED!
[2018-07-10 04:28:09.551] Solved block 531285 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0
[2018-07-10 04:28:09.551] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "105P", "hashrate5m": "105P", "hashrate1hr": "83.8P", "hashrate1d": "96.1P", "hashrate7d": "102P"}
[2018-07-10 04:28:09.551] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "74.5P", "hashrate5m": "74.6P", "hashrate1hr": "53.9P", "hashrate1d": "66.2P", "hashrate7d": "75.1P"}
[2018-07-10 04:33:26.127] Hash for block height 531285 confirms block was CONFIRMED
|
|
|
|
Woohoo, but I'm on a flight and can't post the details. |
|
|
|
Alas it was also a stale block like the last orphan. The pool knew it was a stale share and had already moved on to the new block when it was submitted but it gave it a go anyway. You can see the response from bitcoind after it is forced on an inconclusive result. [2018-07-09 15:12:36.867] Possible stale share block solve diff 10410569547498.558594 !
[2018-07-09 15:12:36.903] SUBMIT BLOCK RETURNED: inconclusive
[2018-07-09 15:12:37.124] Hash for block height 531196 confirms block was ACCEPTED
[2018-07-09 15:12:37.258] Solved block 531196 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0
[2018-07-09 15:12:37.258] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "97.1P", "hashrate5m": "101P", "hashrate1hr": "104P", "hashrate1d": "103P", "hashrate7d": "103P"}
[2018-07-09 15:12:37.258] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "69.2P", "hashrate5m": "71.7P", "hashrate1hr": "73.8P", "hashrate1d": "73.2P", "hashrate7d": "76.5P"}
[2018-07-09 15:16:23.599] Hash for block height 531196 confirms block was ORPHANED
2018-07-09 15:12:37.017412 UpdateTip: new best=00000000000000000013d0a2129e653cde9219885d9ec9a4c252ee84ee531053 height=531195 version=0x20000000 log2_work=89.205391 tx=327038393 date='2018-07-09 15:05:06' progres s=0.999995 cache=65.8MiB(472416txo) 2018-07-09 15:12:37.048343 UpdateTip: new best=0000000000000000001b09798aeab0a4a601e64bf863f4c0c5ba2a49244ff44f height=531196 version=0x20000000 log2_work=89.205438 tx=327039680 date='2018-07-09 15:12:29' progres s=1.000000 cache=66.0MiB(473939txo) The only way we can win under those circumstances is if we win the next block as well. Maybe one day we'll be big enough for that to be possible. Most pools wouldn't even report stale share attempts at blocks like this. |
|
|
|
Keep talking food and beer. The blocks like it.  Looks like Shiraz is the winning drop. [2018-07-09 12:54:40.500] Possible block solve diff 45348563477040.054688 !
[2018-07-09 12:54:40.809] BLOCK ACCEPTED!
[2018-07-09 12:54:41.144] Solved block 531181 by 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.161
[2018-07-09 12:54:41.144] User 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY:{"hashrate1m": "314T", "hashrate5m": "311T", "hashrate1hr": "309T", "hashrate1d": "315T", "hashrate7d": "175T"}
[2018-07-09 12:54:41.144] Worker 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.161:{"hashrate1m": "14.6T", "hashrate5m": "12.4T", "hashrate1hr": "11.8T", "hashrate1d": "11.7T", "hashrate7d": "6.39T"}
[2018-07-09 12:59:19.494] Hash for block height 531181 confirms block was CONFIRMED
And we have a non-Halong block for a change too. https://btc.com/0000000000000000000634f29add5f6f6f87bd5635e3c344d2994179d51425de |
|
|
|
|
Actually the pool didn't like my beer last time, so I'm having wine with my steak tonight.
|
|
|
|
This eve, we have an "Everyday Kolsch" provided by Worthy Brewing. Enjoy.
Cheers, just about to walk down to the waterfront (I'm on vacation) and have a Little Creatures Pale Ale on tap. -ck ballin' with the mobile tap. Here's what it looked like (my wife had a tasting paddle.)  |
|
|
|
This eve, we have an "Everyday Kolsch" provided by Worthy Brewing. Enjoy.
Cheers, just about to walk down to the waterfront (I'm on vacation) and have a Little Creatures Pale Ale on tap. |
|
|
|
Happy centennial thread page ckpool!! *holds up beer*
Thanks! However, more information is needed if it's going to help us find a block. What are you drinking?? P.S. I hate and actively avoid the drama but someone seems hellbent on finding an excuse to bring it up. |
|
|
|
Hey guys wondering if anyone has figured out a possible solution? I tried switching my T1's to performance mode and I'm getting the "Error - failed to recv spi data" on two of my machines. On one all hash boards are down and on the other one board is down.
In performance mode you're overclocking them. There is no guarantee that you'll have enough power at that level, nor that the chains will be stable. You need extra power and aggressive cooling to make it likely to work, but even then it's not guaranteed. |
|
|
|
I even know 1 pool op that has blamed ASIC firmware versions for bad luck (not mentioning any names, but his nickname rhymes with guano  ) Touché. last 10 blocks add to 1002.3 which is 100.23 luck 053.5 060.5 003.9 105.2 052.2 227.7 245.4 057,4 065.5 131.0 1002.3 100.23 % = exactly normal So far asic boost is close to the same as no asic boost. but 10 or even 20 blocks is a same sample. numbers come from here http://ckpool.org/pool/blocks/169.3 016.4 054.4 033.7 = orphan 028.5 123.2 164.0 127.8 181.4 171.5 195.6 1265.8 or 126.58% this is poor luck and was compounded with the orphan 21 blocks since asic boost 1 orphan we will see what the next 10 blocks bring for us. under 100 or over Note you can ignore the orphan as the next block includes the orphan's shates here. |
|
|
|
"solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V",
"date": "[2018-07-06 19:05:33.758]",
"hash": "0000000000000000002edd80de4ecf0b343e84826301dcd813476a26b6daab83",
"shares": 2869976646098,
"diff": 53.5 And another shexy one. Gotta love the Law of Averages when we're on this side of it. [2018-07-06 19:05:33.684] Possible block solve diff 6005957420562.655273 !
[2018-07-06 19:05:33.757] BLOCK ACCEPTED!
[2018-07-06 19:05:33.764] Solved block 530771 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0
[2018-07-06 19:05:33.764] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "101P", "hashrate5m": "101P", "hashrate1hr": "101P", "hashrate1d": "102P", "hashrate7d": "104P"}
[2018-07-06 19:05:33.764] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "71.2P", "hashrate5m": "71.1P", "hashrate1hr": "70.8P", "hashrate1d": "74.4P", "hashrate7d": "78.5P"}
[2018-07-06 19:12:31.312] Hash for block height 530771 confirms block was CONFIRMED
|
|
|
|
Block!!!  Block!!! Happy Fifth . .. of July and 4th block of July.  Block!!! Happy Fifth . .. of July and 4th block of July. diff 60.5 http://ckpool.org/blocks/530580.confirmed "solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V",
"date": "[2018-07-05 13:24:31.031]",
"hash": "00000000000000000030926133424a36e01b145e687b8338c8ccf84b259f85db",
"shares": 3243862402422,
"diff": 60.5 Are any of the rest of us ever going to be the finder? [2018-07-05 13:24:30.963] Possible block solve diff 5794940827930.869141 !
[2018-07-05 13:24:31.029] BLOCK ACCEPTED!
[2018-07-05 13:24:31.036] Solved block 530580 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.msT1x127x78
[2018-07-05 13:24:31.037] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "107P", "hashrate5m": "105P", "hashrate1hr": "104P", "hashrate1d": "94.9P", "hashrate7d": "104P"}
[2018-07-05 13:24:31.037] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.msT1x127x78:{"hashrate1m": "13.1T", "hashrate5m": "16.1T", "hashrate1hr": "16.1T", "hashrate1d": "6.83T", "hashrate7d": "8.08T"}
[2018-07-05 13:38:20.035] Hash for block height 530580 confirms block was CONFIRMED
|
|
|
|
What a day! All I need now is to hit a block on the solo pool That would be nice since that's the only pool I actually make money off too. |
|
|
|
"solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V",
"date": "[2018-07-04 00:01:37.170]",
"hash": "0000000000000000001c379280893dec7b0f01bb81be4cdc7f77188f09964ce5",
"shares": 207481576338,
"diff": 3.9 confirmed by 530372 (BTC) and 530373 (F2Pool) So Shexy! Edit: there's an extreme irony that btc's own explorer lags to show their own block confirming it. [2018-07-04 00:01:37.035] Possible block solve diff 9975188424098.376953 !
[2018-07-04 00:01:37.157] BLOCK ACCEPTED!
[2018-07-04 00:01:37.652] Solved block 530371 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0
[2018-07-04 00:01:37.790] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "87P", "hashrate5m": "86.9P", "hashrate1hr": "86.4P", "hashrate1d": "96.5P", "hashrate7d": "106P"}
[2018-07-04 00:01:37.790] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "66.2P", "hashrate5m": "66.2P", "hashrate1hr": "65.8P", "hashrate1d": "73.3P", "hashrate7d": "80.8P"}
[2018-07-04 00:17:38.822] Hash for block height 530371 confirms block was CONFIRMED
|
|
|
|
block.....
Party!
(Sadly, heat issues pushed my two miners into limp-mode for the next few weeks, 60%, meaning I am postponed until next block.)
[2018-07-03 21:28:08.390] Possible block solve diff 9980568490286.888672 !
[2018-07-03 21:28:08.473] BLOCK ACCEPTED!
[2018-07-03 21:28:08.759] Solved block 530363 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.msT1x124x76
[2018-07-03 21:28:08.761] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "87.1P", "hashrate5m": "85.5P", "hashrate1hr": "85.3P", "hashrate1d": "97.7P", "hashrate7d": "107P"}
[2018-07-03 21:28:08.761] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.msT1x124x76:{"hashrate1m": "17.4T", "hashrate5m": "10.7T", "hashrate1hr": "10.6T", "hashrate1d": "12.4T", "hashrate7d": "8.79T"}
[2018-07-03 21:38:31.739] Hash for block height 530363 confirms block was CONFIRMED
|
|
|
|
|
Even better, they've deleted my follow-up post explaining that I personally edited their post but haven't been able to further edit their opening post making it look like they personally wrote the post that way.
|
|
|
|
Deleting a moderator's post was not smart and I've taken the liberty of correcting their post for them.
|
|
|
|
|
Show Posts
