Closed willscott closed 7 years ago
This begins to be addressed in 57f39b9798dacc84c13fd04c38cbf6ac971b23af, where messages are signed, allowing subscriptions to validate that a message is part of the expected log.
This is now merged to master. new items in a log are signed by the writer, and validated by readers before they move on to the next sequence number.
When alternate bucket is read, or when when there is no next update, the client will get back random data that doesn't decode as expected.
libpdb/Topic
needs to maintain a checksum or otherwise know when a read is 'successful', and not advance state in that case.