3 ms·
> Each time a node has an internal event, it hashes that event with k hash functions and increments its bloom filter. Isn't this effectively
by remcob 7y ago
> Each time a node has an internal event, it hashes that event with k hash functions and increments its bloom filter.
Isn't this effectively the same as generating k random indices? In other words, would the bloom filter work equally well if we pick k random indices to update?
In regular bloom filters this won't work because we want identical elements to collide, but here that doesn't appear to be a concern. I can see how we might want identical nodes to collide (i.e. have the same node use the same indices over and over), but that is not what is going on.
- irwt 7y agoImagine that node A and B are in sync (they have the same bloom filter). If A sends a new event to B, B can check if A's new event really results in that new bloom filter. You basically have a cryptographic proof that an event really happened at that moment. If the hashes of an event point to different indices, you know that something is wrong. Edit: Typo.