Time calculations could be wrong when device resumes from sleep. This is important since we are doing payment checks based on time.

References for this issue.

1. https://go.googlesource.com/proposal/+/master/design/12914-monotonic.md
2. time: use monotonic clock to measure elapsed time golang/go#12914
3. time: Sub is inaccurate after computer has slept golang/go#23178
4. runtime: use CLOCK_BOOTIME, not CLOCK_MONOTONIC, when possible golang/go#24595
5. time: NewTimer firing later if computer sleeps, how to use wall clock? golang/go#35012
6. time: add ExternalNow, etc for external time and timers golang/go#36141

WireGuard fixed it by pathing Go. See here.