CTF-403: Scoreboard Freeze¶
Statement¶
The system could support freezing the public scoreboard at a configurable time before event end. After freeze, participants continue to see their own updated score but the public scoreboard displays frozen standings. Organizers shall see the real-time scoreboard regardless of freeze state. The freeze shall be lifted when the event ends or when an organizer manually unfreezes.
Rationale¶
Scoreboard freeze is a standard CTF practice that maintains suspense in the final hours, participants know their own progress but cannot see if competitors are catching up. Without freeze, the final stretch loses its excitement as outcomes become obvious before the event ends. (CTFd supports scoreboard freeze.)
Traceability¶
- IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/models/event.py(CTFEvent.scoreboard_freeze_at) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/services/scoring/(Scoring service - get_scoreboard recomputes the board as of the freeze cutoff (freeze_at)) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/services/event/(Event service - scoreboard_freeze_at in mutable fields) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/forms/(CTFEventForm - scoreboard_freeze_at field) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/ctf/migrations/0019_add_scoreboard_freeze.py(Migration adding scoreboard_freeze_at to CTFEvent) - TESTS → TEST
shifter/shifter_platform/tests/ctf/test_scoring.py(Scoring tests - TestScoreboardFreeze and TestIsScoreboardFrozen) - IMPLEMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#574(CTF-403: Scoreboard Freeze)