How PubPhys works
PubPhys is an open database of unsolved problems in physics. It currently holds the seed collection: 1,762 problems under 360 topics in 18 fields, and the problems people have added since. Reading is open to everyone; any account with a linked ORCID iD can submit new problems. Any account with a linked ORCID iD can propose a topic. The field's editors decide on both by signed, public decisions: editors, referees and their decisions. Authors revise their problems by signing new revisions. What you type in these forms is kept as a private draft until you sign it. Results on problems (progress, solutions, disproofs) are signed by their authors and checked by editors and referees: posting a result and the process, stage by stage. Any account with a linked ORCID iD can contest a result or a decision on it: contests; the party a decision went against may appeal it once. Public problems and results take comments, and you can follow a problem to be notified of what happens on it; topics, fields and people can be followed, and problems saved. Lists are ordered by points: how ranking works. What changed on the site, and when: changes. Your account: registering, signing in, what each account may do, addresses, suspension and deletion, and the browsers it works in; the limits on what one account can do; the privacy notice and the terms of use.
Fields, topics and problems
- Field: a part of physics, such as condensed matter or cosmology.
- Topic: a big open question, often loosely posed, such as the pairing mechanism in the cuprates. Each topic carries one review paper whose reference has been checked.
- Problem: a precise question under a topic. It has a statement in plain words, a precise statement for specialists, what would settle it, the kind of question and of answer, and its status in the published literature.
Expert and Non-expert
Two buttons in the header, Expert and Non-expert (the first entry of Menu on a narrow screen), choose how the site reads. Expert, the default, shows a problem's precise statement and what would settle it, and in lists the precise statement under each title, cut to four lines. Non-expert shows the statement in plain words instead, on the problem page and in every list. A topic page leaves out "Why it matters" in Expert mode. Titles are the same in both modes. The choice is kept in a cookie in your browser, not with your account (privacy notice). A link above a problem's statement opens that one page in its other version and changes nothing else. The JSON API and the MCP tools have no mode: they return every text of a problem.
Figures
Some of the first hundred problems have one figure: across the top of the problem's card on the home page, as a small picture in the list of problems, and above the statement on its page. A figure is either a schematic drawn by AI agents in LaTeX, captioned "Schematic drawn with AI for PubPhys" on the problem page, or an illustration made with an image-generation model, labelled "AI-generated illustration" wherever it appears. The illustrations are not photographs of a real instrument, place or object, and neither kind is a plot of real data. No physicist has checked the figures yet. Each figure is editorial: it is not part of the signed statement or of any record, and it can be replaced or removed without a new revision. The JSON API and the MCP tools do not return figures. No outside image is used (image credits).
Status in the literature
Each problem is marked open, contested or partially resolved according to the published literature. This is editorial information about the state of research, not a verdict by PubPhys. A short note describes the latest state; notes that mention work from 2024 on were partly written without a live literature search and are marked unverified until an editor checks them.
Revisions and records
Every problem has numbered revisions; nothing is overwritten. The seed collection is revision 1, accepted at import, and its import manifest is timestamped in Bitcoin. Every revision is a signed record in the public log (see Proofs below).
Proofs
Every topic and problem is a signed record in a public log, dated by Bitcoin, so anyone can check what was submitted and when without trusting PubPhys: how this works, the protocol and the keys.
A member saves the proof of each result, new problem and signed change to a problem, and checks it without this site: keep your own proof.
For AI agents and programs
The database can be read through a read-only JSON API and over the Model Context Protocol. The API is read-only. Over MCP, an AI agent holding a member's agent key can also prepare private drafts for that member; the member signs them on the site, and nothing is published without that. How PubPhys itself uses AI: AI at PubPhys.
During maintenance
While PubPhys is being updated, reading, search, the API and checking proofs work as usual, and you can sign in and out. Every other form answers that changes are paused for a short while: what you sent is not saved, so keep your text and send it again later. A record you prepared for signing is kept for 1 hour as usual, so you can sign it once the pause is over.