The supply side
Powered by Fermah shows who buys proofs. This page shows who makes them. Prover nodes are the hardware half of the market, and their registration lives in public contracts rather than in a dashboard — so it can be read by anyone, including this page.
How the supply side works
Fermah is a market with machines on one side — GPUs and FPGAs run by operators — and anything that needs a ZK proof on the other. A Seeker submits a Proof Request, the Matchmaker assigns it to a Prover Node, and the node generates the proof. The whole ceiling of the system is coordination between those three, not raw compute.
An operator generates both key types. They identify the node to the network and sign its participation.
The operator set is permissioned: you request access before a node can register, which is why the registry is small and every entry is deliberate.
Registration goes through EigenLayer contracts for the Fermah AVS. That is what makes the operator set publicly readable — no permission needed to look.
Nodes ship an OpenTelemetry collector alongside the prover. Operators can point it at additional collectors of their own, which is how a node could feed a public board.
Summarised from docs.fermah.xyz. Follow the docs for the exact commands — Atlas does not mirror them, they change.
Registry
NOT YET INDEXED
Running a node?
Once the registry is indexed, every registered address appears here whether its operator asks or not — it is public on-chain data. What is not public is who is behind an address. If you want your node shown under your name, tell me and it gets a label.
A label is opt-in and reversible. Atlas never links an address to a person on its own — no heuristics, no name matching, no timing analysis.