Scope
The project coordinates research on the established Bitcoin Puzzle series, where constrained key ranges and funded addresses were published as a challenge. Participants must not repurpose the client, engines or server protocol to search unrelated wallet keys, test stolen data or access funds they are not authorized to control.
No promise of discovery
Brute-force key search is probabilistic and the remaining spaces are vast. Hardware estimates, network speed and completion percentages are descriptive measurements. They are not financial projections and must not be presented as a likely return on electricity or equipment costs.
Protect local solution material
A potential private key is equivalent to control over the corresponding funds. Keep the solution computer offline when practical, do not paste the key into websites or chat services, and verify any transaction workflow on a trusted system. OpenPuzzle's visible notice contains a path to the protected local export but deliberately avoids printing the key itself.
Operational responsibility
Participants are responsible for cooling, power limits, drivers and local hardware safety. Sustained GPU workloads can draw substantial power. Stop and investigate unusual temperatures, instability or driver resets. The automatic benchmark is a compatibility aid, not a guarantee that every overclock or undervolt is stable.
Data accuracy
Public statistics depend on client heartbeats, leases and database state. Temporary differences between “active clients” and “clients online” can occur because those values use different time windows. A range is treated as research evidence only after the completion checks pass.
Independent verification
OpenPuzzle does not automatically declare a puzzle solved. Any potential discovery requires independent address derivation and blockchain verification. Public status changes should follow verifiable evidence, not an engine message alone.