Testnet, Not Mainnet: What's Actually Running Today
The title is the status, and keeping it accurate is this page's reason to exist: it is the canonical status statement for the whole network, kept current here so that every other page and post can link to it instead of restating it. If you read nothing else, that sentence is the state of Solidus.
What is live right now
Measured by probing every host, not asserted: the same check anyone can repeat with curl.
| Surface | What it is | Status |
|---|---|---|
| solidus.network | This site, the protocol's home | LIVE |
| identity.solidus.network | Personal identity wallet & credential manager | LIVE |
| auth.solidus.network | OIDC provider ("Login with Solidus") | LIVE |
| explorer.solidus.network | Chain explorer | LIVE |
| pod.solidus.network | Personal data store, Solid-compatible, not conformant | LIVE |
| docs.solidus.network | Developer documentation | LIVE |
| devnet-v2.solidus.network | v2 devnet | LIVE |
| verify.solidus.network | Reusable identity verification, issues portable W3C credentials | LIVE |
| wallet.solidus.network | Asset & credential wallet | BETA (labelled) |
| agents.solidus.network | AI-agent identity & passports | BETA (labelled) |
| relay.solidus.network | DIDComm relay | BETA (labelled) |
| node.solidus.network | Validator node portal | DEV ("coming soon") |
Two things this table deliberately does not count: the L1 chain itself and the nine published npm packages. They are the foundation everything above runs on, not separate products, counting them would pad the number, and padded numbers are how status pages rot. Eight more planned subdomains (dev, pay, bridge, gov, data, credentials, status, security) do not resolve today: planned, not built, and this page will say "live" only when they are.
Node sits at DEV because its own page still says "coming soon". These gradings are the surfaces' own words, not our re-grading, when a label changes on a page, it changes here.
Four validators, not twenty-one
The consensus design is specced for a 21-of-100 committee elected by verifiable random function. These are different things, a spec and a deployment, and this page exists partly so no other page ever blurs them. Operationally, four nodes means liveness depends on a committee the project itself runs: decentralization is a spec-stage claim here, not a live property. When a 21-validator network runs, this page will say so, with logs.
What "no mainnet, no token, no audit" concretely means
Anyone implying otherwise is not speaking for this project.
No audit. No third party has reviewed this code. The first targeted external audit, the BBS+ implementation, is aimed at H2 2026 via an NLnet NGI Zero application and has not started. SOC 2 / ISO-style certifications are 2027 roadmap.
No logos on this site, and we won't invent any.
Check it yourself
The table above came from probing each host, not from a roadmap document, and the probe is repeatable by anyone: every URL either answers or it doesn't. rpc.solidus.network is a live, publicly queryable JSON-RPC endpoint, resolving a DID against it takes one curl and no account. Every URL in the table above loads in a browser. And if you want the single strongest "this isn't vaporware" artifact the project has: clone the public protocol repo and run
cargo test -p solidus-exec --release --test twolane_vs_oracle randomized
, the differential-oracle test an anonymous stranger reproduced from a fresh clone on 2026-07-14: 1,344 transactions across 3 streams and 40 blocks, zero divergence. We would rather hand you that command than an adjective. And if it fails on your machine, that is a bug report we genuinely want, file it on the public repo.
For why so much of what runs here is other people's standards, and why that is the point, see /composition. For the fuller receipts, /press.
This page changes when the measurements change, and only then. If anything here disagrees with what a URL actually returns, the URL wins and this page is wrong, tell us.