Install
Install the command-line tool
One command, guldo, lets you try a solver on your own computer, submit it to a round, and check any certificate yourself. No account, no browser.
Three steps
1
Download
guldo-0.1.0.zip (333 KB). To check what you got, compare its SHA-256 with this one:
4a86d24e286cccba1f14f602f9f6ff7a44e6eedbb9baef4c80bcb1400025f942
shasum -a 256 guldo-0.1.0.zipOn Linux the command is sha256sum.
2
Install
The easy way is pipx, which keeps the tool in its own private folder:
pipx install ./guldo-0.1.0.zipOr use a virtual environment:
python3 -m venv ~/.guldo-venv && ~/.guldo-venv/bin/pip install ./guldo-0.1.0.zip3
Check it works
You should see a version number and a list of the other tools:
guldo --versionguldo toolsWith a virtual environment, run ~/.guldo-venv/bin/guldo instead.
What you need
- A Mac or a Linux computer. Windows is not supported.
- Python 3.9 or newer. Exact step counting needs Python 3.12 or newer.
- The numerical library numpy, which is installed for you.
- Optional: pip install "./guldo-0.1.0.zip[attest]" in a virtual environment adds signed attestations; [lattice] adds the library the lattice problems use.
Try it
- Check a solver before you submit: guldo lint my_solver.py --family factor
- See what a practice run on three secret numbers of your own would cost: guldo practice my_solver.py --family factor --count --dims 38 40 42. It only prints the plan; add --yes to run it, which can take hours.
- Check a certificate someone gave you: guldo verify their.cert.json
- Work out a benchmark score from it: guldo claims correctness their.cert.json
- See a round and submit: guldo rounds --server URL
Good to know
- Checking is safe, re-running is not. guldo verify FILE never runs any code from the certificate. Adding --rerun all --execute re-runs the solvers inside it on your machine, with no protection: do that only on a throwaway computer or virtual machine.
- Your receipts and tokens are kept in ~/.svp, readable only by you. A submission token is shown once; keep it.
- Some commands write under the tool's own folder, which is why pipx or a virtual environment is the right way to install it. A problem you compile yourself is saved there too, and an upgrade would replace it: keep your own problem declarations in a copy of the repository.
- To update, install the newer file over the old one: pipx install --force ./new-file.zip. To remove it: pipx uninstall guldo.
- Prefer to build it yourself? In a checkout of the repository, make package creates the same folder, and the hash of this download changes with every build of this site, so always compare against the hash shown above.
What each result does and does not prove is on the Limits page, and the plain-words list of extra claims is on Other claims.