-
Notifications
You must be signed in to change notification settings - Fork 38
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
implement nakamoto consensus, follow the latest valid chain #133
Comments
Shouldn't we maybe compare them by hash? (lower is better?) We have to choose something if we would like to mine. |
no, this would be a "most work" kind of consensus, as the miner we choose the one we received earlier to maximize possible profit. We will research other consensus mechanisms in the future, if you have any ideas we can discuss them and build a prototype to validate. |
ok, I understand now. |
[GH-133] Nakamoto consensus (longest chain consensus)
closed by #162 |
can be started after #97
The text was updated successfully, but these errors were encountered: