Hello NTPsec community, I am developing a Windows-based, paper-only cryptocurrency market observation system. No live trading is enabled. Before starting a read-only market observation pilot, our project requires independently verified UTC evidence with a defensible total clock-error interval within ±1 second. We currently have successful diagnostic NTP offset readings from Google and Cloudflare, but these are not sufficient for formal qualification. I would appreciate guidance on: 1. An existing trusted method for capturing authenticated, traceable UTC evidence on Windows. 2. Preserving raw NTP request/response data, local UTC and monotonic timestamps, and host/session identity. 3. Establishing a defensible uncertainty and freshness model. 4. Finding a qualified independent reviewer who could assess the evidence and methodology. We prefer free or open-source tools and would like to avoid developing a custom time synchronization system. Any recommendations would be greatly ..

Gary E. Miller gem at rellim.com
Fri Oct 30 04:53:27 UTC 2026


Yo Ali!

On Fri, 30 Oct 2026 07:22:07 +0500
Ali Raza via users <users at ntpsec.org> wrote:

> I am developing a Windows-based, paper-only cryptocurrency market
> observation system. No live trading is enabled.

INteresting.

> We currently have successful diagnostic NTP offset readings from
> Google and Cloudflare, but these are not sufficient for formal
> qualification.

Who is it that is reuiqing "formal verification"?  They likely
have strong opinions on what that means.  Maybe someone else here
knows about your regulalatory compliance issues, but here we mostly
worry about IETF compliance, in addition to providing good time.


>    An existing trusted method for capturing authenticated, traceable
> UTC evidence on Windows.

I dount you find more than a few Windows people here.

>    Preserving raw NTP request/response data, local UTC and monotonic
>    timestamps, and host/session identity.

Identity is easy, just configure your chimers to a small trusted
fix set.  Then use NTS.  Have NTPSec log a lot.  Consider ntpviz to
summarize the log data.

>    Establishing a defensible uncertainty and freshness model.

ntpviz again.

>    Finding a qualified independent reviewer who could assess the
> evidence and methodology.

Who defines "qualified"?  Your regulator will have something to say
on that.

> We prefer free or open-source tools and would like to avoid
> developing a custom time synchronization system.

NTPSec will be all you need.  Maybe with gpsd for a local chimer.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 283 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/users/attachments/20261029/16126969/attachment.bin>


More information about the users mailing list