Credential Portability
Ayrıca şöyle anılır reusable KYC, portable credential, verify once reuse everywhere
Credential portability is the property that lets an identity check done once be reused somewhere else, without redoing it. Today, almost no identity verification works this way: run a KYC check for a bank, and a hotel, an airline, and a telecom operator each still make you start from zero, scan your ID again, take another selfie, wait for another review, even though the underlying question ("is this really you") hasn't changed. A portable credential is the fix: the first business that verifies you issues you something you keep, a digital credential, cryptographically signed. That the next business can check on its own, in seconds, without ever calling the first business.
For this to work and stay trustworthy, three things have to be true at once: the credential has to be verifiable (anyone can confirm it's genuine and hasn't been tampered with) without contacting the issuer every time; it has to be selectively disclosable (the holder shows only what's needed, proof of age, not a full birthdate) so reuse doesn't leak more than the original check did; and there has to be a way for the verifying party to know the issuer is trustworthy in the first place, or portability just becomes a way to launder a bad check into looking like a good one.
Who actually built this
The idea that a credential should be portable and independently verifiable is core to the W3C's Verifiable Credentials Data Model, developed by the W3C Credentials Community Group and Working Group over several years. "Reusable KYC" specifically has been tried by a series of earlier ventures, uPort, Civic, Sovrin, Evernym, ShoCard among them, most of which had more funding and more traction at this stage than Solidus does today, and most of which did not make it to broad adoption. That graveyard is real, and it's the honest context for any new attempt at the same idea, including this one.
Solidus today
Solidus Verify Capture, an embeddable identity-capture platform, live at capture.solidus.network, issues a portable credential and runs a real "issued at Business A, verified at Business B, no shared session" reuse flow end to end, backed by a live, publicly-queryable issuer trust registry and over a hundred automated tests. It is testnet, unaudited, and has no paying customer, stated here first, not buried.
See also
KYC is the check that gets made portable. Trust Registry is what lets a verifier decide whether to accept a reused credential's issuer at all. Level of Assurance is how strong that reused credential needs to be for a given purpose. Pairwise DID is a related privacy mechanism for repeat use at the same verifier.
Nereden geliyor
Bunu başkası belirtti. Solidus bir araya getiriyor.
Portability is a design goal baked into the W3C Verifiable Credentials Data Model itself. A credential is meant to be issued once, held by its subject, and verified by anyone without the issuer being contacted again. Applying that specifically to identity checks, "verify once, reuse everywhere", has been tried before, by a string of earlier projects including uPort, Civic, Sovrin, Evernym, and ShoCard, most of which did not survive to see it adopted at scale. Solidus is not the first to attempt this and says so plainly: the bet is that the standards underneath, did:solidus, registered in the W3C DID Method Registry; SD-JWT VC; BBS+ selective disclosure, are more mature now than they were for that earlier generation, not that the idea itself is new.
Bunu nasıl doğrularsınız
Test ağında çalışıyor. Ana ağda değil.
curl https://capture-api.solidus.network/registry/issuers/did:example:test returns a live "issuer not enrolled in this registry" rejection right now. The accountability backstop that makes reuse trustworthy is a running service, not a mockup. The consumer-facing front door of the same pipeline is npm i @solidus-network/capture, with a live browser demo at https://capture.solidus.network/demo/.