9
Views
academic · 2025
Chain cipher steps into a pipeline, encrypt or decrypt text, and review every intermediate stage. A cryptography course project built as a real application.
9
Views
5.4k
Frontend code
lines, TypeScript
Academic
Context
cryptography coursework
The problem
A cryptography syllabus covers a dozen classical and modern ciphers, and understanding them means seeing what each transformation does to the text. Running lab scripts one at a time shows the output but not the composition.
The approach
Built it as a service rather than a set of scripts: a user assembles an ordered pipeline where each cipher carries its own parameter shape, runs it, and sees every intermediate step. Decryption replays a known chain in reverse, which is deliberately a separate flow from encryption because the step order has to invert. The frontend is typed end to end, with the API layer and the pipeline data structure carrying real types, since a wrong field name in a cipher parameter is otherwise silent.
Architecture
Cipher implementations use the standard library rather than third-party crypto packages, since the point is the algorithm rather than the dependency. The pipeline is an ordered list of typed steps, replayed in reverse for decryption.
Each with what it cost
A decision without a stated tradeoff is a preference.
01
Why
They are different tasks: encryption composes a new chain, decryption replays a known one in reverse. One form with a switch hides that the step order must invert.
What it costs
Two views instead of one, in exchange for the inversion being explicit rather than a hidden branch.
Outcome
A working cipher-as-a-service platform with a browsable algorithm catalogue, a per-user key vault, and full pipeline history. Presented as coursework.