Topic: ckpool.org CLOSED - page 67. (Read 162894 times)
Woohoo, but I'm on a flight and can't post the details.
Block!!
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.
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.
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: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.
Code:
[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: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
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: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.
Code:
[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: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.
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. 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.
...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% feeSerious 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.
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
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.
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.
So when an orphan block happens, shares are reset or lost? 
They continue to roll on as if the find didn't happen. So when an orphan block happens, shares are reset or lost?
reset. orphan would have been at 4.1. We picked up from there
So when an orphan block happens, shares are reset or lost?
It doesn't hurt too much when it's that close to the previous block.
Dangit!
fuck that sucks!
but it is worse for the top miner as it would have been 11 btc for him!
another orphan 
http://ckpool.org/blocks/531196.orphaned
http://ckpool.org/blocks/531196.orphaned
Pour one out for the orphan...
Keep talking food and beer. The blocks like it. 
Looks like Shiraz is the winning drop.
Code:
[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
[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
a small miner 1 s9! what would be the bonus for him?
or does he have 161 of them
7 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY 308TH/s 315TH/s 175TH/s 41 124,015,400 45348563477040 100% 28,588,064,562 0.0140184
Well looks like they aren't hurting for hash or coins. Address has over 400 never moved https://btc.com/3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY Congrats you and all
I'm sure that $89 he just got has him out looking for a new boat.
Keep talking food and beer. The blocks like it.
Looks like Shiraz is the winning drop.
Code:
[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
[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
a small miner 1 s9! what would be the bonus for him?
or does he have 161 of them
7 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY 308TH/s 315TH/s 175TH/s 41 124,015,400 45348563477040 100% 28,588,064,562 0.0140184
Well looks like they aren't hurting for hash or coins. Address has over 400 never moved https://btc.com/3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY Congrats you and all
Jump to: