Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The block was not credited #3257

Closed
githubusrR opened this issue Mar 1, 2020 · 5 comments
Closed

The block was not credited #3257

githubusrR opened this issue Mar 1, 2020 · 5 comments

Comments

@githubusrR
Copy link

@githubusrR githubusrR commented Mar 1, 2020

Ubuntu 18.04
Grin Version 3.1.0-beta.1 (proto: 2)

log:

20200301 08:50:18.905 WARN grin_servers::mining::stratumserver - (Server ID: 0) Solution Found for block 588628, hash 000047e46564 - Yay!!! Worker ID: 12, blocks found: 1, shares: 759
20200301 08:50:18.905 INFO grin_servers::mining::stratumserver - (Server ID: 0) Got share at height 588628, hash 000047e46564, edge_bits 31, nonce 3610856989469486504, job_id 0, difficulty 1433803041/1227045549, submitted by rig3

Everything is fine in the log, but there is no block enrollment, there were no rejects either

On the wallet in balances it is not present and in txs

@jaspervdm

This comment has been minimized.

Copy link
Member

@jaspervdm jaspervdm commented Mar 1, 2020

The coinbase reward doesn't show up in your wallet because the block was orphaned: your block vs block in longest chain

@jaspervdm jaspervdm closed this Mar 1, 2020
@githubusrR

This comment has been minimized.

Copy link
Author

@githubusrR githubusrR commented Mar 1, 2020

What caused this?
Everything was working normally

@jaspervdm

This comment has been minimized.

Copy link
Member

@jaspervdm jaspervdm commented Mar 1, 2020

Short lived forks are normal, especially with 1 minute block times

@githubusrR

This comment has been minimized.

Copy link
Author

@githubusrR githubusrR commented Mar 1, 2020

how does one choose who gets the block?I understand reorg but here the block was accepted

@jaspervdm

This comment has been minimized.

Copy link
Member

@jaspervdm jaspervdm commented Mar 1, 2020

Both you and a competing miner found a block at height 588,628 at roughly the same time and broadcast it to the network. Due to network topology and latency the order in which the blocks are received is not the same for every node. So some of the miners received the other block before they received yours, meaning they build their own block at 588,629 on top of the other one. This caused yours to be orphaned, as now the longest chain doesn't include your block. This is a very normal statistical process that happens in every PoW chain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.