SSI (Self-Sovereign Identity)
Ayrıca şöyle anılır Self-Sovereign Identity, SSI, merkeziyetsiz kimlik, dijital kimlik
Self-Sovereign Identity is an approach to digital identity where the person the identity belongs to holds and controls it directly, in a wallet or app they own, instead of a company or government holding a record about them and deciding when to share it. Under SSI, an identity credential (a driver's license, a proof of age, a completed background check) is issued once, stored by its owner, and shown to whoever needs it, on the owner's terms, without the issuer being contacted again or even knowing where it gets used.
This is a reversal of how almost every login and verification works today. Log into a bank, an airline, or a government portal and, underneath, some central database is consulted every time, you don't hold anything, you just prove you're allowed to ask. SSI's bet is that the holder-controlled version is both more private (no central party sees every place you use your identity) and more resilient (no single database breach exposes everyone at once).
Who actually built this
The name and the ten founding principles come from Christopher Allen's 2016 essay. The
first real infrastructure came from the Sovrin Foundation and the Hyperledger Indy/Aries
projects, which built a purpose-made ledger and agent protocols for exactly this pattern
starting around 2017. The Decentralized Identity Foundation (DIF) and the W3C's
Credentials Community Group generalized the same ideas into vendor-neutral standards,
Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs), that don't require
Sovrin's specific ledger at all. Solidus builds on that second, more general layer: its own
chain anchors did:solidus identifiers, but the credential format and the holder-control
model are the DID/VC community's design, not Solidus's.
Solidus today
Solidus's live products (Solidus Verify, Solidus Identity, Solidus Pod) each implement a piece of the SSI pattern: the user holds a wallet, credentials carry selective disclosure, and a completed check becomes something the holder keeps, not just a row in Solidus's own database. All of it runs on Solidus's public testnet today: no mainnet, no token, and no external audit of the cryptography involved. And the honest caveat above stands, full SSI purism would also require a trust layer with no single controlling party, which Solidus does not yet have.
See also
KYC is one concrete thing an SSI-style credential gets used for. Credential Portability is the specific SSI property (portability) Solidus leans on hardest. Pairwise DID and Trust Registry are two of the mechanisms that make or complicate the "self-sovereign" claim in practice.
Nereden geliyor
Bunu başkası belirtti. Solidus bir araya getiriyor.
Coined and popularized by Christopher Allen's 2016 essay "The Path to Self-Sovereign Identity," which distilled ten principles, existence, control, access, transparency, persistence, portability, interoperability, consent, minimalization, protection, into a name the field still uses. The Sovrin Foundation, Hyperledger Indy/Aries, and the Decentralized Identity Foundation (DIF) turned the essay into running ledgers, agents, and specs over the following years. Solidus originated none of this. It is one more attempt at the same pattern, built on W3C DID/VC instead of Sovrin's purpose-built ledger.
Bunu nasıl doğrularsınız
Test ağında çalışıyor. Ana ağda değil.
No single command proves a philosophy. The closest thing to a check is using the running products themselves, verify.solidus.network and identity.solidus.network/present are both live, and seeing whether the credential really lives in the holder's own wallet rather than a Solidus-held database record. There is no industry-wide "SSI conformance" test to point to; none is invented here.