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

PORTFOLIO / MY OPEN OFFERS issue #948

Closed
Ex0ticButt3rs opened this issue Jun 23, 2021 · 4 comments
Closed

PORTFOLIO / MY OPEN OFFERS issue #948

Ex0ticButt3rs opened this issue Jun 23, 2021 · 4 comments

Comments

@Ex0ticButt3rs
Copy link

My open offers are disabling themselves randomly. There is no trigger price set. I did test out the trigger price functionality earlier today yet updated all offers recently to have a blank trigger price.

Currently, the majority of my offers are switching themselves from on to off.

Questions:
1 - Is this a known bug/issue?
2 - What could be the root cause?
3 - What do I need to do to stop this from happening (as I do want all my offers to be active)?

@Ex0ticButt3rs Ex0ticButt3rs changed the title Portfolio / MY OPEN OFFERS issue PORTFOLIO / MY OPEN OFFERS issue Jun 23, 2021
@ghost
Copy link

ghost commented Jun 23, 2021

Go to DAO -> Network Monitor menu, see if it says you need to resync under DAO State.

@Ex0ticButt3rs
Copy link
Author

Ex0ticButt3rs commented Jun 23, 2021

Go to DAO -> Network Monitor menu, see if it says you need to resync under DAO State.

DAO State / Status = "One of your peers is not in consensus with the network but your node is in sync with the seed nodes."
Screen Shot 2021-06-22 at 11 44 00 PM

Please advise. I appreciate your attention to this matter.

@ghost
Copy link

ghost commented Jun 23, 2021

Please DM me your bisq.log on Keybase, I have this same username on there. The log location can be found by going to Application -> Backup

@ghost
Copy link

ghost commented Jun 23, 2021

The problem is caused by confusion in the Bisq app about what addresses are authorized to receive Bisq trading fee payments.

A recent change ending the April 2020 incident repayment shortened that list of fee receiver addresses, but since there are still open offers, Bisq thought the fees were not paid correctly and so disabled the offers.

To address this discrepancy, we've temporarily turned off the fee validation feature via a network filter setting. It might take up to 24 hours for the configuration change to propagate fully, please be patient if not resolved immediately. The Bisq client needs to be restarted in order to pick up the change. Once your Bisq client picks up the network setting, it will stop deactivating your offers.

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

No branches or pull requests

1 participant