Verification Reuse
Ayrıca şöyle anılır check reuse, KYC reuse, identity-check reuse
Verification reuse is the practice of accepting a previously completed identity check instead of running a new one, the second business in the chain trusts the first business's work (or, more precisely, trusts the credential the first check produced) rather than starting from a blank document scan.
It's a narrower, more specific idea than the product Credential Portability describes: portability is the property that makes reuse possible (a credential that's verifiable and disclosable enough to hand to a second party); reuse is the actual event of a second party accepting it instead of re-checking. A system can have a perfectly portable credential and zero reuse, if no second party is willing to trust it, which, honestly, is close to where every attempt at this idea, Solidus included, sits today.
The two things that have to both be true
For reuse to happen at all, two separate conditions have to hold simultaneously: the credential has to be genuine and unaltered (solved by cryptographic signing (the easy part, decades of prior art), and the verifier has to have a reason to trust the issuer it didn't come from) which is a business and regulatory question, not a cryptography one, and the one that actually determines whether reuse happens. A trust registry (see that entry) is the piece of infrastructure that tries to answer the second question at all, rather than leaving it as "trust us."
Solidus today
Solidus's testnet runs the mechanical side of this end to end: an issued credential, a holder who can present it, and a public trust-registry lookup any verifier, or any stranger with a terminal, can query to check whether the issuer is accredited before accepting its credential. That's real, running, checkable code. What hasn't happened is an actual reuse event between two real, unaffiliated businesses with money on the table. Solidus has no paying customer, and the launch sequence deliberately targets lower-regulation verticals first (hotel check-in, age-gated purchases, SIM registration), places where a business can accept reuse on its own commercial judgment, rather than banking, where it couldn't, precisely because that trust question is unsolved at higher stakes.
See also
Credential Portability is the property that makes reuse possible. Credential Reuse Rate is how you'd measure whether it's actually happening. Trust Registry is the mechanism a verifier uses to decide whether to reuse at all.
Nereden geliyor
Bunu başkası belirtti. Solidus bir araya getiriyor.
The idea of not re-running a check that already happened is common to any federated-identity or portable-credential design, not a Solidus concept: SAML and OpenID Connect single sign-on reuse an authentication event across relying parties; the W3C Verifiable Credentials Data Model generalizes the same idea to reusable, independently verifiable claims (see Verifiable Credential). Applying it specifically to KYC/identity-proofing checks, not just login sessions, has been attempted by a string of earlier ventures (uPort, Civic, Sovrin, Evernym, ShoCard), documented under Credential Portability. Solidus composes an existing pattern; it is not the first identity system built around reuse.
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:solidus:testnet:1111111111111111111111zz returns a live HTTP 404 "issuer not enrolled in this registry" rejection right now. The accountability mechanism that would need to exist for reuse to be trustworthy is a running service, not a slide. There is no equivalent proof of an actual cross-business reuse event with a real customer, because none has happened yet.