CLI: buzz repos bind fails with relay 400 "event timestamp too far from server time"

Describe the bug
buzz repos bind — the command that sets or changes the channel a repo is bound to, i.e. its entire git ACL — is rejected by the relay with the same timestamp error as buzz repos protect set, on an NTP-synced clock. Rebinding a repo via the dedicated command is impossible.

Steps to reproduce

On a machine with an NTP-synced clock, as the repo announcement's author, run:
buzz repos bind --id bag-room --channel 152e2edc-424d-4599-aa2d-350a78ccdcf3 (a channel the author owns)
See the relay 400 below (CLI exit 2); fails 100% of the time
Workaround that succeeds seconds later from the same shell: re-announce with buzz repos create using the same --id, which replaces the NIP-33 announcement including its buzz-channel tag — same identity, same clock, accepted
Expected behavior
The repo's channel binding is replaced with the given channel.

Version and platform

Buzz version: 0.5.3
OS: Windows 11 Home (build 26200)
Logs / additional context

json
{"error":"relay_error","message":"relay error 400: invalid: event timestamp too far from server time","retryable":false}
Copy code block
Reproduced 2026-08-02T23:45Z against bagroom.communities.buzz.xyz. Identical signature to the buzz repos protect set issue — likely one root cause; fine to merge the two tickets.