philipma1957
Legendary
 Offline
Activity: 4102
Merit: 7764
'The right to privacy matters'
|
 |
July 09, 2018, 03:20:06 PM |
|
fuck that sucks! but it is worse for the top miner as it would have been 11 btc for him! |
|
|
|
|
|
|
|
|
|
|
|
|
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
jsays
Jr. Member
Offline
Activity: 78
Merit: 7
|
|
July 09, 2018, 03:31:01 PM |
|
|
|
|
|
|
faheshang
Member
Offline
Activity: 99
Merit: 16
|
|
July 09, 2018, 03:34:53 PM |
|
It doesn't hurt too much when it's that close to the previous block. |
|
|
|
|
evade_57
Member
Offline
Activity: 93
Merit: 11
|
|
July 09, 2018, 03:35:37 PM |
|
So when an orphan block happens, shares are reset or lost?  |
|
|
|
|
Fugio
Jr. Member
Offline
Activity: 50
Merit: 15
|
|
July 09, 2018, 03:48:09 PM |
|
So when an orphan block happens, shares are reset or lost? reset. orphan would have been at 4.1. We picked up from there |
|
|
|
|
|
ComputerGenie
|
|
July 09, 2018, 05:44:43 PM |
|
So when an orphan block happens, shares are reset or lost? They continue to roll on as if the find didn't happen. |
If you have to ask "why?", you wouldn`t understand my answer.
Always be on the look out, because you never know when you'll be stalked by hit-men that eat nothing but cream cheese....
|
|
|
studio_mining
Jr. Member
Offline
Activity: 33
Merit: 10
|
|
July 09, 2018, 07:55:52 PM |
|
Serious question, have read the thread:
Looking to move 30+ PH/s of hashing currently pointed towards SlushPool (2/3 of it is ASICBoost T1s).
Other than variable output in a smaller pool, is this a worthwhile move? Less than excited for the 5N ramp up time, but understand and looking for a longterm home.
|
|
|
|
|
Fugio
Jr. Member
Offline
Activity: 50
Merit: 15
|
Serious question, have read the thread:
Looking to move 30+ PH/s of hashing currently pointed towards SlushPool (2/3 of it is ASICBoost T1s).
Other than variable output in a smaller pool, is this a worthwhile move? Less than excited for the 5N ramp up time, but understand and looking for a longterm home.
0% fee |
|
|
|
|
|
ComputerGenie
|
|
July 09, 2018, 09:15:54 PM
Last edit: July 09, 2018, 10:17:38 PM by ComputerGenie Merited by frodocooper (1) |
|
...Other than variable output in a smaller pool, is this a worthwhile move? Less than excited for the 5N ramp up time, but understand and looking for a longterm home.
0% fee Exactly. In the long run, the "worst case" is you only make 2% more (the amount you're currently donating to slush's retirement fund). |
If you have to ask "why?", you wouldn`t understand my answer.
Always be on the look out, because you never know when you'll be stalked by hit-men that eat nothing but cream cheese....
|
|
|
faheshang
Member
Offline
Activity: 99
Merit: 16
|
|
July 09, 2018, 09:44:56 PM |
|
Serious question, have read the thread:
Looking to move 30+ PH/s of hashing currently pointed towards SlushPool (2/3 of it is ASICBoost T1s).
Other than variable output in a smaller pool, is this a worthwhile move? Less than excited for the 5N ramp up time, but understand and looking for a longterm home.
0% fee and now that the pool is over 100PH it was an easy decision for me. |
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4088
Merit: 1631
Ruu \o/
|
|
July 09, 2018, 09:46:38 PM |
|
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. |
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
|
|
|
Fugio
Jr. Member
Offline
Activity: 50
Merit: 15
|
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. tis better to have loved and lost than never to have loved at all. I loved that little block to the fullest for the entire 20 seconds I believed it was ours. Ok on to the next   Drink of the night: El Guapo Agave IPA. Cheers to the next block |
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 221
We are not retail.
|
|
July 10, 2018, 04:05:42 AM |
|
Serious question, have read the thread:
Looking to move 30+ PH/s of hashing currently pointed towards SlushPool (2/3 of it is ASICBoost T1s).
Other than variable output in a smaller pool, is this a worthwhile move? Less than excited for the 5N ramp up time, but understand and looking for a longterm home.
Move half over and ramp up, then pull the other half over if you don't want to wait. Otherwise just wait to push everything over on your next power billing cycle. |
|
|
|
faheshang
Member
Offline
Activity: 99
Merit: 16
|
|
July 10, 2018, 04:29:36 AM |
|
|
|
|
|
|
jsays
Jr. Member
Offline
Activity: 78
Merit: 7
|
|
July 10, 2018, 04:34:37 AM |
|
|
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4088
Merit: 1631
Ruu \o/
|
|
July 10, 2018, 04:45:39 AM |
|
Woohoo, but I'm on a flight and can't post the details. |
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
|
|
|
faheshang
Member
Offline
Activity: 99
Merit: 16
|
|
July 10, 2018, 04:55:30 AM |
|
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 |
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 221
We are not retail.
|
|
July 10, 2018, 05:13:31 AM |
|
Nice, great good feels. Thanks for all the work everyone!
|
|
|
|
Fugio
Jr. Member
Offline
Activity: 50
Merit: 15
|
|
July 10, 2018, 01:12:47 PM |
|
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 |
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4088
Merit: 1631
Ruu \o/
|
|
July 10, 2018, 01:14:31 PM |
|
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
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
|
|
|
|
