Paper Submission

Anonymity

Submissions must be anonymous with no author names, affiliations, or obvious references. The list of authors is requested separately on the submission form; it will be known to the co-chairs but not made available to the rest of the program committee unless the paper is accepted. Note that, per IACR policy, the anonymity requirement does not preclude the authors from posting nonanonymized versions of their work online or talking about it.

Structure

The submission should begin with a title, a short abstract, and an introduction. There is no requirement to include keywords, but they may be supplied if helpful. The introduction should summarize the contributions of the paper and the relationship to existing work in a manner that is understandable to a general cryptographic audience.

Formatting and Page Limits

The main body of the submission must be at most 30 pages long, followed by references (which do not count towards the 30 page limit for the main body). Any amount of clearly marked supplementary material may be supplied, either as an appendix to the main body of the paper or in separate files; however, reviewers are not required to read any supplementary material, and submissions are expected to be intelligible without it.

Submissions must be prepared in LaTeX using the Springer LNCS format (without modifying the LNCS default fonts, sizes, or margins) and submitted electronically in PDF format. Details on the Springer LNCS format can be obtained. All submissions must have page numbers (e.g. using LaTeX command \pagestyle{plain}). The use of BibTeX in conjunction with LNCS’s bibliography style splncs04.bst is strongly recommended; the use of CryptoBib is encouraged.

Code and Data Artifacts

Supplementary materials may contain appropriately anonymized code or data artifacts, which the reviewers may access at their discretion during the paper review process. Alternatively, authors may include in their paper a link to an appropriately anonymized online repository; for example using this tool for anonymization of Github repositories. A separate artifact evaluation process will occur for accepted papers that wish to have their artifacts evaluated and made available on the IACR Artifact Archive; a separate call for artifacts details the submission instructions for that process.

Prior Reviews

If the submission was rejected from prior conferences, the authors are encouraged to include in their supplementary materials their responses to prior reviews, as described in the Guidelines for Authors.

Restrictions on PC Members

Program committee members are allowed to submit one paper if without student co-authors, two papers if at least one of them has a student co-author, and three papers if all of them have student co-authors. Program committee co-chairs are not allowed to submit any papers.

Exclusivity

Submissions must not substantially duplicate work that any of the authors has published elsewhere or has submitted in parallel to a journal or any other conference/workshop that has proceedings. Accepted submissions may not appear in any other conference or workshop that has proceedings. IACR reserves the right to share information about submissions with other program committees to detect parallel submissions and the IACR policy on irregular submissions will be strictly enforced.

Publication and Presentation

The proceedings will be published in Springer’s Lecture Notes in Computer Science series and will be available online. The authors of accepted papers will be expected to upload the IACR version (or the full version) of their papers to the Cryptology ePrint Archive and will be required to complete the IACR copyright assignment form. One of the authors of each accepted paper will be expected to present the paper in person at the conference (very rare exceptions to this rule can be made in case of visa problems). The presentations will be video recorded during the event.

Conflicts of Interest

Authors, program committee members, and reviewers must follow the IACR Policy on Conflicts of Interest, available from https://www.iacr.org/docs/.

In particular, the authors of each submission are asked during the submission process to identify all members of the Program Committee who have an automatic conflict of interest (COI) with the submission. A reviewer¹ has an automatic COI with an author if:

• one is or was the thesis advisor to the other, no matter how long ago;
• they shared an institutional affiliation within the prior two years²;
• they published two or more jointly authored works in the last three years³; or
• they are immediate family members⁴

A reviewer has an automatic COI with a submission if:

• the reviewer has an automatic COI with any of its authors;
• the reviewer is authoring a paper (in submission⁵ or in preparation) whose content substantially overlaps with that of the submission;
• the reviewer has made a contribution to the submission (i.e. the submission is the result of a collaboration that did not result in the reviewer's authorship)

Any further COIs of importance should be separately disclosed. It is the responsibility of all authors to ensure correct reporting of COI information. Submissions with incorrect or incomplete COI information may be rejected without consideration of their merits.

COIs are not restricted to automatic ones, others being possible. COIs beyond automatic COIs could involve financial, intellectual, or personal interests. Examples include closely related technical work, cooperation in the form of joint projects or grant applications, business relationships, close personal friendships, instances of personal enmity. Full transparency is of utmost importance, authors and reviewers must disclose to the chairs or editor any circumstances that they think may create bias, even if it does not raise to the level of a COI. The editor or program chair will decide if such circumstances should be treated as a COI.