How-to Guides
This section provides practical, task-oriented recipes for the most common DID Connect implementation scenarios. Each guide offers step-by-step instructions and copyable code examples to help you integrate specific features into your application.
Before diving in, it's recommended to have a basic understanding of the library's architecture. If you haven't already, please review the Core Concepts section.
Choose a guide below to get started with a specific task.
Request a Verifiable Credential#
Learn how to ask a user to present a Verifiable Credential (VC) from their wallet, such as a digital passport or a membership certificate. This is a common pattern for verifying identity, age, or qualifications without collecting sensitive personal data.
Request a Digital Asset (NFT)#
This guide shows you how to request proof of ownership for a specific digital asset or NFT. You can use this to implement token-gated access to exclusive content, features, or communities.
Request a Signature#
Discover how to ask a user to sign a message or a blockchain transaction. This is essential for confirming user consent to terms of service, authorizing on-chain actions, or verifying control over a DID.
Chain Multiple Workflows#
Learn how to link multiple authentication and claim requests into a single, seamless multi-step process. This is ideal for complex onboarding sequences, multi-factor authentication, or checkout flows that require several user actions.
Implement Delegated Connect#
Implement an advanced authentication flow where one DID can authorize another DID (an agent) to perform actions on its behalf. This pattern is useful for applications where automated services or bots need to interact with users through DID Connect.
Enable Secure Mode#
Understand how to securely handle sensitive information, such as newly generated private keys from a keyPair claim. This guide explains how to establish an encrypted channel between your application and the user's wallet to protect data in transit.
These guides provide the practical knowledge to build user-centric applications. Once you are familiar with these patterns, you can dive into the API Reference for a detailed breakdown of all available classes, methods, and configurations.