Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 1 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Develop the client and server components for the PQC-enabled handshake based on your design. Implement the PQC key generation, encapsulation/decapsulation, and digital signature verification using an appropriate PQC library (e.g., `oqs-python`). Ensure that both client and server mutually authenticate each other and establish a shared symmetric session key. Provide clear logging of the cryptographic steps.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Hold the task contract and output shape stable so generated implementations remain comparable.
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.
Develop a Post-Quantum Secure Data Link for Satellite Communications
The rapid advancement in quantum computing necessitates a proactive migration to Post-Quantum Cryptography (PQC) to secure critical infrastructure, especially long-lived assets like satellites. This challenge focuses on designing and implementing a secure, resilient data link using NIST-standardized PQC algorithms to protect communications between a simulated ground station and a satellite. Participants will explore practical aspects of PQC integration, hybrid cryptography, and performance considerations in a high-latency, potentially bandwidth-constrained environment. Participants will build a client-server application that simulates a satellite communication link. The core task involves establishing a secure channel using a hybrid approach, combining classical cryptographic primitives with PQC algorithms for key exchange and digital signatures. The emphasis is on practical implementation, security against quantum threats, and understanding the performance implications of PQC algorithms on real-world systems. An LLM agent will assist in threat modeling and scenario generation.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.