Quantum Code Golf

Description

• Quantum Code Golf is an online individual coding competition focused on quantum programming and code optimization. Participants must generate a specified target quantum state or unitary using a compact program while minimizing the number of quantum gates used.
• Participants will work within the specified quantum programming framework, language, gate set and allowed libraries. Each valid submission will first be checked for functional correctness and rule compliance. Valid solutions will then be compared using the published code-length and gate-count metrics, with the final leaderboard determined according to the competition rules.

Duration

- Total Duration: 90–120 minutes

Rules & Guidelines

• Eligibility
• Participation is individual.
• Participants must satisfy the eligibility requirements specified in the official event announcement.
• Participants must provide accurate registration information.
• Participants must have access to the supported quantum-programming environment.
• Competition Format
• Participants will receive one or more target quantum states or unitaries.
• The objective is to construct the required target using the permitted programming framework and gate set.
• Solutions must satisfy the published correctness requirements.
• Among valid solutions, optimization will be based on the published code-length and/or quantum-gate metrics.
• Supported Environment
• The official programming language and quantum framework will be specified before the competition.
• Only the libraries, gates and resources explicitly permitted by the organizers may be used.
• Participants are responsible for ensuring that their development environment works before the competition begins.
• Correctness
• A submission must generate the required target quantum state or unitary within the specified tolerance or correctness conditions.
• Incorrect solutions will not qualify for optimization scoring.
• The organizers may use automated tests to verify correctness.
• Code Length

The competition must clearly define how code length is measured.

The published rules should specify whether code length is measured by:

• Number of characters
• Number of tokens
• Number of lines
• Or another defined metric

Only the officially specified metric will be used for ranking.

6. Gate Count

The competition must define which quantum gates are counted.

The published rules should specify:

• Allowed gate set
• How gates are counted
• Whether multi-qubit gates have special weighting
• Whether measurement/reset operations count
• How composite gates are treated
• Submission

Participants must submit their solution through the designated platform.

The submission must:

• Follow the required format.
• Contain executable/valid code.
• Generate the required target.
• Comply with the permitted library and gate restrictions.
• Be submitted before the official deadline.
• Optimization Ranking

Only valid solutions will be considered for ranking.

The leaderboard will be determined using the officially published optimization metrics, such as:

• Correctness
• Code length
• Gate count

The exact priority and weighting must be published before the competition begins.

• External Resources
• Participants may use only resources explicitly permitted by the competition rules.
• Unauthorized libraries, hidden resources, external solutions or prohibited APIs are not allowed.
• Participants must not access or use information intended to bypass the competition's challenge.
• AI Tools

The use of AI coding assistants or generative AI tools must follow the official competition policy.

If AI assistance is restricted or disclosure is required, participants must comply with those requirements.

• Originality
• Participants must independently develop their submissions unless collaboration is explicitly permitted.
• Copying another participant's solution is prohibited.
• Code similarity checks may be performed.
• Submissions found to violate the originality rules may be disqualified.
• Technical Verification

Top-ranked submissions may be inspected to verify:

• Functional correctness
• Code validity
• Gate-count accuracy
• Code-length calculation
• Compliance with allowed libraries/gates
• Reproducibility
• Absence of prohibited resources
• Tie-Breaking

If multiple participants achieve the same score, the published tie-break mechanism will be applied consistently.

14. Disqualification

A participant may be disqualified for:

• Ineligible participation
• Incorrect or fraudulent registration information
• Invalid solutions
• Use of prohibited libraries or resources
• Manipulation of the evaluation system
• Copying another participant's code
• Unauthorized collaboration
• Attempting to exploit the judging system
• Submission after the deadline
• Violation of any published competition rule
• Final Results

The leaderboard will be finalized after correctness and technical verification of the relevant submissions.