> To defend against duplicate messages, we employ an embedded key/value store - namely, RocksDB. RocksDB contains an in-memory Bloom Filter that we use to check for, and ignore, previously applied messages.
Wait, what? Can anybody explain this part? I don't understand how you could use a bloom filter for this. A bloom filter will have false positives by definition. When a false positive is encountered, the message would be ignored even though it has not been previously applied? I'm guessing the explanation is missing something as this seems a very straight forward issue to miss.