Message rejection when timestamps are equal

[realbigsean]

builder-specs/apis/builder/validators.yaml

Line 9 in e602513

must error. Requests with `timestamp` less than or equal to the previous

The above validation results in duplicates of valid messages returning: {"code":400,"message":"invalid timestamp"}

I was under the impression registrations needed to be re-signed infrequently, and the once per epoch registration we are sending would be a duplicate.

This timestamp requirement also creates a re-signing once per epoch requirement (or however frequently we re send registrations), which could add a lot of load for a client running a lot of validators.

[ralexstokes]

also #24