Rateless Bloom Filter (RBF) Overview
- The paper introduces RBF as an adaptive protocol that streams one-hash slices to achieve near-optimal metadata reduction in set reconciliation.
- RBF is characterized by its incremental, slice-based approach that dynamically reduces false positives without prior knowledge of divergence.
- Experimental results show up to 92% metadata reduction and improved communication efficiency compared to static Bloom filters in diverse similarity regimes.
Searching arXiv for the specified papers and closely related Bloom-filter work. arxiv_search query: (Gomes et al., 31 Oct 2025) Rateless Bloom Filter (RBF) denotes, in the set-reconciliation formulation introduced in 2025, a Bloom filter transmitted incrementally as a stream of one-hash slices, so that the receiver can stop exactly when another increment would no longer reduce total communication cost. The term is not used in that sense in the Bloom-filter optimization survey of 2018, which instead treats growable Bloom-filter families such as Dynamic Bloom Filter, Scalable Bloom Filter, Dynamic Bloom Filter Array, and Par-BF, while separately covering Retouched Bloom Filter, a different design that is sometimes abbreviated as RBF in other literature (Gomes et al., 31 Oct 2025, Luo et al., 2018).
1. Terminology and position within Bloom-filter literature
The 2018 survey does not introduce a variant named Rateless Bloom Filter. Its closest matches to a “rateless” or growable Bloom filter are the dynamic-set constructions in Section 6.2: Dynamic Bloom Filter (DBF), Scalable Bloom Filter (SBF), Dynamic Bloom Filter Array (DBA), and Par-BF. These are presented as responses to the “elasticity” challenge, namely dynamic capacity extension without fixing a priori upper bounds. By contrast, the survey’s Retouched Bloom Filter is a fixed-filter false-positive reduction technique based on selectively clearing bits and accepting controlled false negatives; it is orthogonal to rateless growth (Luo et al., 2018).
Within the classical Bloom-filter framework, the survey gives the standard approximations , , and . It also notes that the approximation is a lower bound and provides a more accurate exact expression using Stirling numbers. These relations supply the parameter vocabulary used by both growable Bloom filters in the survey and the later rateless reconciliation construction (Luo et al., 2018).
The 2025 RBF paper narrows the meaning of “rateless” to an adaptive communication protocol rather than merely a dynamically extensible membership structure. In that setting, ratelessness means that the sender can, in principle, stream an unbounded number of Bloom-filter slices, while the receiver determines the stopping point from observed marginal utility. This shifts the design objective from storage elasticity to communication optimality under unknown difference cardinality (Gomes et al., 31 Oct 2025).
2. Problem setting: set reconciliation with unknown divergence
RBF is defined for set reconciliation between two replicas holding sets and . The objective is to identify the symmetric difference
so that both replicas can converge to while minimizing communication. The formulation assumes a symmetric difference cardinality with (Gomes et al., 31 Oct 2025).
The 2025 paper emphasizes variable-sized elements as the motivating regime. Practical workloads such as files, database rows, and transactions are not fixed-size, so the usual reduction is to reconcile fixed-size digests and fetch actual elements only after the differing items are identified. Reconciliation then becomes a metadata minimization problem: the protocol should identify the differing elements at minimum metadata cost, after which the payload transmission is unavoidable (Gomes et al., 31 Oct 2025).
Existing approaches are described as effective only in restricted regions of the parameter space. Fixed-size digest reconciliation schemes such as PinSketch achieve asymptotic 0 metadata but still incur at least 1 bits of metadata and may require 2 decoding, which becomes impractical beyond small 3. Static Bloom filters can be effective when their parameters are tuned to the realized 4, but the optimal choice depends on 5, which is unknown and may vary widely. IBLT-only approaches, including rateless IBLT, are parameter-free with respect to 6 and exact, but for large 7 their communication remains 8 with a relatively large constant, such as 9–0 symbols per difference, each symbol carrying 1, 2, and count fields. RBF is proposed as the missing prefilter that sends “just enough” Bloom filter without prior knowledge of 3 (Gomes et al., 31 Oct 2025).
A plausible implication is that RBF is not primarily a new approximate-membership data structure for static databases; rather, it is a rate-adaptive communication primitive specialized for the case in which false positives can be cleaned up by a second-stage exact reconciler.
3. Construction and protocol mechanics
The core construction is a partitioned Bloom filter decomposed into one-hash slices. If each slice uses 4 and size 5, then 6 slices emulate a partitioned Bloom filter with 7 and total size 8. The paper chooses
9
for a set of size 0, which yields the halving law
1
because 2. Each additional slice therefore halves the false-positive rate (Gomes et al., 31 Oct 2025).
Operationally, the sender streams slices continuously. Slice 3 is a bit array of 4 bits, built by hashing each element 5 with a shared hash function salted as 6 and setting one bit. The receiver applies the slice to its current candidate pool 7: elements that hit a zero bit are moved to the true-negative set 8, while elements that hit a one remain in 9. The receiver then decides whether the most recent slice justified its transmission cost (Gomes et al., 31 Oct 2025).
The full protocol is a two-stage hybrid. In Phase 1, replica 0 sends RBF slices to 1, which partitions 2 into 3 and 4. In Phase 2, replica 5 sends RBF slices back to 6, but now builds the filter over 7; replica 8 analogously obtains 9 and 0. In Phase 3, the remaining suspected common subsets are reconciled with a rateless IBLT operating on fixed-size digests. The RBF stage removes cheap true negatives, while the rateless IBLT resolves the surviving false positives exactly and identifies which side is missing which elements (Gomes et al., 31 Oct 2025).
This protocol architecture differs from the dynamic Bloom-filter families in the survey. DBF, SBF, DBA, and Par-BF grow by allocating additional subfilters as a set expands over time, with insertions directed to an active layer and queries checking multiple layers. Their goal is elasticity of a membership structure. RBF instead uses incremental slices as a transmission schedule over a fixed reconciliation instance, even though both designs exploit layered Bloom-filter composition (Luo et al., 2018).
4. Analysis, stopping rule, and near-optimality
The static Bloom-filter baseline in the 2025 analysis uses the standard false-positive rate 1, optimal hash count 2, and size relation 3. If one direction transmits a static Bloom filter of size 4, the metadata cost is 5, the expected unresolved non-members are 6, and the second-stage cost is 7. Under symmetric roles, the total cost is
8
Minimizing over 9 yields
0
which depends explicitly on the unknown 1 (Gomes et al., 31 Oct 2025).
RBF eliminates this parameter-selection problem by operating in discrete one-slice increments. After 2 slices, the false-positive rate is 3, total Bloom bits are 4, and the total symmetric cost becomes
5
The expected newly revealed true negatives at slice 6 are
7
The stopping rule is to stop when
8
or equivalently continue while
9
This yields
0
slices, so that, up to rounding,
1
The paper states that this matches the optimizer’s 2 up to rounding and keeps communication within at most one slice 3 of the optimum, without requiring prior knowledge of 4 (Gomes et al., 31 Oct 2025).
The survey’s layered false-positive analysis clarifies why this discrete rate adaptation is tractable. For a layered Bloom filter that reports positive if any layer reports positive, the total false-positive rate is
5
For homogeneous layers, this reduces to
6
which grows with the number of layers. That behavior is the baseline weakness of DBF and DBA and is precisely what motivates SBF’s parameter scheduling and, in the reconciliation setting, RBF’s slice-by-slice stopping policy (Luo et al., 2018).
5. Relation to dynamic, scalable, and retouched Bloom filters
The survey’s dynamic-set family supplies the closest antecedents to RBF. DBF uses multiple homogeneous Bloom filters activated over time; one active filter is filled to a precomputed upper bound, then a fresh filter is activated, and queries check layers sequentially. DBA organizes homogeneous Bloom filters into groups, supports scalable parallel queries, and handles deletion in batch using stale-element thresholds per filter. Par-BF employs parallel subfilter lists whose parameters are chosen to meet a global false-positive target while supporting deletion, scalability, and parallel query. SBF uses heterogeneous subfilters whose designed false-positive rates are increased geometrically, with lengths and utilizations adapted “to maintain a given false positive rate” as layers are added (Luo et al., 2018).
Among these, SBF is the strongest conceptual analogue to “rateless” growth as understood in the survey. It allows unbounded growth and controls aggregate false positives through per-layer planning rather than through fixed homogeneous replication. The survey explicitly contrasts this with DBF, whose aggregate false-positive rate rises as 7 unless compensated by larger 8 or smaller per-layer 9 (Luo et al., 2018).
The 2025 RBF differs in three ways. First, it is a communication protocol rather than an in-memory capacity-extension strategy. Second, its unit of adaptation is a one-hash slice chosen to make the false-positive rate decay by a factor of two per increment. Third, the stopping criterion is receiver-driven and cost-aware, using the estimated downstream exact-reconciliation cost 0 rather than a preset false-positive target (Gomes et al., 31 Oct 2025).
The most common terminological confusion concerns Retouched Bloom Filter. Retouched BF, covered in Section 4.3 of the survey, reduces false positives by selectively clearing 1-bits and accepting controlled false negatives through random or selective clearing strategies. It does not address capacity growth and is not a rateless scheme. Stable Bloom Filter is likewise not a growable design; it maintains a stable fraction of 1s under streams by decay or eviction and accepts false negatives. Counting Bloom Filter enables deletions via counters, but does not by itself solve growable or rateless operation without adding counters and additional space. These distinctions matter because “RBF” may refer either to Retouched Bloom Filter in some older usage or to Rateless Bloom Filter in the 2025 reconciliation protocol (Luo et al., 2018).
6. Complexity, implementation, and empirical behavior
The 2025 paper gives the following complexity profile. At the sender, each RBF slice requires 1 hashing-and-bit-setting with 2, for an overall RBF cost of 3. At the receiver, each slice requires one membership test per element in the current 4, which shrinks geometrically, giving amortized 5. The second-stage rateless IBLT has encoding cost 6 symbols, decoding cost 7, and expected decoding thresholds of approximately 8 cells for small 9 and approximately 0 as 1 grows (Gomes et al., 31 Oct 2025).
The same paper specifies several implementation choices. For RBF membership bits, the shared hash function is salted by slice index 2 to obtain per-slice independence. The paper’s experiments used 64-bit digests and 64-bit 3/4 fields; for adversarial settings or very large universes it recommends 128-bit or 256-bit digests. Slices are indexed and independent, so they can be applied out of order, and duplicates are idempotent. In adversarial settings, strong keyed hashing is recommended to prevent chosen-input false-positive inflation, while IBLT purity checks rely on 5 collision probabilities remaining negligible (Gomes et al., 31 Oct 2025).
The survey adds engineering guidance that also applies to layered or rateless deployments. Less Hashing uses two seeds to generate 6 hashes and reduces CPU cost. One Hash BF reduces hashing cost further at the expense of higher false positives. Bloom-1 and OMASS show how bit-array partitioning and blocking can align accesses to fixed-size words or blocks, enabling single-access lookups and parallelism. For large-scale storage systems, BloomStore and forest-structured Bloom filters layer RAM and flash, suggesting that multi-filter growth policies can be coupled to page and cache-line organization (Luo et al., 2018).
Empirically, the 2025 evaluation used 7 elements, varied 8 to sweep Jaccard similarity from 9 to 00, and drew variable-sized elements uniformly in 01 bytes. Against static Bloom filters, RBF reportedly tracks the theoretical best static Bloom filter across all 02 without parameter tuning, while misconfigured static Bloom filters can overshoot metadata by 03–04 depending on the regime. In the hybrid RBF–RIBLT protocol, for Jaccard indices below about 05, total communication is reduced by up to over 06 relative to the state-of-the-art minimum-metadata baseline, and compared with computationally tractable baselines the total-data reduction exceeds 07 at large 08; metadata reductions of up to 09 are reported as 10 grows. The same evaluation also identifies a narrow high-similarity regime in which the first RBF slice imposes a visible fixed cost of approximately 11 KB at 12, making pure RIBLT or PBS more efficient when similarity is at least 13 (Gomes et al., 31 Oct 2025).
These results delimit the practical scope of RBF. It is designed for moderate-to-large divergence, especially after outages or partitions, when 14 is unknown and static Bloom-filter tuning is unreliable. When replicas are almost identical, the fixed per-slice cost can dominate, so pure RIBLT, PBS, or a static Bloom filter with very high 15 may be preferable. The paper therefore positions RBF not as a universal replacement for all reconciliation schemes, but as a near-optimal adaptive Bloom-filter front end whose value increases precisely when the difference cardinality is uncertain and potentially large (Gomes et al., 31 Oct 2025).