Skip to main content

Solve Workflow

This page documents the practical workflow contestants use during a live event.

1. Open a Challenge and Start Runtime​

For deploy-required challenges, contestants click [+] Start Challenge from the challenge detail panel.

Challenge detail with start action

2. Wait for Deployment Readiness​

After start is requested, the challenge can enter a pending status while the platform prepares runtime.

Pending deployment state

When runtime is ready, contestants receive tokenized access data.

Running state with access token

An additional success popup can also present the token/result.

Challenge ready popup

3. Access the Challenge Instance​

HTTP protocol​

Contestants use the token shown in [YOUR ACCESS TOKEN] with this format:

http://<gateway-host>:<http-port>?fctftoken=<YOUR_TOKEN>

The challenge UI opens after gateway token validation.

Sample web challenge instance access

TCP protocol​

If a challenge is configured for TCP, contestants connect through the gateway and provide the issued token during session authentication:

nc <gateway-host> <tcp-port>

4. Submit Flag​

Contestants submit flags in the [SUBMIT FLAG] panel.

The platform handles common verdict states:

  • correct: score is awarded and challenge is marked solved
  • incorrect: attempts are consumed and optional cooldown is applied
  • already_solved: submission is acknowledged without duplicate scoring
  • ratelimited: temporary wait required before retry

5. Stop Runtime When Done​

If the challenge is deploy-required, contestants should stop runtime after completion or when switching tasks.

  • Use [-] Stop Challenge in challenge detail, or
  • Use [STOP] from the Instances page

This helps keep cluster resources available for all teams.

Runtime Start and Stop Flow​

Participant goal: Use challenge environment efficiently and safely.

Operational steps

  1. Start runtime from challenge detail page.
  2. Wait for readiness and connection details.
  3. Access challenge environment and perform solve tasks.
  4. Monitor runtime status while working.
  5. Stop runtime when switching tasks or after completion.
  6. Restart later if further analysis is required.

Expected result: Stable runtime usage with reduced resource waste.

Submission Pipeline and Result Handling​

Participant goal: Submit answers clearly and react correctly to verdicts.

Operational steps

  1. Validate answer format against instructions.
  2. Submit answer through official challenge interface.
  3. Review verdict (accepted, incorrect, already solved).
  4. Track score/rank impact after accepted submission.
  5. Reassess strategy before retrying incorrect attempts.

Expected result: Submission behavior stays fair and efficient.

Hint Economy and Unlock Rules​

Participant goal: Use hints strategically while controlling score trade-offs.

Operational steps

  1. Review available hints and costs.
  2. Check unlock prerequisites.
  3. Decide as a team before spending score.
  4. Unlock selected hint and apply guidance.
  5. Re-evaluate next move based on updated score context.

Expected result: Better solve progress with controlled deduction impact.