Quote from: capulo on December 26, 2019, 11:46:53 PM

Quote from: sunk818 on December 26, 2019, 09:48:24 PM

Quote from: bible_pay on December 26, 2019, 09:10:22 PM

Oh we have two, ok, Im compiling a new wallet now to diagnose this.

Ill check both. Its hard to believe that on the go-live date, WCG would have a bad file, but let me keep checking.

@capulo - quit bbp wallet, and try erasing SAN/wcg.rac, restart wallet

Is the RAC the explicit value from WCG user.gz ?

Looks like what I see in BiblePay debug.log (referenced by SAN/wcg.rac I assume, is an old file from Dec 14th.)

GMT: Thursday, December 26, 2019 6:14:45.930 PM
Your time zone: Thursday, December 26, 2019 10:14:45.930 AM GMT-08:00
Relative: 4 hours ago

GMT: Saturday, December 14, 2019 6:12:02.292 PM
Your time zone: Saturday, December 14, 2019 10:12:02.292 AM GMT-08:00
Relative: 12 days ago

I see from Dec 13, the RAC for capulo was about 91k

Code:

1066130
capulo
SLOVAKIA
1523366299
73312472.726368
124044.285283
1577384085.930994
e7c056024cd3b781edd5af37965c652c
35006

From the latest debug.log, I see the following of 91k RAC

Code:

1066130
capulo
SLOVAKIA
1523366299
71695793.027780
91775.569413
1576347122.292800
e7c056024cd3b781edd5af37965c652c
35006

where is user.gz file?
but you are right, if you check total credit, it also goes down so it is historical data

ps: now i see 124k rac, seems ok (i did only restart)

No the client isnt looking for that user.gz file, he was making an assumption.

The problem has been resolved, lets wait for the sanctuaries to resync and verify the upcoming leaderboard looks correct now.