Hi, thank you for the bug report.

This message is shown when the time on user's PC is vastly different from the time of the backend (few minutes) - thus a signature with incorrect timestamp is produced.

Still this should not happen as the website is supposed to synchronize time with the backend and should work even in such case.

To find out why it still happens, I've added information to the test page: https://chat.peakd.com/signbuffertestpage where you could copy the times and let us know what these say or check if they are similar (within ~3s) and if not the time offset should be set to an approximate difference:

Local time: Fri May 24 2024 12:21:42 ...
Hive time: Fri May 24 2024 12:21:42 ...
Node time: Fri May 24 2024 12:21:43 ...
Time offset: 0