NIKX-Tech / NIKX-Tech/numx

Academic paper: outline, venue, benchmark methodology

Open
#76 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
C
Stars
23
Forks
2
PR merge metrics
No merged PRs in 30d

Description

README.md's Citation section references a paper as "once published" but no
outline or venue has been decided yet. This tracks getting that started:
outline, target venue, and confirming the benchmark methodology
(cross-platform validation results already collected under
validation/results/) is presentable as-is or needs additional controlled
experiments.

Promoted from backlog after outside review (Sepand): the algorithms and
validation methodology are publication-grade, provided two things land
first, both tracked separately:

  • Citation audit of the crypto modules (see the new "Citation audit" issue)
  • An AI-assisted-development disclosure section suitable for a journal
    submission, distinct from CONTRIBUTING.md's dev-facing note (see the new
    "AI-assisted development disclosure section" issue)

#87 (NTT/PQClean cross-validation) is the template for the validation
rigor this paper will describe.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Citation section in README.md and the existing results under validation/results/. Use #87's NTT/PQClean cross-validation as the template for assessing the benchmark methodology, then define the paper outline and target venue. Done means recording whether the current results are presentable or identifying the controlled experiments still needed, alongside the separately tracked prerequisites.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
documentation, testing-qa
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.