Chialisp Guide Pt 8: DIDs & Attestations – Build Decentralized Identity on Chia

11 min read

Chia DIDs social recovery mechanism with M-of-N guardian approval system

Key Takeaways

  • Chia DIDs are singleton-based smart coins that create verifiable, decentralized identities for people, organizations, and devices
  • DIDs use social recovery mechanisms with M-of-N trusted guardians, allowing key rotation without losing your identity
  • Verifiable Credentials (VCs) work with DIDs to create tamper-proof digital attestations for education, employment, and KYC
  • Every DID is a unique singleton that maintains a persistent identity through a linear chain of spends
  • DIDs enable provable NFT authorship, self-custody wallet recovery, and asset grouping without central authorities

Article Summary

Chia DIDs are specialized smart coins built on singleton structures that provide programmable, rekeyable decentralized identifiers with built-in social recovery. These DIDs work with Verifiable Credentials to create a complete identity and attestation system that combines cryptographic security with human-readable recovery methods.

Understanding Chia DIDs: Your Blockchain Identity

A Decentralized Identifier (DID) in Chialisp is like your digital passport on the Chia blockchain.1 Unlike traditional accounts that tie you to a single private key, DIDs give you a permanent identity that survives even if you lose your keys. Think of it as having a bank account that you can recover through trusted friends, rather than needing to remember a 24-word seed phrase forever.

In the Chia ecosystem, every DID is implemented as a singleton – a unique coin that cannot be duplicated.2 This singleton wraps an inner puzzle that controls ownership, creating a two-layer security system. The outer singleton layer ensures your DID stays unique across the entire blockchain, while the inner layer handles who controls it right now.

The breakthrough here is simple: your DID identity stays the same forever, but you can change the keys that control it.1 This separation between identity and control solves one of crypto’s biggest problems – permanently losing access when you lose your keys.

How Singleton Architecture Works

A singleton is a special type of coin that can only exist once.3 Every time you spend a singleton, it creates exactly one new singleton with the same launcher ID. This creates an unbroken chain of coins that all share the same identity. The launcher ID – the coin ID of the very first coin in the chain – becomes your DID’s permanent identifier.

The singleton structure in Chialisp includes three key pieces: the mod hash (the code that runs), the launcher ID (your permanent identity), and the launcher puzzle hash (proof of legitimate creation).3 These three pieces get hashed together to create your full DID identifier, which starts with “did:chia:” followed by the hash.

This architecture means your DID can be spent and recreated thousands of times, but it always maintains the same identity. It’s like having a physical ID card that you can update with new photos and addresses, but the ID number never changes.

Inner Puzzles: The Control Layer

Inside every DID singleton sits an inner puzzle – typically a standard P2 (pay-to-public-key) puzzle that checks signatures.2 This inner puzzle is where ownership happens. When you want to spend your DID (to update it or transfer assets), you provide a solution that satisfies this inner puzzle.

The genius of this design is flexibility. The inner puzzle can be anything – a simple signature check, a multi-signature scheme, or even complex conditional logic.2 The singleton layer doesn’t care what the inner puzzle does; it only cares that there’s exactly one output and that output is a valid singleton.

DID Recovery: Never Lose Your Identity

The recovery mechanism is what makes Chia DIDs practical for real-world use.2 Instead of trusting yourself to never lose a private key, you create a list of trusted DIDs – think friends, family members, or backup services – who can help you recover access.

Here’s how it works: your DID stores a hash of your recovery list and a number for how many approvals you need.2 If you set up 3-of-5 recovery, you need three of your five trusted contacts to approve changing your DID’s inner puzzle to new keys you control. The recovery list itself isn’t visible on-chain until you actually need recovery, protecting your guardians’ privacy.

Recovery SetupSecurity LevelBest ForExample Use
2-of-3 GuardianMediumPersonal walletsTwo family members + one institutional backup
3-of-5 GuardianHighProfessional accountsThree colleagues + two trusted friends
5-of-7 GuardianVery HighHigh-value holdingsDistributed across different social circles
7-of-10 GuardianMaximumOrganizational treasuriesBoard members + key stakeholders + institutional services

The Recovery Process Step-by-Step

When you lose your keys, recovery happens through message coins.2 Each guardian DID creates a special message coin that approves your new inner puzzle hash and public key. These message coins sit on the blockchain waiting for your DID to consume them.

