---
title: Submit flags from a farm
description: Connect an automated exploit farm to the event's submission endpoint using your team's token.
---

Flags change every tick, so a working exploit is worth running against every team, every tick, for as long as the bug survives. Teams automate that with an exploit farm: a program that runs exploits, collects flags and submits them in bulk.

The submission endpoint speaks a line-based TCP protocol over TLS. Farms that support ForcAD's TCP submission, such as DestructiveFarm's `forcad_tcp` submitter, work with it unmodified once connected as below.

## Get your team token

Open **Downloads**. **Submission token** shows your team's token, the first line your farm sends on every connection. If it says there's no live token, ask the organizers to issue one.

Treat the token like a password: anyone holding it submits as your team. The whole team shares it, so it doesn't change when a player leaves; ask the organizers to rotate it if someone who knows it shouldn't. When a token your farm is using is revoked, the next flag it sends is answered `INV Invalid team token: revoked` and the connection closes. Put the new token from **Downloads** into your farm.

## Connect through a local TLS client

The endpoint accepts TLS only, on port 443 of the hostname **Downloads** shows. Most farms speak plain TCP, so run [stunnel](https://www.stunnel.org/) as a local client:

1. On **Downloads**, click **Download athena-submit.conf**.
2. Run it:

   ```bash
   stunnel ./athena-submit.conf
   ```

3. Point your farm at `127.0.0.1:31337`, with your token as its first line.

The config checks the endpoint's certificate chain and hostname. It reads trusted root certificates from `/etc/ssl/certs/ca-certificates.crt`, the system bundle on Debian and Ubuntu. On another system, change `CAfile` to your system's bundle. Never turn certificate or hostname checking off.

## Handle the replies

Every flag gets one reply line. A farm should drop a flag when the reply says it's accepted, already submitted, your own, expired or invalid (including a revoked token), and queue it again only when the reply ends in `try again later`. See [Submission protocol](/players/attack-defence/reference/submission-protocol) for every reply.

The endpoint limits how fast each team may submit. Over the limit, flags are refused with `try again later` and should be retried.

## Submit by hand

**Submit** on the event site sends one flag through the same endpoint with your team's token and gets the same reply a farm would. Use it to test a single flag.
