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
Locked up funds #4894
Comments
Thanks for opening your first issue here! |
@chimp1984 Can you verify that this is a banned node address? @muaawiyahtucker Did you run your node with |
If you mean my Bitcoin Node, then the only thing in my 'bitcoin.conf' file is peerbloomfilters=1 Beyond that, I've not changed any settings on my Bisq app. Where would I find 'ignoreDevMsg'? as I've been talking to the mediator from the start. How would I make that change? just so that I know that I haven't do that. |
Yes 6jxwjzla2vi5mrgq.onion:9999 is in the banned address list. |
@muaawiyahtucker Can you PM me the log files in keybase (same username)? I would like to be sure that there is no bug which caused that issue. Also PM me a screenshor of the trade details. |
ignoreDevMsg is a prog arg one can set to ignore the filter message which contains the ban list. It is not recommended to use that but there for censorship resistence to limit the power of that filter message which is a kind of centralized tool. |
No, the offer was taken before the most recent update (they took my offer, not that I took theirs). This whole problem started 20 days ago. I updated 10 days ago. Ok, I'll DM you now. |
@muaawiyahtucker I think that issue is resolved. If so, can you close it? |
I had a trade, the other person on the trade did not respond for 20 days to the mediator moved towards arbitration. He told me to click on the proposed deal he offered and it then glitched with an error. After that error, that told me to log the error here, further errors showed up. All relevant screen shots are attached.
1.5.0
There were no steps to reproduce it as is clear from the above.
The reason why it can't be reproduced is because it depends upon the other trader who did not respond for 20 days. I cannot replicate that, as I don't know why he did not reply in those 20 days. The error could have been from his end or my end, or maybe he's dead or something, I don't know.
I click on the 'accept' button for the deal and it do what it's supposed to without an error.
This is the error I get after trying to accept the deal.
This is what I get every couple of minutes now on the app over and over again.
Device or machine
Mac Pro 4,1 flashed to 5,1
Additional info
This was the instructions received from the mediator
The text was updated successfully, but these errors were encountered: