Results from the Jane Street hardware puzzle
The puzzle presented a small chip's final GDS layout, requiring solvers to reverse-engineer the chip's functionality. Over 400 submissions came from more than 30 countries, including students, researchers, engineers, and retirees. Most solvers used tools like KLayout, Yosys, Z3, and custom tools implemented in various programming languages.
The chip's purpose was to function as a hardware checker for an 11x11 Star Battle puzzle, where the objective was to place exactly two stars in each row, column, and colored region without any two stars touching, even diagonally. The chip accepted 121 cycles of input to place stars, then performed several parallel checks to validate the solution.
Key checks included a 2-bit counter for each row and column, ensuring two stars per row/column, a 121-bit ROM mapping squares to regions, a 2-bit counter for each region, and a delay line tracking nearby squares to prevent diagonal adjacency. Additionally, there was a counter for the total number of stars to generate Easter egg outputs.
The puzzle was designed using the SKY130 open-source standard cell library and utilized the LibreLane toolchain. Solvers extracted a gate-level netlist from the GDS layout, either using existing tools or writing their own netlist extraction tools. Once the netlist was recovered, simulating the circuit required knowledge of each cell's behavior, which some solvers addressed by generating Verilog or building their own evaluators.
Instead of directly analyzing the circuit, several solvers opted to work backward from the "success" output to determine the conditions for a valid input. Others simulated the chip with different inputs, observing how intermediate signals changed, ultimately constructing a solution grid that met the required conditions for success.
Alternatively, some solvers employed SAT solvers, which were well-suited to this challenge as they could compute the necessary input to make a specific condition evaluate to true. This approach allowed solvers to find the correct solution without needing to understand the circuit's inner workings.
Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.