Support

Who is supporting this project, and how to help

Steering

• Manuel Barbosa — University of Porto
• Pooya Farshim — Input Output / Durham University
• Denis Firsov — Input Output / Tallinn University of Technology
• Jens Groth
• Mohammad Mahmoody — Bilkent University
• Christian Rechberger — TU Graz
• Stefano Tessaro — University of Washington

Listed alphabetically; each name links to that person’s own page. Support means backing the project and its aims; it is not an endorsement of any particular statement on the site, and it is not a review of one. Reviews are recorded where they belong — in the provenance badge on each statement’s own page, which moves off AI-written, unreviewed only when someone has actually read that statement.

The project is looking for more steering members — in cryptography, in formal methods and DevOps, and anyone who can bring tokens.

Anyone listed here can ask to be removed at any time, without giving a reason.

The project is currently maintained by Pooya Farshim.

Supporting the project

The project’s stated aim is that the cost of attacking a problem should come down to compute anyone can bring, rather than to whose budget is larger — the argument is on the Philosophy page. Six things help, in rough order of how scarce they are:

1. Reviewing. The scarcest. Most statements on this site have never been read by a person, and the ones that have are the only ones anyone should cite. Reading a single statement carefully is a real contribution and is recorded as one.
2. Conjecture formulation and resolutions. Open questions from your own work, stated precisely enough to be attacked or refuted — and proofs or refutations of what is already here. How to propose one.
3. Formalizations. Statements and proofs, machine-checked. A formalized statement pins down what was actually claimed; a formalized proof settles whether it holds. Both are tracked per statement, and both are usually the longest part of the work.
4. Website and workflow maintenance and upgrades. The site, its build, and the scripts and prompts behind it. Everything is in the repository, and the tooling gets more use than the pages do.
5. Contributing tokens. Pooled capacity, and bounties payable on a verified resolution rather than on a committee’s schedule. This is the form of help that most directly buys attempts at open problems.
6. Ideas! How the archive should be organized, what a statement’s page owes a reader, which conventions are wrong. Open an issue and say so.

To be listed, or to correct how you are listed, open an issue or a pull request on the repository.