The lock is virtual; the calculation is real. Our ordinary computer runs a mathematical simulation of the quantum program. Please use a made-up test code: it is sent to our server for the calculation.
You supplied the test code. It defines the matching rule for our quantum program. Grover's algorithm then increases the probability of measuring the matching result. An unknown real PIN would first require a suitable checking rule; this learning lock is not a way to open real locks.
The lock has 1,000,000 valid codes, from 000000 to 999999. Twenty search qubits represent 1,048,576 bit strings; the remaining 48,576 are not valid codes. Our specialised C++ simulator computes all 1,048,576 possibilities using 804 Grover rounds, with no extra helper qubit. The most frequent measured valid code must satisfy the matching rule, or the lock stays closed.
The ideal success probability per measurement is about 99.99998%, not a guaranteed 100%. The full double-precision state vector occupies 16 MiB; the complete program requires additional memory. The calculation uses all ten cores of the i9 with AVX2 instructions. The result is bit for bit the same as with a single core.
More digits mainly mean more computing work: in each of the 804 rounds, the simulation recomputes all 1,048,576 possibilities. That takes about a tenth of a second. An ordinary program that checks the codes one after another against the same rule would finish sooner here. The simulation shows how the quantum program works. It is not a speed record and not a quantum advantage.
The wheels do not show quantum codes being tested one by one. Their fast movement fills the wait for results; slow motion then highlights the match. Both are visual design, not a measure of compute speed. With reduced motion, the result appears directly.
IBM's explanation of Grover's algorithm