RSA Accumulators in Cryptography
- RSA Accumulators are cryptographic primitives that condense sets into constant-size group elements, enabling efficient membership and non-membership proofs.
- They rely on the strong RSA assumption and are optimized through techniques like prefix-suffix products and precomputed trees for dynamic updates.
- RSA Accumulators are pivotal in applications such as certificate revocation, authenticated PKI, and blockchain state commitment due to their low communication overhead.
An RSA accumulator is a cryptographic primitive that compresses a set of values into a single constant-size group element, supporting efficient (non-)membership proofs with security rooted in the strong RSA assumption. The RSA accumulator is a principal example of asymmetric cryptographic accumulators and is widely deployed for privacy-preserving set-membership, verifiable data outsourcing, efficient certificate revocation, and blockchain state commitment. Its operation and performance have been formalized and optimized across several application domains (Cebe et al., 2019, Ozcelik et al., 2021, 0905.1307, B, 2020).
1. Mathematical Structure and Core Algorithms
Let be a security parameter (commonly $2048$ or $4096$). Initialization requires generating two strong primes and setting the RSA modulus . Let (which is kept secret). Select randomly from the group of quadratic residues or from . The system’s public parameters are , and optionally a hash-to-prime function for mapping arbitrary data to unique prime representatives.
Given a multiset , map each to a prime and compute the accumulator value as
This construction is quasi-commutative: the resulting is independent of the order of accumulation due to (Ozcelik et al., 2021).
- Membership Proof: To prove , provide . Verification: .
- Non-Membership Proof: To prove , find integers such that (via extended Euclidean algorithm with ), and publish . Verification: (Cebe et al., 2019, Ozcelik et al., 2021).
2. Security Properties and Assumptions
The RSA accumulator’s collision resistance is based on the strong RSA assumption: given , it is infeasible to find with . A valid membership witness for would allow computation of an -th root of , where is the prime representative of , violating strong RSA (Ozcelik et al., 2021).
Soundness is uniquely tied to the difficulty of extracting or producing forged roots in . Non-membership soundness requires the trapdoor ; otherwise, non-membership proofs cannot be constructed, preventing adversarial removals (Cebe et al., 2019).
3. Efficient Update and Dynamic Operations
Adding an element (prime representative ) to the accumulated set: . Deleting (requires knowledge of ): . Witness updates propagate by raising previously computed witnesses to or as appropriate. In trapdoorless (public) settings, deletions are not supported (Cebe et al., 2019, Ozcelik et al., 2021).
To accelerate membership proof computation in dynamic or large sets, several optimizations are deployed:
- Prefix-suffix products: Compute all witnesses with multiplications and exponentiations (Cebe et al., 2019).
- Precomputed trees: Two-phase tree algorithms deliver query time at the expense of update at the source (0905.1307).
- Parameterization: Partition into blocks (e.g., ), balancing source update and directory query time at (0905.1307).
- Hierarchical accumulations: Multilevel partitions trade performance for mixed workloads (0905.1307).
4. Complexity, Communication, and Storage
The accumulator, witnesses, and proofs remain constant size (, with ). Core complexities:
- Full accumulation: prime multiplications, exponentiation.
- Incremental add: exponentiation.
- Witness generation: (naive) or (with precomputation or trapdoor).
- Verification: exponentiations (Ozcelik et al., 2021, Cebe et al., 2019, 0905.1307).
- Non-membership proof: one extended GCD and exponentiation.
- Communication: one group element (membership), one group element plus integer (non-membership), typically $2048$ or $4096$ bits per proof.
The following table summarizes asymptotic costs for key accumulator variants (0905.1307):
| Scheme | Source Update | Directory Query | Proof Size | User Verify |
|---|---|---|---|---|
| Naive | / | |||
| Precomputed | ||||
| Parameterized | ||||
| Hierarchical |
5. Applications
RSA accumulators are applied in certificate revocation, verifiable set-membership in public key infrastructures, anonymous credentials, and consensus mechanisms in blockchains.
- Certificate Revocation: In AMI/IoT, accumulators compress thousands of revoked certificates into a single digest with per-device proofs. For revoked certificates, full CRL storage is reduced from MB to MB, and distribution overheads shrink by two orders of magnitude at a cost of $9.8$ ms per modular check (Cebe et al., 2019).
- PKI Authenticated Dictionaries: Dynamic accumulators support time-stamped, efficiently verifiable online repositories with sublinear update and query costs (0905.1307).
- Blockchains: In securePrune, RSA accumulators succinctly commit to the UTXO set, supporting block pruning and rapid node bootstrapping. With , , storage is capped at $400$ MiB (an reduction) and sync times decrease by . Non-interactive PoE protocols embed accumulator transitions efficiently in block headers (B, 2020).
6. Construction Techniques and Parameter Choices
Prime-representative mapping (hash-to-prime) is pivotal for accumulator soundness. Generic mapping is achieved via
with minimal for to be prime (Cebe et al., 2019).
Modern deployments use $3072$- or $4096$-bit for $128$-bit classical security. Recommending prime representatives of at least $256$ bits mitigates divisor attacks (Ozcelik et al., 2021). The function is application-dependent and must be collision-resistant.
RSA accumulators are classified as:
- Public: no trapdoor; only additions, larger/less efficient witnesses.
- Private: trapdoor known; supports deletions, fast updates, but requires trust in manager.
- Universal: both membership and non-membership proofs (requires trapdoor) (Ozcelik et al., 2021).
7. Comparative Context and Limitations
Compared with Merkle trees (hash trees) and authenticated skip lists, RSA accumulators uniquely achieve -size proofs and verification time, independent of (0905.1307). However, public (trapdoor-less) accumulators only support additions, whereas witness and deletion efficiency in fully dynamic settings require a trusted party holding , introducing potential vulnerabilities.
Efforts to obviate the need for private trapdoors continue, but as of these constructions, only trapdoor-based accumulators enable efficient membership and non-membership proofs for dynamic sets (Ozcelik et al., 2021).
References
- "Communication-efficient Certificate Revocation Management for Advanced Metering Infrastructure and IoT" (Cebe et al., 2019)
- "An Overview of Cryptographic Accumulators" (Ozcelik et al., 2021)
- "An Efficient Dynamic and Distributed RSA Accumulator" (0905.1307)
- "securePrune:Secure block pruning in UTXO based blockchains using Accumulators" (B, 2020)