pull down to refresh
@ek had a late night, but he should see this when he comes online. wallet logs and satistics are disjoint but he's been working on relating them together better.
Cool! It's not urgent for me personally, just a discrepancy so I thought I'd let y'all know.
One thing to note is that sender logs are stored in the browser. So if you're using multiple devices, the wallet logs for a send wallet will only correspond to sends on the device that conducted the send - ie it won't show on other devices. Satistics represent what the server knows about all devices. So that's at least one reason there might be a discrepancy.
Anyway, just wanted to provide a bit more info. We are currently doing an iteration on wallets and satistics so we appreciate the feedback!
Oh! That actually makes sense! This may very well be what happened here and my assumption that this was part of the sync was wrong...
@ek plans to sync sender wallet logs for this reason. We initially thought sender logs might have sensitive info in them, but over time we realized they don't and syncing them would improve UX issues like this.
What's the best way to go about debugging that?
Can you share the payment hash of the one you can see in satistics?
8bb24de6153e955065e6f7249d37054e74d2a7070c10a29095c972503d01fb8d
No worries, you did not bother me!
I've been testing cashu NWC since after @ek's encouragement last week it turned out that connecting works now.
It works-ish in practice but SN side I'm missing an invoice in
wallet logsthat I do have onsatistics. What's the best way to go about debugging that?