Description
CoreWars is back, and this time you must intentionally lose every battle against the Imp. Submit a warrior that self-terminates immediately.
Setup
Edit the provided Redcode warrior so it contains nothing but a header and ends immediately.
Pipe the modified warrior into nc saturn.picoctf.net 62089 to fight the Imp.
printf ';redcode\nDAT 0, 1\nend\n' > imp.rednc saturn.picoctf.net 62089 < imp.redSolution
Walk me through it- Step 1Strip the warriorA warrior that only contains a DAT instruction dies the moment it executes it. DAT is the data instruction and any process that attempts to execute it is immediately terminated. One DAT line is enough to lose every round.
Learn more
Core War is a programming game from 1984 (A.K. Dewdney) where two programs called warriors compete inside a virtual machine called the MARS (Memory Array Redcode Simulator). Warriors are written in Redcode, an assembly-like language: a few opcodes, addressing modes, and a circular memory of typically 8000 cells. The MARS interleaves instructions from each warrior. A warrior dies when it executes a
DATinstruction; the last live warrior wins.The Imp is the simplest possible warrior:
MOV 0, 1copies the current instruction one cell forward, and execution follows it. The result is a self-replicating wave that sweeps memory forever.A warrior whose source is just
;redcodeplusendloads with zero executable instructions, so the very first scheduled tick lands onDATand dies. Across all 100 rounds the result is deterministic: 0 wins, 100 losses. With a normal scoring tiebreaker (more wins beats more ties beats more losses), this hits the requirement of losing every round.Want to test locally first?
sudo apt install pmarsinstalls pMARS, the standard MARS simulator. Runpmars -r 100 -b imp.red imp.redand confirm the empty warrior loses 100/100 before connecting. The pMARS reference covers the CLI in detail. - Step 2Run the matches over netcatSend the file through nc and read the summary. The flag prints once 100 rounds finish.bash
timeout 30 nc saturn.picoctf.net 62089 < imp.redLearn more
The challenge server runs the matches synchronously, so the response is just stdin in, summary out. Wrap nc in
timeout 30if the connection seems to hang; that catches the case where the warrior is malformed and the server waits for more bytes. If the response complains about syntax, double-check the file has Unix line endings (runfile imp.red; CRLF endings break some pMARS variants).For deeper Core War strategy the corewar.co.uk archive has decades of documented warriors and tournament results.
Flag
picoCTF{h3r0_...6d4cf}
Any warrior that terminates immediately will forfeit every round and yield the flag.