Mint time outside of tolerance - some mints about 15 minutes behind #1194
Labels
No labels
DB & Storage
Deployment
Error Handling & Logging
Maintenance
Payment Backend
backport
backport v0.13.x
backport v0.14.x
backport v0.15.x
bindings
blocked
bug
cdk-sql
ci
cli
deps
documentation
duplicate
enhancement
good first issue
help wanted
invalid
keep-open
ldk-node-ui
migrations
mint
mutation-testing
needs rebase
needs review
new nut
nut change
question
ready
rust-version
rustfmt
stacked hold
stale
testing
wallet
weekly-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cashubtc/cdk#1194
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I sometimes get these errors about timestamps, in my chat+cashu app, where CDK generates this error:
Mint time outside of tolerance. This was with coinos.io, but I think I've seen it with others too. With coinos, sometimes it works and sometimes it doesn't.Update: Here's a straightforward example. I put in some logs. I'll try to find a way to contact the mint, and close this
The mint is sometimes about 20 minutes behind. I verified my wallet's time with https://time.is/Unix_time
I removed the timecheck from the cdk and am continuing to test, so far this seems to be working:
Although, of course we do need the correct time for various spending conditions, so I'm not proposing to remove this check
Interesting thanks for finding this. I've asked the nutshell devs if nutshell somehow caches the time or if the mints system clock is just off.
Either way the tolerance is not actually something in spec and something I just put in cdk, so I think we should maybe make this a softer error as it blocking a simple receive is not a good experience. However, as you point out is an import check for spending conditions, so it should probably be in the spec more specifically as if someone is doing conditions with short term timeouts even 20 min could make a difference.
I deleted my comment from 20 minutes ago, because I discovered my clock was a bit off! Sorry about this
Now I'm not sure if I trust any of the data I've presented here :-)
No worries brings up a good point even if the data is a little off.
Cdk does store it but it only check the the time when it fetches it from the mint.
This issue is stale because it has been open for 60 days with no activity.