-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Dao fix issues with majority hash #2360
Dao fix issues with majority hash #2360
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Added some fixes to spelling mistakes and variable naming.
Otherwise this looks better, waiting for the end of batch parsing and checking the current phase at that height before publishing vote. I wonder if our usage of chainHeight, blocHeight, height and what not is lacking since we're getting confused. Perhaps better naming would help us understand better what we're doing.
core/src/main/java/bisq/core/dao/governance/votereveal/VoteRevealService.java
Outdated
Show resolved
Hide resolved
core/src/main/java/bisq/core/dao/governance/votereveal/VoteRevealService.java
Outdated
Show resolved
Hide resolved
core/src/main/java/bisq/core/dao/governance/votereveal/VoteRevealService.java
Outdated
Show resolved
Hide resolved
core/src/main/java/bisq/core/dao/governance/voteresult/VoteResultException.java
Show resolved
Hide resolved
Co-Authored-By: ManfredKarrer <mk@nucleo.io>
…ealService.java Co-Authored-By: ManfredKarrer <mk@nucleo.io>
…ealService.java Co-Authored-By: ManfredKarrer <mk@nucleo.io>
…ealService.java Co-Authored-By: ManfredKarrer <mk@nucleo.io>
Yes we should rename once blockHeight params to be always the same. |
I think we might need to differentiate between parsed height, known last block height, height for a certain block and perhaps even more and use different but consistent names. |
No description provided.