-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
Go to |
Please DM me your bisq.log on Keybase, I have this same username on there. The log location can be found by going to |
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. |
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)?
The text was updated successfully, but these errors were encountered: