Decentralized DID System Development on Blockchain

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.

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.

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...');

Development Process and What's Included

1. Analytics: Requirements audit and use case analysis (1–2 weeks).
2. Design: Choose DID method, stack, and smart contract architecture.
3. Development: Smart contracts (EVM, Solana), wallet integration, VC lifecycle.
4. Testing: Unit tests, integration tests, gas benchmarks.
5. 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.

Digital Identity on Blockchain: DID, SBT, and Verifiable Credentials

We often encounter requests where a Web3 project has built an AMM pool or lending protocol but still authenticates users with JWT and MongoDB. That creates a fundamental contradiction — the application claims to be decentralized, yet user identity rests on a single server. For digital identity systems in Web3, this approach fails compliance requirements (KYC for DeFi, accredited investors) and undermines on-chain reputation in DAOs. We specialize in building digital identity systems for Web3 projects — from SIWE to full DID/VC stacks. Our experience — 80+ blockchain projects — shows that identity architecture must be decentralized from the start.

How does Sign-In with Ethereum solve authentication?

EIP-4361 (SIWE) removes login/password entirely. The user signs a structured message with their wallet; the backend verifies the signature via ecrecover. No credential leaks, no password hashing.

Implementation: siwe library (JS/TS) on the frontend, SiweMessage.verify() on the backend. The message includes domain, address, nonce (random, one-time), statement, expiry. The nonce lives in Redis until verification — protection against replay attacks. Today, SIWE is used by over 80 projects in the top 100 DeFi.

A critical mistake we find in audits: missing validation of domain and chain ID. If the backend does not check message.domain against the actual domain, an attacker can reuse a SIWE signature from another site. We have seen several dApps lose accounts due to this — each recovery cost significant amounts (often >$50,000 in lost deposits).

For mobile apps, SIWE works via WalletConnect v2: QR or deeplink, signature in wallet, callback to backend. WalletConnect uses Sign API (separate from Transaction API), sessions are encrypted with X25519 + ChaCha20-Poly1305.

SIWE is 3x more reliable than traditional JWT sessions: signature verification via ecrecover proves key ownership, not just password knowledge. Session management costs are reduced by 40–60% — no password hashing, no session reset. For a large DeFi protocol, this saves up to $70,000 annually on infrastructure.

What is DID and which method to choose?

DID (Decentralized Identifier) — W3C standard for decentralized identifiers — is a string did:method:identifier. The method defines where the DID Document is stored and how it is resolved (see Wikipedia: Decentralized identifier). The main methods we use in production:

For most DeFi projects, did:ethr or did:key suffice. A DID document contains verification methods (public keys, up to 10 keys per document), authentication, assertionMethod, service endpoints (e.g., link to KYC service). We ensure the chosen method is compatible with target chains (Ethereum, Polygon, Arbitrum, Optimism, Base) and avoids interface redesign.

Common mistakes when choosing a DID method:

• Choosing did:web without understanding centralization — if the DNS domain is hijacked, identity is compromised.
• Ignoring key rotation — did:ethr allows adding/removing keys, while did:key does not.
• Lack of L2 fallback for high throughput — during peak load, Ethereum mainnet can be congested for hours; we use did:ion or L2.

How does verification work via Verifiable Credentials?

Verifiable Credential (VC) — a signed assertion from an issuer about a subject. W3C format: JSON-LD or JWT. Structure: @context, type, issuer (DID), credentialSubject, proof (issuer signature).

Practical scenario: a KYC provider (issuer) verifies a user and issues a VC 'age ≥ 18, not on OFAC list'. The user stores the VC locally (wallet extension or mobile app). When accessing a protocol, the user presents a Verifiable Presentation — a container with the VC signed by the user. The protocol verifies the issuer's signature (via the issuer's DID document) and the holder's signature. No personal data goes on-chain. The protocol does not store a database of KYC-passed users. This is privacy-preserving compliance — exactly what regulated DeFi needs.

Zero-knowledge proofs for VCs take privacy to another level. Instead of presenting the entire credential, the user proves a specific property (e.g., age ≥ 18) without revealing the value. Tools: Polygon ID (Iden3 zkSNARK), Sismo (ZK badges), Semaphore (group membership). Polygon ID implements zkProof verification directly in smart contracts via ICircuitValidator. Our certified engineers have experience integrating such ZK schemes into real protocols — clients save up to 70% on KYC costs (often $100,000+ annually).

Why are Soulbound Tokens not suitable for mass adoption?

SBTs (EIP-5192, concept by Vitalik Buterin) are non-transferable NFTs. Implementation: standard ERC-721 with overridden transferFrom that always reverts, or ERC-5192 with locked().

Production uses:

• DAO Governance — Snapshot + SBT for one-person-one-vote. Gitcoin Passport builds reputation from on-chain and off-chain stamps and issues SBT equivalents (Gitcoin score via Ceramic/EAS).
• Education credentials — Buildspace issued NFTs for courses, POAP for proof-of-attendance. SBTs make them non-transferable — cannot buy someone else's history.
• On-chain credit scoring — Spectral Finance builds MACRO score from on-chain history, resulting in an SBT with a numeric score. Lending protocols use it for under-collateralized loans.

Key technical limitation: recovery mechanism. Losing access to a wallet means losing all SBTs. Without recovery, mass adoption is impossible. Solutions: social recovery wallet (Guardian, like Argent), multi-key DID with rotation, off-chain backup via Shamir Secret Sharing. We include recovery planning in every SBT project.

Ethereum Attestation Service as a standard identity layer

EAS is deployed on Ethereum mainnet, Optimism, Arbitrum, Base. Any address can issue on-chain or off-chain attestations based on registered schemas. A schema is an ABI-encoded structure. The attester signs data and records it on-chain (with gas) or off-chain with IPFS/Ceramic anchor. Verifiers read via IEAS.getAttestation(uid).

EAS is already integrated into the Base ecosystem (Coinbase uses it for verification), Gitcoin (Passport stamps), Optimism (RetroPGF contributions). It is becoming the de facto standard for on-chain identity layer on L2. Our developers are certified for EAS (experience with 5+ projects). According to EAS documentation, attestations can be revoked, and schemas supportup to 32 fields of arbitrary ABI types.

How can we choose the right identity solution for your project?

1. Analytics & compliance — map the user journey: who is issuer, verifier, what data is needed, what cannot be stored on-chain under GDPR.
2. Architecture design — choose between on-chain SBT, EAS, DID/VC stack. Data schema, ZK circuit (if needed).
3. Implementation — smart contracts (Solidity 0.8.x, Foundry/Hardhat), issuer service (Node.js/Go), holder wallet (ethers.js viem), verifier contract.
4. Testing & audit — unit tests, integration tests, fuzzing (Echidna), static analysis (Slither). Engage third-party auditor.
5. Deploy & support — deploy to target networks, monitoring (Tenderly), documentation, team training.

Deliverables

• Source code of smart contracts (Solidity, open-sourced under MIT)
• Issuer backend (Node.js/Go) with API for issuing VC/SBT
• Holder wallet integration (ethers.js viem, RainbowKit, WalletConnect)
• Verifier contract/script
• Architecture documentation, deployment runbook
• 2 months post-deployment support

Timeline Estimates

Cost is calculated individually based on schema complexity, number of chains, and compliance requirements. Contact us to discuss your scenario and get an optimal plan.

Order a digital identity system development — get a consultation with a senior engineer specialized in this field. Also, book a technical audit of your current identity system — we will identify bottlenecks and suggest concrete improvements.