Your DID’s recovery mode checks that enough valid message coins exist (meeting your M-of-N threshold), verifies they’re from DIDs in your recovery list, and confirms the approvals all point to the same new puzzle.2 If everything checks out, your DID spends itself and recreates with the new inner puzzle – giving you back control with your new keys.

The recovery path includes several safety checks: it asserts your current DID coin ID and amount, calculates coin IDs for each recovery message to verify authenticity, and ensures the recovery list hash matches what’s stored in your DID.2 This multi-layered verification prevents attackers from tricking your guardians or hijacking the recovery process.

Verifiable Credentials: Digital Proof That Matters

Verifiable Credentials (VCs) are where DIDs become truly powerful.4 A VC is a cryptographically-signed statement about you – like a digital diploma, employment verification, or age proof – that’s issued to your DID. The credential lives on-chain, but the proofs (the actual data) can be revealed selectively.

Think of VCs like physical credentials but better. Your university issues a degree VC to your DID. You control that VC completely – you decide when to show it, who sees it, and which parts to reveal.4 The university can’t take it back (though they can revoke the proofs if needed), and anyone can verify it’s legitimate by checking the signature.

The W3C Verifiable Credentials standard guides Chia’s implementation.9 This means a VC issued on Chia could potentially work across different blockchain systems and traditional identity systems that support the same standard. You’re not locked into one ecosystem.

How VCs Work with DIDs

Every VC requires three parties: the issuer (who creates the credential), the holder (who owns it), and the verifier (who checks it).6 The issuer must have a DID to sign credentials. When minting a VC, the issuer creates a singleton containing the credential data and signs it with their DID’s keys.

The VC itself is a singleton just like a DID.4 This means it has a unique identity and can be updated or transferred. The VC stores a root hash of all the proofs it contains. These proofs are key-value pairs – things like “age: 25” or “degree: Computer Science” – that are hashed together to create the root.

When you need to prove something, you reveal only the specific proofs required.5 If a bar needs to verify you’re over 21, you can reveal just your age proof without showing your name, address, or any other credential details. The verifier checks that your revealed proof matches the root hash stored in your VC and that the VC signature is valid.

Minting and Managing VCs

To mint a VC, you first add proofs to your local database using the add_proof_reveal command.4 These proofs generate a root hash. You then create the VC singleton with this root hash, your DID as the issuer, and optionally specify a recipient DID.

VCs can be transferred between DIDs just like any other coin.5 When you transfer a VC, the new holder receives the credential singleton but needs to get the actual proof data separately. This separation ensures that credentials can move between holders while proof data remains private until explicitly shared.

Revoking proofs works by updating the VC to point to a new root hash – typically an empty one.5 Only the issuing DID can revoke proofs. This creates a permanent on-chain record that the credential is no longer valid, though the VC singleton itself continues to exist.

Use Cases for DIDs and VCs

NFT Creator Verification

NFT standards on Chia can implement DID-based creator verification.1 The CHIP-0007 NFT metadata standard specifically includes DID information to combine collection data with verifiable ownership, allowing artists to mint NFTs using their DIDs and creating an immutable link between creator identity and artwork that collectors can verify for authenticity.

When you mint an NFT with your DID, the NFT metadata includes your DID identifier. Anyone can look up that NFT and verify it was created by your specific DID. If you build a reputation as a creator, that reputation travels with your DID across all your works – and survives even if you change your signing keys.

KYC and Financial Services

Verifiable Credentials enable privacy-preserving Know Your Customer (KYC) processes.11 A KYC provider can issue a VC to your DID certifying that you’ve passed identity verification. You can then present this VC to different financial services without repeating the full KYC process each time.

Amberoon’s Manatoko VC, launched in September 2025, brings Chia’s DID and Verifiable Credential technology to community banking.11 The platform addresses KYC compliance challenges by enabling banks to verify customer identities using privacy-preserving VCs issued to customer DIDs. This implementation aligns with FDIC and FinCEN guidelines while reducing onboarding friction and compliance costs for community banks. The system demonstrates how financial institutions can leverage blockchain-based identity verification for regulatory compliance while maintaining customer privacy.

Educational Credentials

Universities and training programs can issue degree and certificate VCs to student DIDs.9 These credentials are tamper-proof and instantly verifiable by employers. Students control when and how to share their credentials, and institutions can revoke proofs if a degree is rescinded.

