Built, Not Pitched: The Receipts

If a claim cannot carry one, it does not appear here. That is the page's whole contract: it exists so that a reporter, a researcher, or a diligence reader can verify Solidus without believing anyone, including us.

The canonical, always-current version of that sentence lives at /status; this page does not re-derive it.

The standards receipts

did:solidus is registered in the W3C DID Method Registry. Not "a W3C standard," not "W3C-approved": a registry listing, which is exactly what it is. Check it:

curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 | jq '{title,state,merged}'

Pull request #713, "Register did:solidus method," state closed, merged: true, merged 2026-07-04. The method behind the listing resolves live: see did:solidus.

Solidus is a DIF Associate Member. The Decentralized Identity Foundation stewards DIDComm, Presentation Exchange, and Sidetree. The Solidus logo and link are on the identity.foundation homepage, membership is participation in the body's work, not an endorsement of ours.

The engineering receipts

Nine published npm packages. The org page is browsable at npmjs.com/org/solidus-network, and any package is checkable from a terminal:

npm view @solidus-network/sdk version     # 0.6.3
npm view @solidus-network/bbs version     # 0.6.3

The protocol-side line is sdk, auth, bbs, and types at 0.6.3, plus the agent-identity family at 0.1.4; the org page carries the full list with each package's own README.

A benchmark you can rerun, with its raw logs published. 75.6K TPS on the payment lane, 17.7K ops/s on the identity lane, 64.9K TPS on a 95/5 mix, measured on a single Apple M4, ten cores, one machine. No geo-distributed number exists, and any comparison to a global payment network would be meaningless; the raw logs are in the public repo at docs/bench/2026-07-13-apple-m4/. The stronger artifact is the correctness harness: a differential oracle that replayed 2,186,046 transactions across 1,000 streams and 100 blocks with zero divergence, and which an anonymous stranger reproduced from a fresh clone on 2026-07-14 (1,344 transactions, 3 streams, 40 blocks, test result: ok):

cargo test -p solidus-exec --release --test twolane_vs_oracle randomized

A bounded model check, not a proof. The consensus spec was checked with TLA+/TLC: 963,033 states exhaustively at MaxView=2, zero safety violations. Spec and results are in the repo under tla+/TLC_RESULTS.md. We call this a bounded model check because that is what it is.

The bug we found in our own cryptography

In the v1 format of our credential header, a field called verification_id was, by our own later analysis, a correlation handle as strong as a DID: a stable identifier that could link a user's presentations across verifiers, in a system whose entire point is preventing exactly that. We published the defect and shipped v2, which demotes it to an always-hidden message, because a privacy system whose failures are secret is not a privacy system. That the v2 behavior is as claimed is itself checkable: the unlinkability demo ships inside the published tarball and prints its own honesty boundary when it runs.

npm i @solidus-network/auth @solidus-network/bbs
node node_modules/@solidus-network/auth/demo/unlinkability-demo.mjs

Facts for accurate reporting

  • Founded: January 2025
  • Founding team: three
  • Validators: 4 (a development committee run by the project; the 21-of-100 VRF committee is a spec, not the deployment)
  • Live surfaces: the measured list is at /status. No count is printed here, because a count copied into prose is wrong the week a surface moves.
  • Token: none exists. There is no supply figure, no price, and no ticker to print: a number presented as any of those is wrong.
  • Whitepaper and brand assets: available from this page's download blocks

Zero pitches sent

As of this page's last update, Solidus has sent zero press pitches. This page is not evidence of coverage: it is the pre-built asset that makes future fact-checking cheap. When a claim here and reality disagree, reality wins and the page gets fixed; if you catch such a disagreement, that is exactly the kind of message we answer fastest.

Press contact: [email protected], media inquiries, interview requests, and fact-checking.

For why almost everything above is built from other people's open standards, and why that is the strategy, see /composition. For the term-by-term version with a proof per entry, the Lexicon.

The audit status of this implementation

The unlinkability implementation described here is unaudited.

Keep reading

Built, Not Pitched: The Receipts · Solidus