implement nakamoto consensus, follow the latest valid chain #133

Activity

1. cytadela8 commented on Nov 22, 2017

   

   cytadela8

   on Nov 22, 2017

   Last edited by cytadela8

   Contributor

   More actions

   if there are 2 valid blocks at the same height, wait for the following block

   Shouldn't we maybe compare them by hash? (lower is better?) We have to choose something if we would like to mine.
2. thepiwo commented on Nov 22, 2017

   

   thepiwo

   on Nov 22, 2017

   ContributorAuthor

   More actions

   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.
3. cytadela8 commented on Nov 22, 2017

   

   cytadela8

   on Nov 22, 2017

   Contributor

   More actions

   ok, I understand now.
4. thepiwo

   assigned

   cytadela8

   on Nov 29, 2017
5. cytadela8

   added 6 commits that reference this issue on Dec 14, 2017

   [GH-133] Chain.Worker cleanup

   8cef334

   [GH-133] Satoshi consensus implemented

   a3f12cc

   Merge branch 'master' into GH-133

   56c623e

   [GH-133] Refactoring. Chainstate calculated only once

   a5804d8

   Merge branch 'master' into GH-133

   f83d627

   Merge branch 'master' into GH-133

   0727ebc
6. thepiwo

   added a commit that references this issue on Dec 18, 2017

   Merge pull request #162 from aeternity/GH-133

   ...

   ed4b4dd
7. thepiwo commented on Dec 18, 2017

   

   thepiwo

   on Dec 18, 2017

   ContributorAuthor

   More actions

   closed by #162
8. thepiwo

   closed this as completedon Dec 18, 2017