Submission

Submit challenge boxes from a private repository created from the Destrier box template.

Before you submit

Make sure the box is complete and ready to reproduce:

Item	Requirement
`box.yaml`	Valid against the current Destrier box schema.
`target/`	Contains the source, build files, or disk images required for each host.
`solver/`	Includes a reference solver that demonstrates the intended solution.
`README.md`	Documents the scenario, vulnerability, objective, capture points, solve path, and any reviewer notes.
Disk images	Included for VM hosts, including domain controllers.

You will also need the relevant local tools for your box:

Tool	Used for
`boxr`	Linting, builds, local tests, submission, and status checks.
Docker	Building container hosts.
Packer	Producing virtual machine disk images, if you use it locally.
`qemu-img`	Inspecting or converting image-backed virtual machine disks.

Keep the repository and all challenge materials private during review and after the competition.

Submit your box

Authenticate with your Destrier account:

boxr login

Lint

Check the manifest and repository structure before building:

boxr box lint [dir]

string

Optional path to the challenge box directory. Defaults to the current directory.

Fix any reported errors before continuing.

Build

Build the hosts declared by the box:

boxr box build [dir]

Container hosts are built with Docker. Build any VM disk images with your own VM toolchain before submission; prebuilt VM disk images are uploaded during submission.

Test

For container-backed boxes, start the box locally and prove the reference solver captures a declared flag:

boxr box test [dir]

boxr box test wires the local network from box.yaml, waits for the entry host health check, and runs solver/solve.py. Use --no-solve to bring the target up without running the solver, or --keep-up to leave it running after the test.Full-machine VM boxes are not tested by this command. Submit them and exercise them with boxr run on the platform.

Submit

Submit the completed box for review:

boxr box submit [dir]

The command publishes source-built container hosts, uploads prebuilt VM disk images, records generated artifact fields, and submits everything outstanding.For a box with exactly one disk-image host, pass --file <path> if the image is not where boxr would normally look.

Check status

Track the submission and any associated image uploads:

boxr box status [dir]

Run any command with --help to see its available arguments and options:

boxr box lint --help
boxr box build --help
boxr box test --help
boxr box submit --help

For top-level CLI commands and environment variables, see CLI.

Validation

Validation checks both box.yaml and the files referenced by it.

Check	What it catches
Schema	Missing or unknown fields, invalid values, and malformed YAML.
References	Flags, hosts, networks, or entry points that reference objects that do not exist.
Flag values	Missing, malformed, or duplicate static flags.
Run type	Host layouts that do not match the declared `container`, `vm`, or `network` run type.
Build inputs	Missing or invalid source and image paths.
Network layout	Duplicate names, CIDRs or IP addresses, and host IPs outside their assigned network.
Required structure	Missing required files or directories, including `solver/`.
Identity	Duplicate `competitionId/id` pairs used by more than one box.

Local linting uses the same box rules checked by CI, so resolve any failures before submitting for review.

Review process

Access

Reviewers confirm that the private repository and any required image artifacts are accessible.

Build and start

The declared hosts are built or loaded, the environment starts, and its health checks are verified.

Verify the solve

Reviewers inspect or run the reference solver to confirm that the intended capture points can be reached and submitted.

Calibrate difficulty

The submitted category and difficulty are reviewed against the actual environment and solve path.

Accept the box

Once approved, that version is locked for use in Destrier. Further changes require a new version.

After acceptance

Accepted boxes may still receive feedback related to stability, fairness, or capture verification. Any changes made after acceptance should be submitted as a new version. If Destrier pays for the contribution, a confidentiality agreement may also be required. Do not disclose the box, solver, flags, write-up, or intended solution unless Destrier explicitly approves it.

Overview

Competing

Evaluation

Contributing

Before you submit

Submit your box

Validation

Review process

After acceptance

​Before you submit

​Submit your box

​Validation

​Review process

​After acceptance

Before you submit

Submit your box

Validation

Review process

After acceptance