The practical guide to web3 domains for creators: what owning your name actually buys, what ENSv2 pricing looks like in 2026, and where the honest limits are.
Verifiable Credentials (VCs) are tamper-evident digital claims about a person or entity, cryptographically signed by trusted issuers. They can be verified instantly without contacting the issuer.
What are Verifiable Credentials?
Components
Issuer : Who creates the credential
Subject : Who the credential is about
Holder : Who possesses the credential
Verifier : Who checks the credential
Example VC
{
"@context": ["https://www.w3.org/2018/credentials/v1"],
"type": ["VerifiableCredential", "UniversityDegreeCredential"],
"issuer": "did:eth:0xuniversity",
"issuanceDate": "2024-01-01T00:00:00Z",
"credentialSubject": {
"id": "did:eth:0xstudent",
"degree": "Computer Science",
"GPA": "3.8"
},
"proof": {
"type": "EcdsaSecp256k1Signature2019",
"created": "2024-01-01T00:00:00Z",
"proofPurpose": "assertionMethod",
"verificationMethod": "did:eth:0xuniversity#key-1",
"jws": "eyJhbGciOiJFUzI1NksiLCJiNjQiOmZhbHNlLCJjcml0IjpbImI2NCJdfQ.."
}
}
Copy link
Types of VCs
Personal
Identity documents
| Age verification
Citizenship
| Marital status
Professional
Employment history
| Degrees and certifications
Professional licenses
| Skills assessments
Financial
Income verification
| Credit history
Accreditation status
| Tax records
Health
Vaccination records
| Medical certifications
Test results
| Insurance status
Social
Memberships
| Community reputation
Contributions
| Achievements
How VCs Work
Issuance Flow
1. Issuer verifies information
2. Creates VC with claims
3. Signs with private key
4. Sends to holder's wallet
5. Holder stores encrypted VC
Copy link
Verification Flow
1. Holder presents VC to verifier
2. Verifier checks:
- Issuer's signature
| Credential not expired
- Not revoked
| Meets requirements
3. Verification complete
4. No issuer contact needed
Copy link
VC vs Traditional Credentials
Feature VC Traditional Verification Instant Contact issuer Tampering Impossible Possible Privacy Selective disclosure Full exposure Portability Digital Physical/digital Cost Low High
VC Standards
W3C Verifiable Credentials
Official web standard
| Universal format
Interoperable
| Growing adoption
Key Properties
Tamper-evident : Cannot be forged
Cryptographic : Mathematically secured
Portable : Works across systems
Privacy-preserving : Selective disclosure
Selective Disclosure
What It Is
Share only needed information:
Prove age 21+ without showing birthdate
| Verify degree without GPA
Confirm employment without salary
Zero-Knowledge Proofs
Prove facts without revealing data
| "I'm over 21" without showing ID
Enhanced privacy
| Minimal disclosure
VC Use Cases
Employment Verification
Traditional: Call HR, wait days
VC: Instant verification of:
- Employment dates
| Job title
- Salary range
| Performance
Copy link
Education
Traditional: Request transcript
VC: Instant proof of:
- Degree earned
| Graduation date
- Major/minor
| Honors
Copy link
KYC/AML
Traditional: Submit documents repeatedly
VC: One-time verification:
- Identity verified
| Reusable across services
- Privacy maintained
Copy link
Age Verification
Traditional: Show full ID
VC: Prove:
- Age > 21: ✓
| No other data shared
Copy link
VC Wallets
What They Store
Verifiable credentials
| Private keys
Presentation definitions
| Consent records
Popular Wallets
Spruce : Ethereum -based
| Trinsic : Enterprise
Microsoft Authenticator : ION
| Dock : Multi-chain
Trinsic : End-to-end VC platform
| Veramo : Open-source framework
Hyperledger Indy : Enterprise
| Dock : Developer-friendly
Enterprise Solutions
Microsoft Entra : Verified ID
| IBM : Digital Health Pass
Workday : Credential integration
Benefits of VCs
For Holders
Own your data
| Privacy control
Instant verification
| Reusable credentials
Reduced friction
| Better UX
For Issuers
Lower verification costs
| No ongoing queries
Brand trust
| Digital transformation
For Verifiers
Instant verification
| No manual checks
Reduced fraud
| Lower costs
Better UX
| Trust without contact
VC Privacy Features
Decentralized Identifiers
Issuer has DID
| Verifier checks DID
No central database
| Trust is cryptographic
Minimal Disclosure
Share only what's needed
| Zero-knowledge options
Privacy by design
| User control
Revocation
Issuer can revoke VCs
| Revocation registries
Real-time status
| Trust maintained
VC Challenges
Adoption
Still early days
| Limited issuer support
Verifier acceptance
| Network effects needed
Usability
Complex for users
| Wallet management
Understanding required
| UX improvements needed
Many implementations
| Not all compatible
Standards evolving
| Fragmentation risk
Recovery
Lost wallet = lost VCs
| No standard recovery
Need backup solutions
| Complex process
VC Implementation
For Issuers
// Create VC
const vc = await veramo.createVerifiableCredential({
credential: {
issuer: { id: 'did:eth:0xissuer' },
credentialSubject: {
id: 'did:eth:0xsubject',
degree: 'Computer Science'
},
type: ['UniversityDegree']
},
proofFormat: 'jwt'
})
Copy link
For Verifiers
// Verify VC
const result = await veramo.verifyCredential({
credential: presentedVC
})
if (result.verified) {
// Credential is valid
}
Copy link
Standards Bodies
W3C : VC Data Model
| DIF : Interoperability
W3C CCG : Credentials Community
Projects
Hyperledger : Indy, Aries
| Sovrin : Public network
Trinsic : Platform
| Veramo : Framework
VC vs SBT
Feature VC SBT Storage Off-chain On-chain Privacy High Public Revocation Easy Hard Cost Low Gas feesVisibility Private Public
Future of VCs
Trends
Government adoption
| National digital IDs
Enterprise integration
| HR systems
Mobile-first
| Wallet apps
Innovations
Biometric VCs
| Hardware binding
AI verification
| Fraud detection
Social graphs
| Reputation systems
Getting Started with VCs
As a Holder
Get a VC wallet
Request VCs from issuers
Store securely
Present when needed
As an Issuer
Choose platform
Define credential schema
Set verification process
Issue VCs
Maintain revocation registry
As a Verifier
Define requirements
Integrate verification
Trust issuers
Accept VCs
VC Best Practices
Security
Secure private keys
Verify issuer DIDs
Check revocation status
Use trusted wallets
Backup credentials
Privacy
Use selective disclosure
Minimize shared data
Understand what you share
Review before presenting
Audit credential usage
VC Resources
Documentation
W3C VC Data Model
| DIF specifications
Platform docs
| Community guides
Veramo (veramo.io)
| Trinsic (trinsic.id)
Dock (dock.io)
| Hyperledger Indy