What's Actually Running in Solidus Node Today (and What Isn't)

Five things are true about Solidus Node right now, and they are not all true in the same way. Read this page first; every other page on this surface points back to it instead of re-arguing its own honesty.

The ledger

#	Claim	Proof	Caveat
1	`solidus-node` v0.1.0 is a real, signed, checksum-verified release	see block below	Signature-verified ≠ confirmed-syncing (row 2)
3	A CUDA/GPU build shipped and was published (2026-07-15)	`node.solidus.network/gpu`, manifest `variant` field	Zero throughput or cost-per-job ever measured
4	An operator/staking dashboard exists	compiles in the repo	Not deployed to this domain: nothing in it describes anything real
5	A validator committee is running	`architecture-system.md`	4 nodes today, against a `protocol.md` §7 spec of 21-of-up-to-100 VRF-selected

Row 1's proof, exactly as run:

curl -sI https://releases.solidus.network/install.sh          # 200, 7,323 B
curl -s  https://releases.solidus.network/stable/latest.json  # 200, Ed25519-signed, rollout_percent: 100
# binary download (27,933,008 B, ELF x86-64) → SHA256 0012f106…8630e
# matches the signed manifest exactly; release pubkey 4554f96c…

That is a real chain: the install script serves, the manifest is signed and at full rollout, and the downloaded binary's hash matches the manifest byte for byte. The fail-closed verification path genuinely works end to end.

Why two of these look the same and aren't

Passing that signature chain proves one thing precisely: the binary a fresh install pulls down is the binary Solidus published, unmodified, with a valid signature. It does not prove that binary still talks to the chain. No command currently confirms this, that's the open question, not a hidden one. It is a version-skew question, not a signature question, and it stays open until someone runs that clean-box test and publishes the result. Until then, this page does not carry a curl | sh install-and-sync demo, because that would present two separate claims, "the binary is authentic" and "the binary syncs", as one proven fact, and only the first one is proven.

The GPU row carries a related but different gap. The onnx-cuda build ships and is published, and the manifest's variant field plus a loud CPU-execution-provider warning in the installer make it structurally impossible for a CPU build to silently present as a GPU one. That is a real design property. What it is not: a performance claim. No throughput number, no cost-per-job figure, and no latency figure has ever been measured for either the CPU or the CUDA path. Verifiable off-chain compute, with GPU as one optional tier, never "a GPU network," and never a number that doesn't exist.

What "not deployed" means for the dashboard

A Next.js operator dashboard, validator health scores, tiered comparisons, a staking calculator, compiles in the codebase. It is not deployed to node.solidus.network. Nothing on this page, or any page on this surface, describes any of its screens as available today; "compiles, not deployed" is the only accurate phrasing for it, every time it comes up. That includes any reward number the prototype shows. No tradeable token exists to distribute, price, or stake, so a staking calculator or an APY tier in that prototype does not describe anything real: it describes Figma-Make copy waiting on a token that has not been designed yet.

The committee number, stated once at full precision

Solidus's Proof-of-Identity design specs a 21-of-up-to-100 VRF-selected validator committee, that's protocol.md §7, and it's a design target, not a status report. What is actually running, verifiable against architecture-system.md, is a 4-node dev committee. Both numbers belong in the same breath every time this comes up, on this page and every other: the spec describes where the network is going, the 4-node figure describes what's live right now, and blurring the two would misstate the current state of the network far more than any single omitted number would.

What this means for different readers

If you operate infrastructure and are asking whether there's a product here to add to what you run today: there isn't yet.

Where to go next

For the step-by-step version of the install chain above, GPG, SHA256, the exact commands, run by you rather than described here, see running-a-node-honestly. For the consensus-math version of "check this yourself," including the bounded model check and the stranger's independent reproduction, see reproducible-consensus. For what a validator actually is before any of this ledger means anything to you, see what-is-a-validator, installing this binary is not the same as becoming one; that requires staking and DID registration, neither of which exists without a token to stake.