W3C tech in the news: "W3C Advances DID Standard That Underpins Mobile Wallets and Digital Credentials" at Mobile ID World
"The technical standard that makes user-controlled digital credentials possible – including the kind stored in mobile wallets – has reached a new milestone at the W3C, signaling that the foundation for decentralized mobile identity is maturing."
https://mobileidworld.com/w3c-advances-did-standard-that-underpins-mobile-wallets-and-digital-credentials/
#DecentralizedIdentifiers #DigitalCredentials #MobileWallets
W3C Advances DID Standard That Underpins Mobile Wallets and Digital Credentials
ICYMI: W3C pushes DIDs v1.1 to implementations - and your ad stack may feel it: W3C's Decentralized Identifiers v1.1 enters Candidate Recommendation on March 5, 2026, inviting implementations of a cryptographic identity standard that could reshape how digital identity works online.
https://ppc.land/w3c-pushes-dids-v1-1-to-implementations-and-your-ad-stack-may-feel-it/ #W3C #DecentralizedIdentifiers #DigitalIdentity #Blockchain #Cryptography
W3C pushes DIDs v1.1 to implementations - and your ad stack may feel it
W3C's Decentralized Identifiers v1.1 enters Candidate Recommendation on March 5, 2026, inviting implementations of a cryptographic identity standard that could reshape how digital identity works online.
PPC LandW3C pushes DIDs v1.1 to implementations - and your ad stack may feel it: W3C's Decentralized Identifiers v1.1 enters Candidate Recommendation on March 5, 2026, inviting implementations of a cryptographic identity standard that could reshape how digital identity works online.
https://ppc.land/w3c-pushes-dids-v1-1-to-implementations-and-your-ad-stack-may-feel-it/ #W3C #DecentralizedIdentifiers #DigitalIdentity #Cryptography #Privacy
W3C pushes DIDs v1.1 to implementations - and your ad stack may feel it
W3C's Decentralized Identifiers v1.1 enters Candidate Recommendation on March 5, 2026, inviting implementations of a cryptographic identity standard that could reshape how digital identity works online.
PPC LandMeet me at #DICE2023 in #Zurich.
Let's talk #VerifiableCredentials and #DecentralizedIdentifiers as part of #SelfSovereignIdentity with all its exciting implications and potential.
Things to discuss: #GaiaX, #SSI implementation for Gaia-X Federation Services (#GXFS), #SSI at #Eclipse Foundation and how SSI is crucial for #dataspaces and #dataecosystems
📅 Date: June 7th to 9th 2023
📍 Location: Zurich, Switzerland
You can still register at https://diceurope.org
DICE Europe | Driving Innovation in Digital Identity
Join the international community of innovators and leaders shaping the future of digital identity and decentralized ecosystems through collaborative events and discussions.
@LukaszOlejnik if you are in the EU:
#DecentralizedIdentifiers. In general, making various kinds of e-identity and secret management work without relying on central CA trust hierarchy. Various blockchain companies are pivoting because a distributed ledger is a possible solution, certainly not the only one.
I don't understand what this thing is
Would anyone explain it to me please ?
An example for laypeople, like me
Thanks
#decentralizedIdentity
#decentralizedIdentifiers
https://www.w3.org/TR/did-core/
Decentralized Identifiers (DIDs) v1.0
Decentralized identifiers (DIDs) are a new type of identifier that
enables verifiable, decentralized digital identity. A DID refers to any
subject (e.g., a person, organization, thing, data model, abstract entity, etc.)
as determined by the controller of the DID. In contrast to
typical, federated identifiers, DIDs have been designed so that they may
be decoupled from centralized registries, identity providers, and certificate
authorities. Specifically, while other parties might be used to help enable the
discovery of information related to a DID, the design enables the
controller of a DID to prove control over it without requiring permission
from any other party. DIDs are URIs that associate a DID
subject with a DID document allowing trustable interactions
associated with that subject.
Been a while since I've updated y'all about #doauth.
Well, we can insert credentials under transaction with a very nice interface: a keypair and a claim map.
Underneath, it's 99%-compliant with #verifiablecredentials and #decentralizedidentifiers standards, but on the surface it just gives programmers what they care about!
Here's how to insert a credential / claim in #doauth: https://git.sr.ht/~doma/do-auth/commit/d2a28de2e48dfd3c739b40633b280c4ab4814826#test/db_test.exs-1-4
~doma/do-auth: Problem: Credential isn't inserted as one piece - sourcehut git
Decentralized Identifiers (DIDs) v0.13