Transaction

01d66a3b2b45f4fe075b21877500a8badf638305597b8f25eb82c09e64c2ed42
Timestamp (utc)
2024-03-22 08:54:19
Fee Paid
0.00000008 BSV
(
0.00951539 BSV
-
0.00951531 BSV
)
Fee Rate
10.52 sat/KB
Version
1
Confirmations
94,129
Size Stats
760 B

2 Outputs

Total Output:
0.00951531 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMü<div class="post">I'd go for a small server that returns a unix timestamp, the client fetches it, computes the clock drift (difference in time) and all the protocol related times are based on that drift. The clocks would still drift a little (they'd do it anyway on the system clock) and we would not get perfect synchronization (impossible in distributed systems), but it would solve our current problems.<br/><br/>The code is about 5 lines and some simple math (sums) when calculating the timestamps.</div> text/html
    https://whatsonchain.com/tx/01d66a3b2b45f4fe075b21877500a8badf638305597b8f25eb82c09e64c2ed42