"Short factoring proofs" - inconsistent parameters
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- cryptography, documentation
Research direction
Read the “Short factoring proofs” article, especially the “Security parameters” and “Choice of security parameters” sections, and compare their notation with the referenced PS00 paper. Resolve whether m or K should name the number of z_i values, remove the redundant parameter, and add the requested guidance on its relationship to k.】【。
Written by the indexing model from the issue text.
Description
In the article "Short factoring proofs" under "Security parameters:" you list among others "$m$, and $K$". However, $K$ is never used in the rest of the article. Instead, $m$ takes the role of $K$ (from the original paper [PS00]), denoting the number of $z_i$'s. I suggest to rename $m$ to $K$, or vice versa, so that there are no more redundant security parameters.
Also, it would be nice to give more details on the choice of $K$/$m$ in the respective section "Choice of security parameters". For example, you write "$B$ and $\ell$ should satisfy $\ell \cdot \log B = \theta(k)$", so you could add something like "$K$/$m$ should be approximately equal to $k$" (or, heuristically, even smaller, cf. [PS00]).
- Dominant language
- HTML
- Stars
- 189
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from trailofbits/zkdocs
-
Dark modeOpen
Difficulty 4/5 3-5 days Newbie friendliness 45/100
trailofbits/zkdocs#69 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
trailofbits/zkdocs#44 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
trailofbits/zkdocs#19 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
trailofbits/zkdocs#18 · 2 comments ·
-
HACSpecOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
trailofbits/zkdocs#7 · 2 comments ·
All issues in trailofbits/zkdocs
Similar issues
-
French BIP39 wordlist starts with a UTF-8 BOM, so generated French mnemonics carry U+FEFF and derive a non-canonical seedPossibly taken @Kshot3000 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 91/100
ergoplatform/sigma-rust#976 ·
Maintainers usually reply within 1 day
-
init variableOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
EVerest/EVerest#3052 · 1 reaction ·
Maintainers usually reply within 2 days
-
[Defect]: FFDH pattern treats ephemeral E as requiredPossibly taken @Mehrn0ush claimed this 2 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
CycloneDX/specification#1147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
midnightntwrk/midnight-zk#558 ·
Maintainers usually reply within 1 day