Now it's 0001
My placement went from the fifties deferred payment to the six hundreds?
? 
Topic: ckpool.org CLOSED - page 84. (Read 162894 times)
My derp was around 001
Now it's 0001
My placement went from the fifties deferred payment to the six hundreds?
?
Now it's 0001
My placement went from the fifties deferred payment to the six hundreds?
?
Congrats. It's raining blocks.
What happens during an orphan block? Do coins appear in our wallets (as unmatured) then get taken away when its officially orphaned?
That mostly depends on the network, the wallet you use, and the peers you're connected to....If your node saw both blocks (this usually doesn't get visually represented in most GUIs), then box that normally shows a pie chart (◔,◕, etc.) and/or ✓ will likely show an ✖ and say "Conflicted" with the value being inside [] brackets.
It's pretty rare for a "average user" GUI wallet to show things like that.
For most, especially since it's a coinbase tx from a non-local node, would never see it because the block competed against was already accepted as valid (it might not seem like it, but 0.7 seconds can be like an eternity in network time).
Another block yay! Its a block party!!!
What happens during an orphan block? Do coins appear in our wallets (as unmatured) then get taken away when its officially orphaned?
Only if you see that block first before the other one that orphans it. In this situation you wouldn't have seen anything. Wallet fully synced and yet no TX for latest payout? strange.
"17zyuMZzuD4cd4WCP24WcnnMcBkYiRc3es": 0.01627649
"17zyuMZzuD4cd4WCP24WcnnMcBkYiRc3es": 0.01627649
It's there with 9 confirmations, like all the rest of the rewards:
https://btc.com/17zyuMZzuD4cd4WCP24WcnnMcBkYiRc3es
Hope your wallet isn't bogus.
Watching the chain to see if we win a double race... likely the only adrenaline-inducing thing left in mining. 
Watching the pool you mine in lose that race... likely the worst feeling left in mining.
Alas it was a foregone conclusion. It wasn't much of an orphan race at all, so even the fast block change code in the pool couldn't have prevented us losing that one.Watching the pool you mine in lose that race... likely the worst feeling left in mining.
For people wondering what he's talking about, we had a block orphaned. What happened was the block had already been solved by another pool, but a miner submitted a stale share 700ms later that was also a block solve. There was almost no chance it was going to be successful, but the pool will try to use it as a block solve anyway, forcing bitcoind to accept the block, in the unlikely event it wins the orphan race (or solves two blocks back to back). Realistically the pool can just ignore it since it was stale but we'll try anything to get a block.
Here are the pool logs where you can see it says it's submitting a stale share block solve:
Code:
[2018-06-14 18:11:25.412] Block hash changed to 00000000000000000037e634734805d4a48f7d50125ecc55a2f137e2722a32f3
[2018-06-14 18:11:26.100] Possible stale share block solve diff 10130992321539.841797 !
[2018-06-14 18:11:26.100] Submitting block data!
[2018-06-14 18:11:26.107] SUBMIT BLOCK RETURNED: inconclusive
[2018-06-14 18:11:26.171] Hash for block height 527471 confirms block was ACCEPTED
[2018-06-14 18:11:26.176] Solved block 527471 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0
[2018-06-14 18:11:26.176] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "142P", "hashrate5m": "142P", "hashrate1hr": "136P", "hashrate1d": "83.7P", "hashrate7d": "56.6P"}
[2018-06-14 18:11:26.176] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "107P", "hashrate5m": "107P", "hashrate1hr": "102P", "hashrate1d": "73.4P", "hashrate7d": "54.6P"}
[2018-06-14 18:11:26.272] Block hash changed to 0000000000000000001bc87b3d85516a0b00bf873a43dbef986125c269c210d8
[2018-06-14 18:32:31.978] Hash for block height 527471 confirms block was ORPHANED
At the end the pool sees that it lost the orphan race and moves to the new block. Unfortunate, but one of the realities of mining. The only fortunate part is the pool code already takes into account what should happen in the case of an orphan, to prevent the interleaved payouts getting out of sync. It will also NOT artificially reset the diff back to 0% since we didn't win a block.[2018-06-14 18:11:26.100] Possible stale share block solve diff 10130992321539.841797 !
[2018-06-14 18:11:26.100] Submitting block data!
[2018-06-14 18:11:26.107] SUBMIT BLOCK RETURNED: inconclusive
[2018-06-14 18:11:26.171] Hash for block height 527471 confirms block was ACCEPTED
[2018-06-14 18:11:26.176] Solved block 527471 by 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0
[2018-06-14 18:11:26.176] User 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V:{"hashrate1m": "142P", "hashrate5m": "142P", "hashrate1hr": "136P", "hashrate1d": "83.7P", "hashrate7d": "56.6P"}
[2018-06-14 18:11:26.176] Worker 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V.0:{"hashrate1m": "107P", "hashrate5m": "107P", "hashrate1hr": "102P", "hashrate1d": "73.4P", "hashrate7d": "54.6P"}
[2018-06-14 18:11:26.272] Block hash changed to 0000000000000000001bc87b3d85516a0b00bf873a43dbef986125c269c210d8
[2018-06-14 18:32:31.978] Hash for block height 527471 confirms block was ORPHANED
You can see the full details of what would have been a block in this sadly named block file:
http://ckpool.org/blocks/527471.orphaned
What happens during an orphan block? Do coins appear in our wallets (as unmatured) then get taken away when its officially orphaned?
Wallet fully synced and yet no TX for latest payout? strange.
"17zyuMZzuD4cd4WCP24WcnnMcBkYiRc3es": 0.01627649
"17zyuMZzuD4cd4WCP24WcnnMcBkYiRc3es": 0.01627649
I got my payout
got tx
"solvedby": "1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D",
"date": "[2018-06-15 02:07:52.247]",
"hash": "0000000000000000001543f546e5a30e8660394863199cb285342f58cade373e",
"shares": 2696179102157,
"diff": 54.6
"date": "[2018-06-15 02:07:52.247]",
"hash": "0000000000000000001543f546e5a30e8660394863199cb285342f58cade373e",
"shares": 2696179102157,
"diff": 54.6
Booya! BLOCK PARTY!!!
Would have been a double block day if not for the orphan!
Still might be.
Would have been a double block day if not for the orphan!
Party!
Making up for the orphan at 54.6% diff 
This time it wasn't Halong! One of our regular miners (but with a Dragonmint T1 nonetheless).
https://btc.com/0000000000000000001543f546e5a30e8660394863199cb285342f58cade373e
Full payout details:
http://ckpool.org/blocks/527499.confirmed
This time it wasn't Halong! One of our regular miners (but with a Dragonmint T1 nonetheless).
Code:
[2018-06-15 02:07:52.153] Possible block solve diff 13236048667151.658203 !
[2018-06-15 02:07:52.242] BLOCK ACCEPTED!
[2018-06-15 02:07:52.251] Solved block 527499 by 1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D.DMT11
[2018-06-15 02:07:52.251] User 1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D:{"hashrate1m": "129T", "hashrate5m": "128T", "hashrate1hr": "124T", "hashrate1d": "118T", "hashrate7d": "105T"}
[2018-06-15 02:07:52.251] Worker 1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D.DMT11:{"hashrate1m": "15.4T", "hashrate5m": "13.7T", "hashrate1hr": "12.9T", "hashrate1d": "9.85T", "hashrate7d": "8.94T"}
[2018-06-15 02:17:24.830] Hash for block height 527499 confirms block was CONFIRMED
[2018-06-15 02:07:52.242] BLOCK ACCEPTED!
[2018-06-15 02:07:52.251] Solved block 527499 by 1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D.DMT11
[2018-06-15 02:07:52.251] User 1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D:{"hashrate1m": "129T", "hashrate5m": "128T", "hashrate1hr": "124T", "hashrate1d": "118T", "hashrate7d": "105T"}
[2018-06-15 02:07:52.251] Worker 1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D.DMT11:{"hashrate1m": "15.4T", "hashrate5m": "13.7T", "hashrate1hr": "12.9T", "hashrate1d": "9.85T", "hashrate7d": "8.94T"}
[2018-06-15 02:17:24.830] Hash for block height 527499 confirms block was CONFIRMED
https://btc.com/0000000000000000001543f546e5a30e8660394863199cb285342f58cade373e
Full payout details:
http://ckpool.org/blocks/527499.confirmed
Our difficulty % was around 125%
Code:
"solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V",
"date": "[2018-06-13 13:28:53.840]",
"hash": "00000000000000000031552854fde522e73177585ecd463dea64fb503c4e0083",
"shares": 6085301242740,
"diff": 123.2
I was wondering where is this 'solvedby' URL?
Thanks!
http://ckpool.org/blocks/
Thanks! Didn't noticed the above info was at the bottom of the blocks.
BLOCK! (527356)
13hr 20mins!
13hr 20mins!
well that was hours ago but it was a "lucky" block well under 100%
Ops!
Forgotten to take into account the timezone. Was too excited!
Timestamps in the /blocks URL are UTC-5?
Our difficulty % was around 125%
Code:
"solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V",
"date": "[2018-06-13 13:28:53.840]",
"hash": "00000000000000000031552854fde522e73177585ecd463dea64fb503c4e0083",
"shares": 6085301242740,
"diff": 123.2
I was wondering where is this 'solvedby' URL?
Thanks!
http://ckpool.org/blocks/
Our difficulty % was around 125%
Code:
"solvedby": "36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V",
"date": "[2018-06-13 13:28:53.840]",
"hash": "00000000000000000031552854fde522e73177585ecd463dea64fb503c4e0083",
"shares": 6085301242740,
"diff": 123.2
I was wondering where is this 'solvedby' URL?
Thanks!
Are you looking for the URL to actually see the block info ? Here: https://btc.com/stats/pool/CKPool
Height: 527,282
Jump to: