Verification reuse. The plumbing runs, and the plumbing was never the hard part

The mechanism is real, and you can check part of it yourself in one command. And reuse has never happened with a real, unaffiliated second business, which is what this page is about.

What reuse is, mechanically

A person is verified once. They keep a credential. When a second business needs the same fact established, it does not re-run a capture pipeline, it checks a signature and checks the issuer.

That second check is the whole idea, and it has two halves:

1. Is this credential authentic and unexpired? Ordinary public-key verification.
2. Do I have any reason to trust who issued it? This is the half that distinguishes reuse from "trust me": a relying party queries a trust registry for the issuer, rather than accepting an unverified assertion.

The proof you can run

The accountability half is a live service, not a diagram:

$ curl -s https://capture-api.solidus.network/registry/issuers/did:solidus:testnet:1111111111111111111111zz
{"statusCode":404,"error":"Not Found","message":"issuer not enrolled in this registry"}

HTTP 404, returned live on 2026-07-31. An issuer that is not enrolled is rejected, by a publicly queryable endpoint, right now.

That is what makes reliance a checkable position rather than a leap of faith: a verifier can establish that an issuer is known before acting on anything it signed. It is a small thing to be able to demonstrate, and most of what vendors claim in this space cannot be demonstrated at all.

What that command does not prove

It proves the registry rejects an unknown issuer. It does not prove anyone uses it.

The hard problem in verification reuse is not cryptography: it is a second company choosing to trust a check it did not run. That is a commercial, legal and risk decision, made one company at a time, and no amount of working code moves it.

So this page describes working plumbing attached to a network that has one participant.

Three more bounds, none of them small

• There is one credential type. The issuer advertises a single credential configuration today. A reuse ecosystem needs more than one shape of claim.
• The registry is ours. It is a single Solidus-operated list, not a federation of independently operated ones. What that costs you is the subject of vendor lock-in, and it is a real cost.
• Reuse does not discharge the second business's obligation. Whether a supervisor accepts third-party verification as satisfying a duty is unsettled, and a cheaper mechanism does not make it settled.

How this relates to the pages either side of it

• This page is the plumbing, what happens on the wire.
• Reliance is the decision, whether anyone chooses to act on it. Zero so far.
• Re-verification cost is the price, and every figure in it is provisional.

All three have to be true at once for the argument to work. Today the first one is.