ckpool.org CLOSED

[-ck]

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).

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

https://btc.com/0000000000000000001543f546e5a30e8660394863199cb285342f58cade373e

Full payout details:
http://ckpool.org/blocks/527499.confirmed

[1714018816]

1714018816

[1714018816]

1714018816

[1714018816]

1714018816

[1714018816]

1714018816

[jsays]

Party!

[userghost]

Would have been a double block day  if not for the orphan!

[-ck]

Would have been a double block day  if not for the orphan!

Still might be.

[tfbiii]

Booya! BLOCK PARTY!!!

[tfbiii]

"solvedby": "1J17t8CjjVwegqn6Y4JC7osA8fNsuz8z5D",
 "date": "[2018-06-15 02:07:52.247]",
 "hash": "0000000000000000001543f546e5a30e8660394863199cb285342f58cade373e",
 "shares": 2696179102157,
 "diff": 54.6

[Philopolymath]

got tx

[userghost]

Wallet fully synced and yet no TX for latest payout? strange.

"17zyuMZzuD4cd4WCP24WcnnMcBkYiRc3es": 0.01627649

I got my payout

[userghost]

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.

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.

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?

[-ck]

Wallet fully synced and yet no TX for latest payout? strange.

"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.

[-ck]

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.

[userghost]

Another block yay! Its a block party!!!

[wh0]

 

[ComputerGenie]

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).

[User name used]

Congrats. It's raining blocks.

[evade_57]

My derp was around 001
Now it's 0001
My placement went from the fifties deferred payment to the six hundreds?
?

[ComputerGenie]

My derp was around 001
Now it's 0001
My placement went from the fifties deferred payment to the six hundreds?
?

The top payment spot in the deferred list is ~59¢ and number 600 is ~53¢, it's a long, long list of small miners all competing for a lot of relatively equal small payments.

[evade_57]

Genie, what confuses me is that overnight I went from just under $10 to pocket change this morning using your online tool
I am using Gekkoscience pods and sticks, but also an Antminer V9
I did note in a previous post that my ID on this pool was showing an additional worker which made no sense (3)
My max workers should be 2 (it is now) as the Gekkoscience hardware all run off one Raspberry Pi which should represent one worker, correct?
I am new to new so apologies in advance

[ComputerGenie]

Genie, what confuses me is that overnight I went from just under $10 to pocket change this morning using your online tool
I am using Gekkoscience pods and sticks, but also an Antminer V9
I did note in a previous post that my ID on this pool was showing an additional worker which made no sense (3)
My max workers should be 2 (it is now) as the Gekkoscience hardware all run off one Raspberry Pi which should represent one worker, correct?
I am new to new so apologies in advance

The number of workers show could be any number of things, including your miner initially contacting the pool without adding a worker tag (i.e., using just YourAddy instead of YourAddy.PiWorker).

As per the difference from timeX to timeY, I don't know the specifics of when you last got paid or what your hash shares amount to, but we did hit 2 blocks last night, so it should be expected that things are different than yesterday ("how different" depends on who got paid what and when).

[evade_57]

Thanks Genie!!!!!!!

I just updated my Bitcoin Core Wallet to keep it up to date and

WOOT!!!!!!!!!!!!   

My first Bitcoin payment ever .00160

Awesome, no longer a pool virgin!

Many thanks all!!!!!!! esp ck for all his work