N2c local submission rejects message at very beginning of epoch (Clock Skew)

[jpraynaud]

Why

At the beginning of an epoch the message sent to the DMQ network are rejected likely due to clock skew. On the publisher node the n2c local submission mini-protocol rejects messages with the following error:

{"event":{"bearer":{"localAddress":"/ipc/dmq.socket","remoteAddress":"/ipc/dmq.socket@73"},"event":{"kind":"TraceReceivedMsg","sigId":"5646b7cad1084af5e47644b8fc145d36d6fe5e7198cb61629ea27db1b924294e660f493cdbec84972259b2fcf3ef4a1767629cd79f5f9db5805090eb41040c2f"}},"time":"2026-01-16T00:03:02.267896159Z","type":"LocalMsgSubmission.Server"}
{"event":{"bearer":{"localAddress":"/ipc/dmq.socket","remoteAddress":"/ipc/dmq.socket@73"},"event":{"kind":"TraceSubmitFailure","reason":{"reason":"ClockSkew","type":"invalid"},"sigId":"5646b7cad1084af5e47644b8fc145d36d6fe5e7198cb61629ea27db1b924294e660f493cdbec84972259b2fcf3ef4a1767629cd79f5f9db5805090eb41040c2f"}},"time":"2026-01-16T00:03:02.268004078Z","type":"LocalMsgSubmission.Server"}
{"event":{"bearer":{"localAddress":"/ipc/dmq.socket","remoteAddress":"/ipc/dmq.socket@73"},"event":{"message":{"agency":"SingBusy","kind":"MsgRejectTx","reason":{"reason":"ClockSkew","type":"invalid"}},"type":"SendMsg"}},"time":"2026-01-16T00:03:02.268061722Z","type":"LocalMsgSubmission.Protocol.Server"}

This error is received for more than 3 hours (from 2026-01-16T00:05:02.24051588Z to 2026-01-16T03:27:02.274520522Z).

What

Add some tolerance for supporting some clock skew between nodes at epoch boundaries.

How

• Support clock skew at epoch boundaries

[crocodile-dentist]

We will need to add/enhance the tracing to see what is causing this.