This system solves the fake diploma problem that costs employers billions annually. When an employer receives a credential, they can verify the issuing institution’s DID signature and check that the credential hasn’t been revoked – all without contacting the university directly.

Healthcare Records

Medical providers can issue VCs containing health information to patient DIDs. Patients control access to these credentials and can selectively disclose information to different providers. Emergency responders could verify blood type or allergies through a VC without accessing full medical records.

Access Control and Memberships

Organizations can issue membership VCs to member DIDs. These credentials can grant access to physical spaces, online platforms, or exclusive content. The organization can revoke access by revoking the VC’s proofs without needing to change locks or system passwords.

Technical Deep Dive: Message Coins

Message coins are temporary coins that carry information between DIDs.2 Unlike regular coins meant for payments, message coins exist solely to communicate approvals, updates, or attestations. They’re created, announced, and consumed in a single transaction flow.

When your DID needs to send an attestation – perhaps certifying that you’ve completed KYC with a service – it creates a message coin containing that attestation data.2 The recipient’s DID can consume this message coin to verify the attestation came from your DID specifically.

This creates a decentralized web of trust. DIDs can attest to each other’s identities, creating verifiable social graphs without central authorities.1 If ten trusted community DIDs attest that your DID belongs to a real person, verifiers can have confidence even without formal KYC.

Rekeying vs Recovery: Understanding the Difference

Rekeying happens when you voluntarily want to change your keys – maybe you’re rotating for security or moving to a new hardware wallet.1 You control your current keys, so you can sign the rekey transaction yourself. The DID’s inner puzzle gets updated to the new public key, and you retain all associated VCs and assets.

Recovery happens when you’ve lost access.2 You can’t sign transactions anymore, so your guardians sign instead. The process is similar – updating the inner puzzle – but the authorization comes from guardian message coins rather than your own signature. Recovery typically includes a timelock delay to prevent rushed or malicious recoveries.

DID Implementation Challenges

The biggest challenge in DID systems is the guardian selection problem.7 Who should your guardians be? Family members might all use the same password manager, creating correlated risks. Friends might not stay in touch. Institutional services cost money and introduce centralization.

Best practice suggests diversifying across different social circles and including at least one institutional guardian as a backup.7 You might use three close friends, two family members, one colleague, and one paid custody service. This makes collusion nearly impossible while ensuring someone will help if needed.

Guardian coordination is another challenge. When you need recovery, you must contact your guardians and convince them you’re really you. This happens off-chain through phone calls, video chats, or in-person meetings.7 The human element cannot be automated – which is both a feature (prevents automated attacks) and a bug (slows emergency recovery).

Privacy Considerations

DID systems must balance transparency and privacy carefully.1 The DID identifier itself is public – anyone can see it exists on-chain. But the recovery list hash keeps guardian identities private until recovery actually happens. Your metadata can be encrypted so only those with decryption keys can read it.

VC privacy is more complex.4 The credential exists on-chain, so everyone can see you have a VC from a particular issuer. But the proofs are stored off-chain in your local database. You choose which proofs to reveal and when. This selective disclosure lets you prove you’re over 18 without revealing your exact birthdate.

Expert Perspective on Decentralized Identity

Ethereum co-founder Vitalik Buterin has been a prominent advocate for social recovery wallets since 2021, emphasizing their importance for mainstream crypto adoption.7 In his influential article “Why We Need Wide Adoption of Social Recovery Wallets,” Buterin argues that traditional seed phrase backup methods create single points of failure that prevent billions of people from safely using cryptocurrency. Social recovery systems, like those implemented in Chia DIDs, distribute trust across multiple guardians while maintaining user sovereignty – addressing one of the crypto industry’s most critical usability challenges.

Chia Network’s focus on bringing security and regulatory compliance to blockchain infrastructure technology demonstrates the real-world utility of blockchain through projects that require cryptographic verification and decentralized systems.8 This philosophy extends to DID design where innovation enables both security and usability, making blockchain technology accessible to enterprises and individual users alike.

Case Studies: DIDs in Action

The NFT ecosystem on Chia demonstrates practical DID implementation.1 The CHIP-0007 NFT metadata standard specifically includes DID information to combine collection data with verifiable ownership, allowing artists to mint NFTs using their DIDs and creating an immutable link between creator identity and artwork that collectors can verify for authenticity.

