-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Requested report of issue from bisq application #7073
Comments
Can you briefly describe the nature of the issue with your own words? what were you trying to do and what happened that prevented you from doing it? |
Sorry it was the auto-log and notfication so didn’t pay too much attention to the details. Likely it required a full SPV resync on an old account so was excessively slow, failing and freezing multiple times, resulting in deleting a spvresync file and starting from scratch in order to recover. It is working now but not the smoothest as the SPV often becomes out of sync (again, and old wallet).On May 10, 2024, at 9:19 AM, suddenwhipvapor ***@***.***> wrote:
Can you briefly describe the nature of the issue with your own words? what were you trying to do and what happened that prevented you from doing it?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Thank you for the feedback. |
Tor is suffering ddos attacks (https://metrics.torproject.org/torperf.html). |
Requested report of issue from bisq application
bisq.log
Description
Version
Steps to reproduce
Expected behaviour
Actual behaviour
Screenshots
Device or machine
Additional info
The text was updated successfully, but these errors were encountered: