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

Remind user when their DAO state needs to be refreshed #5552

Merged
merged 1 commit into from Jun 8, 2021
Merged

Remind user when their DAO state needs to be refreshed #5552

merged 1 commit into from Jun 8, 2021

Conversation

ghost
Copy link

@ghost ghost commented Jun 2, 2021

As described in #5393, having a DAO state that is in conflict can cause issues and unnecessary mediation cases.

Unfortunately, users are not notified when their DAO state is in conflict with seednodes, it is only shown by checking DAO -> Network Monitor -> Dao State.

This PR attempts to rectify that by checking the DAO state whenever Bisq has completed the block sync. If the DAO is reporting a conflict then a popup will be shown to the user asking them to resync . To avoid annoyance, this popup will only be shown at most once per session (and then only if a resync is needed).

This PR only checks the overall DAO state, not the voting or proposals state. This is intentional, since proposal and voting states are only applicable to a small subset of users whereas the goal of this PR is to prevent problems in trading.

Screenshot

image

 

Fixes #5329
Fixes #5393

@ripcurlx ripcurlx added this to the v1.6.6 milestone Jun 7, 2021
@ripcurlx
Copy link
Contributor

ripcurlx commented Jun 7, 2021

@jmacxx Maybe we could make it even easier if we offer the user a button to jump directly to the DAO -> Network Monitor screen in the popup as well. WDYT?

@ghost
Copy link
Author

ghost commented Jun 7, 2021

@jmacxx Maybe we could make it even easier if we offer the user a button to jump directly to the DAO -> Network Monitor screen in the popup as well. WDYT?

@ripcurlx I did the needful, looks better. Further testing revealed a bug, which has also been resolved. 😅

Copy link
Contributor

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

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

Successfully merging this pull request may close these issues.

DAO out of sync causes Bisq fee to be validated incorrectly BSQ trading fee calculated incorrectly
1 participant