@tonych, the same problem with version 1.7.1, any help here?
I am trying to sync my byteball wallet from a couple of weeks ago and it gets about a third of the way (35-45%) and then stops making progress. When I close and reopen the wallet, I get this error and the program closes:
Uncaught exception: Error: known bad go38q4DxyfamiSTzl5rmEBooilX0qGmoS36Wc9zVEY=: authentifier verification failed
Any ideas what to do? I have several full backups of the byteball folder, but for every one of them I run into exactly the same problem.
+1 got same error
Uncaught exception: Error: known bad
go38q+DxyfamiSTzl5rmEBooilX0qGmoS36Wc9zVEY=
authentifier verification failed
Interesting. I got a similar error with 1.7.1, almost immediately after startup. I didn't record the actual string though. I switched to a backup and the error did not reappear yet, but synch is very slow as is often the case - 70% now, about 5 hours in.
Edit: Update - I left the 1.7.1 wallet running from the backup file overnight. After about 8 hours it had reached 80% synched, but it seemed stalled at that number after a few more hours. I closed it and restarted, which in the past has always fixed these apparent stalls in synching.
On restart it quickly threw the error above, with the same "known bad" string as other posters got, so it seems there are at least three of us with this problem, using the latest version (1.7.1).
