Why Solidus Prioritizes Standards Bodies Over Press
Solidus has sent zero press pitches. There is no media list, no embargo calendar, no briefing deck sitting in a drafts folder: the receipts page that would carry a press hit instead carries a merged pull request and a membership listing, because those are what exists. That is also this page's honest admission up front: the strategy below is cheap and it compounds, but it is slow. Nothing here changes that; this page explains a sequencing choice, not a launch.
What a press hit buys, and what it doesn't
A press mention is fast and it is borrowed. A reporter's credibility stands in for the claim until a reader checks it themselves, which, for most readers, is never. That trade works well for products a buyer can try in five minutes. It works badly for a protocol whose entire pitch is don't trust us, check us (see /press): a headline saying "Solidus registered a DID method" is not more true than the pull request itself, and it adds a layer of trust, trust the reporter did the checking, that the underlying claim doesn't need.
A standards-body action is slow and it is owned. Nobody has to believe Solidus's account of it; the record sits on someone else's site, dated, and any reader can pull it up cold. That is a worse trade for velocity and a better trade for a diligence reader, a grant reviewer, a technical investor, a fellow implementer, who is going to verify anyway and would rather not start from a press release.
Two zero-cost wins, both real and both dated
Two actions cost nothing but time and both have already happened:
did:solidus is registered in the W3C DID Method Registry. Not "a W3C standard" and not "W3C-approved": a registry listing, which is what it is and what the page says. The record is pull request #713 to w3c/did-extensions, state closed, merged, on 2026-07-04. Anyone can pull the merge status from GitHub's API without asking Solidus anything.
Solidus is a DIF Associate Member. The Decentralized Identity Foundation stewards DIDComm, Presentation Exchange, and Sidetree, the working groups where the field's actual interoperability gets negotiated. The Solidus logo and a link sit on the identity.foundation homepage today; membership is a line of participation in that body's work, not an endorsement of Solidus's own claims, and the page treats it as exactly that, participation, not validation.
Both of these were available at close to zero marginal cost: a membership form and a specification write-up, not a fundraising round or a hiring decision. The reason they had not already happened by the time this strategy was written down was sequencing, not difficulty, which is itself worth stating plainly rather than dressing up as foresight.
One line item still in the queue, named as what it is
A third standards-body action sits in the application queue rather than the receipts column: OpenWallet Foundation associate membership, a modest paid tier under the Linux Foundation umbrella that would let Solidus draw on reference implementations for wallet-side credential protocols. It is not yet held. It appears here, in the queue, rather than on /press among the things that are checkable today: the distinction this page insists on is exactly the one between an action taken and an action planned, and blurring it for one line item would undercut every other claim on this page.
The same discipline applies to the wider non-dilutive funding queue this strategy sits inside, NLnet, the Ethereum Foundation's ESP, Web3 Foundation grants, and similar programs are applications in progress, not funding received. None of them is a credibility receipt yet; they become one only on the day an award letter, not a submission, exists.
The tradeoff, stated plainly
This is a slower path than a launch story. A registry listing and a membership badge do not trend, do not generate inbound, and do not compress into a soundbite the way a funding announcement or a partnership headline would. What they do is accumulate: each one is a fact a skeptical reader can verify without asking Solidus to vouch for itself, and each verification a reader does themselves is worth more, to the kind of reader this project needs first, than a hundred readers who took a journalist's word for it. The same logic is why the claims that didn't hold up get walked back publicly rather than quietly dropped: a standards receipt is only as good as the discipline that keeps every other page honest about the gap between what's shipped and what's aspirational.