DID Connect

The digital landscape is evolving at breakneck speed. Our daily lives—from gaming to workplace collaboration—are increasingly mediated by tech giants,

The recent California DMV Hackathon in January 2025 spotlighted the potential of mobile driver’s licenses (mDLs) for secure, efficient identity verifi

The conversation around onchain trust is no longer a futuristic concept; it's a present-day reality. While some may still be discussing the theoretica

As 2024 comes to an end, we at ArcBlock take pride in reflecting on a transformative year marked by innovation, community growth, and strategic advanc

Welcome to the Decentralized Me podcast, where we explore groundbreaking ideas shaping the future of decentralized platforms. In our latest episode, h

Apps created on ArcBlock can use Decentralized identity (DID) to facilitate GDPR compliance. However, compliance isn't automatic and ultimately depen

The open protocol and development kit for connecting users and dapps.

@arcblock/did-connect-js helps Node.js apps integrate DID Connect for secure authentication

@arcblock/did-connect-react aids DID Connect with components & session management.

A DID is a digital identifier. It helps its holder and a verifier establish who controls an identity and who a claim relates to. It is not a wallet, and it does not replace application accounts, sign-in methods, or permission rules.

ArcBlock’s DID method, using the did:abt: namespace to identify accounts, assets and other objects. Resolution requires support for this method.

A verifiable credential is a signed statement from an issuer about a subject. It gives a verifier something more specific to inspect than a screenshot or an assertion passed along without its source.