-
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 vote reveal tx publishing #2195
Merged
ManfredKarrer
merged 13 commits into
bisq-network:master
from
ManfredKarrer:dao-fix-vote-reveal-tx-publishing
Jan 5, 2019
Merged
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
ff22470
Improve logging
ManfredKarrer 9658115
Add chainTipHeight property
ManfredKarrer 00d0aa5
Use chain tip height for vote reveal tx publishing
ManfredKarrer 4fd8490
Handle late vote reveal txs
ManfredKarrer e70612d
Merge branch 'master' into dao-fix-vote-reveal-tx-publishing
ManfredKarrer ef37dc3
Set chainTipHeight before parsing.
ManfredKarrer c137e7e
Refactor maybeRevealVotes method.
ManfredKarrer 0a9f4fc
Remove phase and cycle check for vote reveal txs.
ManfredKarrer c1792a3
Ignore items if isBlindVoteInCorrectPhaseAndCycle is false.
ManfredKarrer c87383a
Refactorings
ManfredKarrer d23bb2c
Improve logs
ManfredKarrer 2f9125a
Improve logs
ManfredKarrer 4d8a348
Merge branch 'master' into dao-fix-vote-reveal-tx-publishing
ManfredKarrer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I have a feeling that we might want to wait to publish until we've parsed the chain up until chainTipHeight instead of publishing before we're done parsing. I don't have a concrete example, but publishing before knowing the actual current state seems like it could lead to more trouble. Maybe it would invalidate some BSQ, or maybe it would just burn some to fees.
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.
The onNewBlockHeight is called before the parsing of the block. So at the first block of the reveal phase we create and publish the tx. In the next block it will be validated and added to to the DaoState. So we could not wait for parsing until it is not published.