W3C Digital Credentials API
Ayrıca şöyle anılır Digital Credentials API, DC API, navigator.credentials for VCs
The Digital Credentials API lets a website ask the browser for a credential, and lets the browser decide which wallet answers. It is the same shape as the passkey flow users already accept.
Why shipping before standardisation matters here
The specification is a Working Draft and two stable browsers already implement it. That inverts the usual sequence and changes the planning question from "when is this ratified" to "what happens when the browsers most users have already support it".
The strategic point, which is not technical
Whoever the browser offers in its chooser gets the presentation. A wallet reachable only by QR code competes on user effort; a wallet reachable through the browser competes on nothing, because it is simply there. This is the difference between a distribution channel and an integration.
Where Solidus sits
Outside it, and the absence is worth naming plainly rather than describing as roadmap. Being outside the browser path is a market-access position, not a missing feature.
Nereden geliyor
Bunu başkası belirtti. Solidus bir araya getiriyor.
W3C Federated Identity Working Group. Still a Working Draft, and already shipped in two stable browsers, which is an unusual order and means the practical deadline is set by browser releases rather than by the specification reaching Recommendation. It extends the Credential Management API so a website can request a digital credential the way it requests a passkey.
Bunu nasıl doğrularsınız
Solidus bunu inşa etmedi. Girdi kavramı açıklıyor.
The draft is public at w3.org and the API is observable in the browsers that ship it. Nothing on the Solidus side implements it, which is checkable by its absence from the wallet and frontend code.