Due to a change in the security policy of the University of Miami,
tool authors can no longer be given StarExec Miami accounts. Therefore,
tool submission for CoCo 2026 is no longer done by uploading solvers
directly to StarExec.

Instead, please package your solver as in previous years, so that it
can be run on StarExec Miami, and submit the resulting archive to the
CoCo SC. Since attaching solver archives directly to emails may cause
them to be rejected by mail-system filters, we recommend using a file
sharing service and sending the corresponding download link to the
CoCo SC. The SC will be responsible for running your tools as expected.

The easiest way to package your solver is to prepare a single archive
containing the following files:

bin/ -- directory containing the executables needed by your solver
bin/my_tool
bin/starexec_run_default -- the wrapper script that calls your tool
starexec_description.txt -- a short description of your tool

Please note that the contents must not be contained in an additional
folder, that is, the archive needs to extract to bin/my_tool as
opposed to mytool/bin/my_tool.

Please do not add version numbers or years to the solver name in
starexec_description.txt.

See the section about solvers of the user guide
https://github.com/StarExecMiami/StarExec/blob/b34216b356c2c6aa3644fa39467c544d1baee3ef/WebContent/public/StarExecUserGuide.pdf
for more information on the expected StarExec solver format.

If you registered for multiple categories and need to use your tool
with different configurations, you can either add multiple
bin/starexec_run_config wrapper scripts or submit multiple solver
archives. In any case please indicate in the description the intended
category for each solver/configuration.

For tools that team up with a certifier, you should no longer submit
the certifier yourself. Instead, in the description of your tool and/or
configuration indicate the certified categories you want to participate
in (e.g. "TRS+CeTA", "COM+FORTify"). In the certified categories it is
expected that your tool produces output, where the first line is the
answer (YES/NO/MAYBE) and the remaining lines contain the certificate.
For example:

YES/NO
... CPF3-output or FORTify-certificate ...

For tools that internally produce CPF2 certificates, we expect that
they run the corresponding converter to CPF3 themselves, which is
available at

https://isafor-ceta.uibk.ac.at/cpf3.html

Tool submission will be open until July 1 (AoE).