CHES 2025 aims to support open and reproducible research within the field of cryptography. As such, authors of papers accepted to CHES 2025 are invited to submit artifacts associated with their papers, such as software or datasets, for review, in a collaborative process between authors and the artifact review committee.
For 2025, authors can choose to have their artifacts evaluated by the CHES Artifact Evaluation Committee (AEC) against two badges: Artifacts Available and Artifacts Functional. Each evaluation is optional. This system broadly follows the conventions established in recent years in security research conferences such as USENIX Security and NDSS.
We expect all submissions, regardless of the evaluation level, to adhere to the submission instructions and format outlined on this page.
The goal of the process is not just to evaluate artifacts but also to improve them. Artifacts that pass successfully through the artifact review process will be archived alongside the paper on the website of the Transactions on Cryptographic Hardware and Embedded Systems (TCHES) and at https://artifacts.iacr.org/.
Examples of this in the field of cryptography include:
Where possible, such as in software-based artifacts relying solely on open-source components, the artifact review process will aim to run the artifact and test harness, and see that it produces outputs that would be required to assess the artifact against results in the paper. For artifacts that depend on commercial tools or specialized physical hardware, the goal of the artifact review process will be to confirm that the artifacts are functional (should the submitters wish to be evaluated for functionality) and could plausibly be used by someone with access to the appropriate tools to reproduce the results.
In addition to the badges, the artifact review committee may recognize zero or more artifacts at the CHES 2025 conference as exemplars in terms of functionality, amenability to enabling reproducibility, or reusability.
The artifact review process begins after the paper has been accepted for publication in TCHES. Only papers accepted to CHES 2025 will be considered under the artifact review process.
Following notification of acceptance (or acceptance with minor revisions) to CHES 2025, the artifact may be submitted for review up to the next artifact submission deadline.
For papers accepted to TCHES Volume 2025 Issue 1
For papers accepted to TCHES Volume 2025 Issue 2
For papers accepted to TCHES Volume 2025 Issue 3
For papers accepted to TCHES Volume 2025 Issue 4
Once the artifact is submitted, two or more members of the artifact review committee will be assigned to review the artifact. The artifact review process will be a continuous process and may involve requests from the reviewers for additional help on how to run the artifact, interpret its results, etc. It is acceptable (and expected) that the interaction between the reviewers and the authors leads to the artifact being updated during the review process. Updates that affect scientific characteristics reported in the paper (such as changes to performance) should be clearly documented.
We aim for the artifact review process to be completed within 6 weeks of the artifact being submitted, but this will vary depending on the scale of the artifact and the timeliness of interaction between the authors and reviewers. Authors of artifacts that are accepted for archiving will be provided instructions on how to submit the archival version of their artifacts.
We ask for authors to be understanding and to join us in viewing this as a collaborative process trying to produce better artifacts for the scientific community.
The artifact review process will be single-blinded: the authors of the paper and artifact are not anonymous, but the reviewers will be anonymous. Communication between the authors and the reviewers will be facilitated via the HotCRP review site. Authors should not attempt to learn the identities of the reviewers, for example, by not embedding analytics or tracking elements in the artifact or a website; if you cannot comply with this for some reason out of your control, please notify the chairs immediately to discuss.
The TCHES 2025 artifact review process follows the same conflict of interest policy as TCHES, which is the IACR policy with respect to conflicts of interest. A conflict of interest is considered to occur automatically whenever an author of a submitted paper and a reviewer
Conflicts may also arise for reasons other than those just listed. 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. For more information please see the IACR Policy on Conflicts of Interest. Authors will be asked to identify conflicts of interest with the committee members at time of artifact registration.
In order for the IACR to distribute Artifacts, we require permission to do so. You are asked to grant the IACR permission to do so under an open-source license of your choice, such as an OSI-approved license. As some Artifacts may combine portions created by you and third-party materials obtained elsewhere, you must ensure that you have obtained a license to redistribute all third-party materials included in the Artifact that were not created by you, for example by including only open-source components or by otherwise obtaining and demonstrating the required permission.
It is not a requirement that any patent rights be granted.
Artifacts shall be registered and submitted via the IACR HotCRP artifact server: HotCRP Artifact Submission Server
A submission shall include:
The artifact itself shall include at least the following files:
Files such as LICENSE and README can be plain text files or Markdown files.
Source code files within the artifact are encouraged to be organized, formatted, and documented using best practices and conventions appropriate to the programming language in question. For example, formatted using a consistent style such as PEP8 for Python; documentation of APIs using JavaDoc for Java or Doxygen for C; unit tests using an appropriate framework.
This document serves as guidance on how researchers and engineers can package their hardware projects as part of the CHES Artifact Review Process. It is designed to capture best practice when it comes to improving the re-usability and reproducibility of hardware projects in the cryptographic research community.
The primary form of the artifact should be as source code, with suitable build scripts and instructions on how to install the appropriate dependencies.
For artifacts with complex dependencies or build requirements, the authors are encouraged to also package the artifact in the manner that makes it most amenable to successful execution. Potential formats include:
When in doubt, imagine a first-year grad student in 2029 who is told by their supervisor "See if you can change this artifact from CHES 2025 to do X." We want to give them the best chance of success with the least amount of pain.