[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

Search:


View post   

>> No.26298914 [View]
File: 22 KB, 310x400, 1363747059434.jpg [View same] [iqdb] [saucenao] [google]
26298914

I had a fun experience with the xsn core client. My wallet was feeling a little light, and my transactions weren't adding up right, I was missing thousands.
At first I thought I had sent them somewhere, but there were no outgoing transactions of that size.
Then thought I had been hacked, then that XSN PoS was somehow broken and somebody stole coins from my wallet via an attack.
Then I identified the chunk that was missing and chased it around on the block explorer and eventually found the coins still sitting there in an address that was mine, but not appearing in the wallet.
Finally I realized this was probably a client desync and went through the wallet repair options. "Recover transactions 1" was enough to find the missing coins.
This whole problem started shortly after I had sent some coins that drew from the chunk that was missing.
I can't recall any dirty client shutdowns that would have caused this desync, but there may have been clean shutdowns during that time range.
Anybody else seen this issue or did I just get lucky? Is the client database just particularly sensitive to (even proper) restarts?
tl;dr = I thought I was shidding, but I was only fardding.

Navigation
View posts[+24][+48][+96]