PID
Ayrıca şöyle anılır Person Identification Data, Personal Identification Data (common but imprecise variant)
Origin: composes. The European Commission defines this schema; only a Member State (or its designee) may issue one. Solidus does neither.
PID stands for Person Identification Data, the baseline, government-issued set of identity attributes every EUDI Wallet must hold as its foundation credential. It's the digital equivalent of what's printed on a national ID card or passport: legal name, date of birth, a national identifier where applicable, plus a handful of optional fields like nationality or place of birth depending on the Member State. Every other credential a EUDI Wallet holds, a diploma, a professional license, an age-verification attestation, sits on top of the PID; the PID is what makes the wallet that specific person's wallet in the eyes of the system.
What makes a PID different from an ordinary credential
Two things:
- Only a Member State (or a party it explicitly designates) can issue one. This is a legal fact, not a technical one: the PID is what gives a EUDI Wallet its legal standing, so its issuance is restricted the same way issuing a passport is restricted.
- It must be issued in two credential formats at once, not one. The ARF requires a PID provider to issue the same PID as both an mdoc (the ISO 18013-5 CBOR-based format) and an SD-JWT VC, deliberately, because the two formats serve different presentation scenarios: mdoc is compact and built for offline, proximity presentation (tap your phone at a gate); SD-JWT VC is built for the existing web/OAuth ecosystem developers already know. A wallet only counts as holding a real PID if it can present either.
Solidus's actual relationship to it
Solidus does not issue PIDs and has no legal authority to: that's not a roadmap item, it's a structural fact about who is allowed to. What Solidus does issue is its own KYC credentials (KycLevel1Credential through KycLevel3Credential), which carry verification-level and country-of-verification metadata but were designed for a different purpose and do not map cleanly onto the PID's fixed attribute schema. Building a PID-shaped credential type, same OID4VCI issuance pipeline, PID-matching attribute set, is a real, buildable roadmap item with no protocol-level blocker; Solidus simply hasn't built it. And building it would not change the legal-authority problem above: a Solidus-issued, PID-shaped credential would still not be a PID in the eyes of eIDAS 2.0 unless issued by or on behalf of a Member State.
Check it yourself
The mandatory PID attribute set is public in the ARF's own PID rulebook and the Commission's PID Identification Manual, both discoverable from github.com/eu-digital-identity-wallet. Compare it against what Solidus's shipped KYC credentials actually contain: the gap is visible, not hidden.
Nereden geliyor
Bunu başkası belirtti. Solidus bir araya getiriyor.
The PID data schema and issuance rules are defined by the European Commission, the core definition traces back to the original 2014 eIDAS Regulation, with the detailed attribute set and issuance rules specified by implementing regulation and the ARF's PID rulebook under eIDAS 2.0. Only a Member State, or a party it explicitly designates, has legal authority to issue one: Solidus does not, and cannot.
Bunu nasıl doğrularsınız
Planlandı. Hiçbir şey inşa edilmedi.
The mandatory PID minimum attribute set is public in the ARF's PID rulebook and the Commission's PID Identification Manual, both discoverable from github.com/eu-digital-identity-wallet. Compare it yourself against the KYC credential schema Solidus actually issues, documented in the public protocol/SDK repos at github.com/solidusnetwork.