In the financial services sector, Amberoon’s Manatoko VC represents the first major production deployment of Chia’s DID and VC primitives for banking compliance.11 The system processes customer identity verification for community banks, demonstrating that blockchain-based identity systems can meet strict regulatory requirements while providing better user experiences than traditional KYC processes. Following FDIC guidance in August 2025 that showed increased acceptance of alternative data sources, the platform positions early-adopting banks to capture competitive advantages in customer acquisition.

The Future of Chia DIDs

DID functionality continues to evolve through the Chialisp development roadmap.2 Ongoing improvements focus on easier identification methods, improved recovery workflows, and better integration with off-chain identity systems. The goal is making DIDs so easy to use that non-technical users don’t even realize they’re using blockchain technology.

Cross-chain DID bridges could enable Chia DIDs to work across multiple blockchains. Your single DID could control assets on Chia, Ethereum, and Bitcoin simultaneously, with recovery mechanisms that work regardless of which chain you’re interacting with. This interoperability would make DIDs truly universal identifiers.

Integration with traditional identity systems is another frontier. Imagine using your Chia DID to log into government services, proving citizenship through a VC issued by your country’s digital identity authority.9 The blockchain handles verification and privacy while governments maintain authority over who gets credentials.

Conclusion: Your Identity, Your Control

Chia DIDs represent a fundamental shift in how we think about digital identity. Instead of accounts tied to companies or keys you can lose, you get a permanent identity that survives key loss, company shutdowns, and platform changes. Combined with Verifiable Credentials, DIDs create a complete identity system that puts you in control.

The technology is here and working today.6 DIDs are being used for NFT creation, wallet recovery, credential issuance, and financial services compliance. As tools improve and adoption grows, DIDs will become as normal as email addresses – a permanent identifier you use across the internet, but one that you truly own.

Start experimenting with DIDs today. Create one, set up recovery guardians, and explore how VCs work. The concepts might seem complex at first, but they solve real problems that make crypto unusable for millions of people. Your future self – the one who lost their keys but recovered thanks to guardians – will thank you.

Chia DIDs FAQs

What are Chia DIDs and how do they work?

Chia DIDs are Decentralized Identifiers implemented as singleton smart coins on the Chia blockchain that provide permanent, verifiable identities. They work by wrapping an ownership puzzle in a singleton layer, creating an identity that persists even when control keys change through rekeying or social recovery mechanisms.

How does DID recovery work on Chia Network?

DID recovery uses social recovery where M-of-N trusted guardian DIDs can approve changing your DID’s inner puzzle to new keys you control. Guardians create message coins with approvals, and when enough valid messages exist (meeting your threshold), your DID can be recovered even if you’ve lost your original keys.

Can Chia DIDs be used with NFTs?

Yes, Chia DIDs are designed to work with NFTs to prove provenance and creator authenticity. When you mint an NFT using your DID, the NFT’s metadata includes your DID identifier, creating a cryptographic link that anyone can verify to confirm you’re the original creator.

What are Verifiable Credentials in the Chia ecosystem?

Verifiable Credentials are cryptographically-signed attestations issued to your DID by credential issuers like universities or employers. These credentials are tamper-proof singletons containing proof hashes that you control, allowing selective disclosure of information while maintaining verifier trust through on-chain signatures.

How do I set up guardian DIDs for recovery?

To set up guardians for your Chia DID, you create a list of trusted DIDs and specify how many approvals you need (M-of-N threshold). Your DID stores a hash of this guardian list, and you can update it through normal DID operations, though changes typically include a timelock delay for security.

Chia DIDs Citations

  1. CHIP-0004: DID1 Standard Specification – Chia Network GitHub
  2. DIDs Documentation – Chialisp.com Official Guide
  3. Singletons Architecture – Chialisp.com Technical Documentation
  4. Verifiable Credentials Guide – Chia Documentation
  5. Verifiable Credentials RPCs – Chia Technical Reference
  6. Version 1.8.2 Release: Verifiable Credentials Support – Chia Network (June 2023)
  7. Why We Need Wide Adoption of Social Recovery Wallets – Vitalik Buterin
  8. Chia Network Leadership Transition Announcement – Business Wire (January 2023)
  9. Verifiable Credentials: The Ultimate Guide 2025 – Dock Labs
  10. State Management in Chialisp – Chia Documentation
  11. Amberoon Launches Manatoko VC on Chia Network – Amberoon Press Release (September 2025)