Submission Topics:
Indocrypt 2026 invites original contributions on all technical aspects of cryptology. We welcome submissions of any cryptographic topic, including but not limited to:
- Access Control
- Applied Cryptography
- Attacks & Malicious Code
- Authentication & Identification
- Blockchain Security and Privacy
- Cryptographic Protocols
- Cryptanalysis
- Data and Computation Integrity
- Edge/Fog Computing Security and Privacy
- Embedded System Security
- Formal Methods for Security
- Game Theory for Cryptography
- Hardware Security
- Lightweight Cryptography
- Machine Learning for Security
- Multi-Party Computation
- Network Security
- Privacy-Enhancing Technologies
- Public Key Cryptography
- Post- quantum cryptography
- Quantum Cryptography
- Secure Voting
- Security & Privacy
- Secure Distributed Computing
- Security in the Internet of Things
- Symmetric Key Cryptography
- Zero-Knowledge Proofs
Important Dates
Submission deadline: Aug 27 (EoD, AoE), 2026
- Final notification: Oct 10, 2026
- Conference: Dec 13-16, 2026
Instructions for Authors
Submissions must not substantially duplicate work that any of the authors has published elsewhere or has submitted in parallel to any journal or any other conference or workshop with formally published proceedings. Authors may also not submit the work to any other journal or conference/workshop with published proceedings until the date of notification. Accepted submissions may not appear in any other conference or workshop that has proceedings. Information about submissions may be shared with program chairs of other conferences for the purpose of detecting duplication.
The submissions must be written in English. It must be anonymous, with no author names, affiliations, acknowledgements, or obvious references; all submissions will go through a double-blind peer-review process. Submissions must be submitted after processing in LaTeX2e using the Springer LNCS format with default margins and font. The paper must begin with a title and must contain the following columns accordingly: a short abstract, a list of keywords, the main body, appendices (if any), and references. The main body must commence with an introduction that concisely summarizes the paper's contributions in a way that is comprehensible to a general cryptographic reader. The paper must not exceed 20 pages (including appendices, if any, but excluding references) in length after being formatted in LNCS style. All submissions must have page numbers, e.g., using LaTeX command \pagestyle{plain}. Appendices (if any) should be placed after the main body and before the references. Failure to meet the aforementioned standards may result in rejection at an early stage. Significant changes between the submitted version and the published version should be approved by the program committee.
If there is any additional supporting material, such as source codes, proofs, or other files supporting verification of the results, it should be included in the main paper after the references. There are no prescribed format and page restrictions for the supporting material, but it should be clearly labelled. However, the submission should be self-contained and intelligible as the committee members will read additional supporting materials at their discretion. Note that unverifiable data or results may risk rejection.
The proceedings will be published by Springer in the Lecture Notes in Computer Science series. All accepted papers must conform to the Springer publishing requirements, and authors will be required to sign the Springer's LNCS Copyright form when submitting the proceedings version of their paper. By submitting a paper, the authors agree that if the paper is accepted, one of the authors will present the paper at the conference.
Papers must be submitted electronically in pdf format.
Conflicts of Interest (CoI)
The conference requires cooperation from both authors and program committee members to ensure a fair review process. For this purpose, authors must report all program committee members who, in their opinion, have a conflict of interest and therefore may not be able to provide an unbiased review. An author is mandated to declare a conflict with a program committee member if they:
- share an institutional affiliation at the time of submission;
- had at any time in the past a supervisor/PhD student relationship;
- have collaborated or published within the prior two years;
- are in some form of financial relationship, or have been at some point during the past two years;
- are related, or have close personal friendships.
For other forms of conflict, authors must contact the program chairs and explain the perceived conflict. Authors also need to notify the program chairs of any other reason or circumstance that creates a risk that professional judgment may be unduly influenced.
The program chairs reserve the right to request further explanation and can remove non-mandatory conflicts at their discretion.
Program committee members (including the program chairs) who have a genuine conflict of interest with a paper, will be excluded from evaluation and discussion of that paper. When a program chair is conflicted, the other co-chairs will be responsible for managing that paper. If all program chairs are in conflict, a committee member will be appointed to handle the paper. Program chairs are not allowed to be authors or co-authors of any submissions.
Submit Paper