Demo
Your code really runs in the sandbox and the verdict is real. Nothing is locked, and solving this cannot unlock anything.
Get the real thing →Try it
Arm a timer. See what happens when it fires.
On a real install this would be twenty-five minutes and it would take your whole screen. Here it is eight seconds and it takes this page — enough to show you the shape of the thing.
The problem you get is deliberately winnable the wrong way: the obvious nested loop is correct, passes every test, and will not clear the gate.
- Runs your code
- In the same throwaway container: no network, dropped capabilities, read-only filesystem.
- Times it honestly
- Measured inside the container, worst case across the suite, not around the call.
- Unlocks nothing
- There is no session and no token. The response has nowhere to put one.