Is This Just Another Blockchain Identity Project? Partly Yes, and Here Is the Part That Is Not

The concession, first and in full

Yes, we run our own network, and the identifier resolves there. A sceptic who hears "identity project with its own chain" has correctly identified the pattern.

Yes, no resolver driver exists for our method, so third-party tooling resolves nothing.

And our own demand meter reads zero. We built an instrument that would register somebody needing this, and it has no rows.

That is the sceptic's case, made with our own numbers, and none of it is disputed.

What is different, with the command rather than the adjective

The passport standard is not ours. We anchor to registries defined and deployed by other people, and we did not write the specification. A project that invented both the standard and the chain it runs on has a different risk profile than one that did not.

The identifier method is registered in a public registry, and the entry is one request away:

curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713

returns a merged request titled "Register did:solidus method".

The credential format is published, so verification needs the issuer's key and none of our code.

The card is public, fetchable with no account at all.

And the packages install from the public registry into an empty directory, with no monorepo and no credentials, which is how the claims on these pages were checked rather than assumed.

What that difference does and does not buy

It buys falsifiability. Every sentence above can be checked by somebody who thinks we are lying, which is the only property that distinguishes a claim from a slogan.

It does not buy demand. Being checkable and being needed are different, and this estate has measured the second at zero.

The honest version of the pattern

Most projects in this category share three properties: a chain, a token story, and claims that cannot be checked from outside.

We have the first. The second belongs to a different surface and does not appear here. The third is the one we have deliberately attacked, which is what this entire estate is.

Two out of three is not a refutation of the objection. It is a smaller version of it, and a reader who discounts us on the remaining one is making a defensible judgement.

What is real, because absences alone would misdescribe us

A live passport in a registry we do not control, readable by anyone.

A method registration that merged, checkable in one request.

Published packages that install clean, and a card that needs no account.

And an estate that publishes its own defects, including a demand meter reading zero, which is the least flattering number this company holds.

What would actually settle it

1. A published external audit, which replaces our self-assessment with somebody else's.
2. A resolver driver, which makes the identifier usable by software that has never heard of us.
3. One unaffiliated relying party, which converts every thesis on this surface into a result.
4. A metered verification from outside, which is the same event seen from the other end.

None of the four is done, and the first two are entirely within our control, which is worth saying because it means the delay is ours rather than the market's.