Submission Guidelines
General Guideline
Overview
This challenge is open for researchers, fact-checkers, and relevant professionals. Participants have two options for submission:
With ACMMM 2025 Publication
Without ACMMM 2025 Publication
Each team is expected to submit two artifacts:
Results
Reports or Papers
The format and requirements for each artifact depend on the publication option chosen.
Results Submission
The format of the results submission for each task is outlined in the corresponding task sections. Ensure that all results are clearly formatted according to the provided specifications.
Reports or Papers Submission
Option 1: Freestyle Report (Non-Publishing Option)
For teams not intending to publish with ACMMM 2025, a freestyle report is required.
Format:
PDF Document
Freestyle Text that provides a detailed explanation of the approach and methodology used to solve the challenge.
There are no strict formatting guidelines; however, clarity and structure are encouraged.
Option 2: Technical Paper (ACMMM 2025 Publishing Option)
For teams intending to publish with ACMMM 2025, a technical paper (6+2 pages) must be submitted.
Submitted papers (.pdf format) must use the ACM Article Template. Please remember to add Concepts and Keywords. Please use the template in traditional double-column format to prepare your submissions. For example, word users should use Word Interim Template, and LaTeX users should use sample-sigconf-authordraft template. When using sample-sigconf-authordraft template, for submission and review of manuscript you could use the following documentclass command instead of the example provided in the template:\documentclass[sigconf, screen, review, anonymous]{acmart}
Submission Link:
The result submission link for both Main Task and Sub Task: https://mv.fotoverifier.eu/
Main Task - Results Format
Participants must submit ZIP files that contain detailed verification report in Markdown (.md) format for each assigned case (10 validation cases of Stage 1 and 10 live cases if the team is qualified for the Final Stage). The submission should follow these guidelines:
File Format and Naming
- Reports must be in Markdown (.md) format. The file name of the report is
report.md - Folder report contains supporting media files for the MD file.
- The submission file for each case is the ZIP file that contains above files and folders with this name:
teamname_caseID.zip - You can find the sample here.
Report Structure
Each report should include the following sections:
# Case Summary
- Brief overview of the verification findings.
# Content Classification
- **Tags:** Assign relevant tags based on platforms, people, brands, or specific topics (e.g., TikTok, Trump, Coca-Cola, Ukraine War, or AI-generated).
# Verified Evidence
- **Source Details:** Identify where the content originates (URLs, original posts, metadata).
- **Where? (Location):** Determine the correct geographical context.
- **When? (Time):** Establish the accurate timeframe.
- **Who? (Entities Involved):** Identify key individuals or groups.
- **Why? (Motivation or Intent):** Provide a reasoned explanation of possible intent.
# Forensic Analysis
- **Authenticity Assessment:** Determine if the content is synthetic, modified, or recaptured.
- **Verification Tools & Methods:** Clearly document the tools and techniques used.
- **Synthetic Type (if applicable):** Identify AI-generated content (e.g., GANs, Stable Diffusion).
- **Other Artifacts:** Note any detected anomalies or manipulations.
# Other Evidence & Findings
- **Supporting Sources:** Use additional fact-checks, reports, or metadata to back claims.
- **Cross-Checking Information:** Ensure verification through multiple independent sources.
- **Other Info:** Unclassified supporting evidence and analysis.
OOC Subtask - Results Format
Docker Container
We recommend that challenge participants submit their solutions as a Docker container, since it will make sure that we don’t get any errors resulting from software incompatibility issues or any other similar reason. In this case, we recommend them to follow the instructions given under https://github.com/detecting-cheapfakes/detecting-cheapfakes-code.
Standard Python Executable
If the participants face any difficulties in submitting their solutions as a Docker container, or if they feel more comfortable submitting their solution as a standard Python project, they can do so by following the instructions below. It would also be helpful for us if the participants use PyTorch as the main library if they would like to submit their Python projects, however, this is not compulsory.
- We expect that the submitted code will be executable by a single command, for example:
python solution.py <path to folder containing the hidden test split file private_test.json> - Participants should expect the same format for both the
private_test.jsonfile and thepublic_test.jsonfile. - To cope with any software incompatibility issues, we request the participants to provide a
requirements.txtfile along with their solutions, containing the names and specific version numbers of software packages used. This is fairly easy to do with both Conda (conda list), and Pip (pip list). We recommend that the participants use Conda and create a fresh environment before starting to write the code for their challenge solution.
Jupyter Notebook
Participants can also submit their solutions using Jupyter notebooks, by following the instructions below.
- Participants should structure their code so that it allows us to change the input path by updating a single line in the main file, i.e., the submitted notebook should be executable after changing the
INPUT_FOLDERparameter from the path for the public test split file, to the path for the private test split file, as shown below:INPUT_FOLDER = <path to folder containing the hidden test split file private_test.json> - Participants should expect the same format for both the
private_test.jsonfile and thepublic_test.jsonfile.
Submission Filename
The submission file name should be in the format: teamname_subtask.zip