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

miner always "0x0000000000000000000000000000000000000000" #824

Closed
dvgoyeneche opened this issue Sep 23, 2019 · 4 comments
Closed

miner always "0x0000000000000000000000000000000000000000" #824

dvgoyeneche opened this issue Sep 23, 2019 · 4 comments

Comments

@dvgoyeneche
Copy link

I have miner="0x0000000000000000000000000000000000000000" in all my blocks in quorum.
¿Is this normal?

@zzy96
Copy link
Contributor

zzy96 commented Sep 24, 2019

For Raft, miner is always "0x0000000000000000000000000000000000000000". For IBFT and Clique, miner is used to store the candidate address of vote.

@dvgoyeneche
Copy link
Author

Thanks! How can we know who has mined the block?

@zzy96
Copy link
Contributor

zzy96 commented Sep 25, 2019

In Ethereum, we need to know who is the miner which is an Ethereum account for block reward (That's why we have this miner field). However, the new block is actually propagated by node. So your question should become "which node has mined the block". Then the answer is: For Raft, it is always the leader node. You can check node role with raft.role. For IBFT, every round one of the validator nodes will propose block. For Clique, miner nodes will try to seal the block with its coinbase account if it is in the signer list. You may also trace the log to get which node actually mined the block.

@fixanoid
Copy link
Contributor

fixanoid commented Oct 14, 2019

To add to @zzy96 answer. Raft block header contains sealer information that could be used to recover raft id of the minter. See: https://github.com/jpmorganchase/quorum/blob/master/raft/minter.go#L428

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

No branches or pull requests

3 participants