Closed
Milestone
Jan 29, 2024–Feb 7, 2024
Data-Availibility Layer (DAL): Split the SRS
Context
Some problems were raised related to the current cryptographic protocol used by the DAL:
- Memory consumption is too high because of the SRS size
- The guarantees by the commitment proofs are wrong because of the polynomial degree check. This could lead to a security issue.
- The time taken by the verifier for checking the validity of a shard can be too long for big stakers
This milestone will only target the first issue
Solutions
- Splitting the SRS between a SRS for the verifier and one for the prover
Work breakdown
-
(François) (hours) Small refactorisation !11734 (merged) -
(Anne-Laure) (days) Loading the SRS of the verifier at top-level !11685 (merged) -
(Anne-Laure) (days) Load the zcash SRS for the verifier !11807 (merged) -
(François) (days) Provide a benchmark for cryptographic primitives !11583 (merged) -
(François) (days) Fix the integration of the SRS within the DAL node !11837 (merged) -
(François) (days) Ensure that the DAL node by default use the verifier SRS (moved to %Data-Availibility Layer (DAL): Finish the integration of the cryptographic protocol ) -
(Anne-Laure) (days) Clean up the SRS integration in DAL crypto !11902 (merged) -
(Anne-Laure) (days) Extends the benchmark to include zcash SRS !11929 (merged)
Loading
Loading
Loading
Loading