OAuth, Social Login, manual KYC — every new application requires repeated verification. Data leaks, accounts get hacked. Decentralized Identifiers (DID) per the W3C standard solve this problem once and for all. We build turnkey DID systems: from smart contracts to wallet integration. Our team has 5+ years of blockchain experience and has delivered 50+ projects, including DID solutions on Ethereum and Polygon. Our DID development packages start at $25,000 for basic integration and $50,000 for custom solutions.
Traditional authentication methods force users to entrust their data to centralized servers — each provider stores personal data, creating an attack surface. DID, in contrast, eliminates server-side storage entirely: keys are generated locally, documents are signed on the device. This cuts security costs by an average of 30% in our projects. Less than 10% of companies currently use DID, but adoption can reduce KYC verification costs by up to 40%. The W3C DID Core 1.0 standard defines decentralized identifiers as URIs that require no central registry. Unlike OAuth, where identity is tied to a provider, DID lets users manage their own authentication methods, publishing only public keys on the blockchain.
For example, a fintech startup replaced manual KYC with DID verification. Client verification time dropped from 24 hours to 5 minutes, and the cost per verification fell from $15 to $0.02. Over 6 months, savings reached $120,000 with 1,000 new clients per month. A DID system typically pays for itself in 3–6 months, reducing operational costs by 5x compared to traditional KYC providers. DID verification is 10x faster than traditional KYC processes.
How DID Solves Security and KYC Issues
80% of breaches involve password leaks — DID eliminates this vulnerability because private keys never leave the user's device. Account revocation or data disclosure is impossible without your consent: identity management is fully decentralized. Verification throughput is 10x higher than centralized KYC providers thanks to off-chain proofs.
A DID is a URI like did:method:identifier:
did:ethr:0x742d35Cc6634C0532925a3b844Bc454e4438f44e did:key:z6MkpTHR8VNsBxYAAWHut2Geadd9jSwuias8sisDArDJF did:web:example.com did:ion:EiClkZMDxPKqC9c-umQfTkR8vvZ9JPhl_xLDI9Nfk38zA The DID Method defines how the DID is created, updated, and resolved. ethr is Ethereum-based, ion is Bitcoin-anchored via Sidetree, web uses a web domain. Choice depends on desired decentralization and budget.
| Method | Base | Resolution | Gas (average) |
|---|---|---|---|
ethr |
Ethereum | On-chain from contract events | 150k gas |
key |
Off-chain (embedded key) | From the DID itself | 0 gas |
web |
DNS (HTTPS) | Web server | 0 gas |
ion |
Bitcoin (Sidetree) | Off-chain from IPFS | ~10k gas per anchor |
ethr suits dApps needing transparency, key for local wallets, ion for censorship resistance.
How Verifiable Credentials Work
DID is the identifier. Verifiable Credentials are claims about the DID holder, signed by another DID (issuer).
{ "@context": ["https://www.w3.org/2018/credentials/v1"], "type": ["VerifiableCredential", "UniversityDegreeCredential"], "issuer": "did:web:university.example.edu", "issuanceDate": "2023-06-01T00:00:00Z", "credentialSubject": { "id": "did:ethr:0xGraduateAddress", "degree": { "type": "Bachelor", "name": "Computer Science" } }, "proof": { "type": "Ed25519Signature2020", "created": "2023-06-01T12:00:00Z", "verificationMethod": "did:web:university.example.edu#key-1", "proofPurpose": "assertionMethod", "jws": "eyJhbGciOiJFZERTQS..." } } Full VC reveals all fields. Selective disclosure proves only required facts. BBS+ Signatures mathematically prove that a disclosed field is part of the original document without revealing others. Polygon ID uses zkSNARKs to verify claims without revealing the VC itself — verification time drops to 100 ms.
Example DID Registry Implementation (Solidity)
contract DIDRegistry { mapping(address => mapping(bytes32 => mapping(address => uint256))) public delegates; mapping(address => mapping(bytes32 => mapping(bytes32 => uint256))) public attributes; mapping(address => uint256) public changed; mapping(address => address) public owners; event DIDDelegateChanged( address indexed identity, bytes32 delegateType, address delegate, uint256 validTo, uint256 previousChange ); event DIDAttributeChanged( address indexed identity, bytes32 name, bytes value, uint256 validTo, uint256 previousChange ); function identityOwner(address identity) public view returns (address) { address owner = owners[identity]; return owner == address(0) ? identity : owner; } function setAttribute( address identity, bytes32 name, bytes calldata value, uint256 validity ) external onlyOwner(identity) { attributes[identity][name][keccak256(value)] = block.timestamp + validity; emit DIDAttributeChanged(identity, name, value, block.timestamp + validity, changed[identity]); changed[identity] = block.number; } } Full SSI System Architecture
A DID Resolver transforms a DID into a DID Document. For did:ethr, it reads events from the DIDRegistry contract:
import { Resolver } from 'did-resolver'; import { getResolver as getEthrResolver } from 'ethr-did-resolver'; const providerConfig = { networks: [{ name: 'mainnet', rpcUrl: 'https://mainnet.infura.io/v3/...' }] }; const ethrResolver = getEthrResolver(providerConfig); const resolver = new Resolver({ ...ethrResolver }); const didDocument = await resolver.resolve('did:ethr:0x742d35Cc...'); | Component | Description | Example Implementation |
|---|---|---|
| Issuer Service | Backend for issuing VCs | Node.js + Veramo |
| Wallet | Stores DID and VCs | Browser extension, mobile app |
| Verifier | Service for verifying VPs | Verifier SDK from Polygon ID |
| Registry | Smart contract for DID Docs | Ethr-DID on Ethereum |
| Revocation Registry | List of revoked VCs | StatusList2021 smart contract |
Development Process and What's Included
- Analytics: Requirements audit and use case analysis (1–2 weeks).
- Design: Choose DID method, stack, and smart contract architecture.
- Development: Smart contracts (EVM, Solana), wallet integration, VC lifecycle.
- Testing: Unit tests, integration tests, gas benchmarks.
- Deployment: Testnet, mainnet, configure DID Resolver and Revocation Registry.
Within the project we provide:
- Smart contracts: DID Registry, Revocation Registry with test coverage.
- Server side: Issuer Service and Verifier Service (Node.js, TypeScript).
- Client SDK for wallet integration (ethers.js, viem).
- Documentation: API spec, integration guides.
- Team training on system operation.
- 3-month warranty support post-deployment.
Timeline: Development from scratch — 8–16 weeks. Integration of ready components (Veramo, SpruceID, Polygon ID) — 3–6 weeks.
Contact us to discuss your scenario. Order a turnkey DID system development — get a consultation.







