Decentralized Identity & KYC

Decentralized Identity (DID) & On-Chain KYC Provider

InSoBlok provides decentralized identity (DID) and privacy-preserving on-chain KYC: self-sovereign DIDs with custody wallets, delegated signers, and account recovery; W3C Verifiable Credentials with EIP-712 signatures and Merkle anchoring; and ZK proofs that verify a wallet meets a tier or compliance status without revealing the underlying data — resolvable across 20+ chains.

Key facts

  • Self-sovereign DID with custody wallets, delegated signers, recovery
  • W3C Verifiable Credentials, EIP-712 signatures, Merkle anchoring
  • ZK KYC: prove tier or compliance without exposing data
  • Cross-chain DID resolution across 20+ networks
  • Pairs with TasteScore reputation and sanctions screening
  • Selective disclosure for privacy-preserving trust portability

What is decentralized identity and on-chain KYC?

Decentralized identity (DID) gives users a portable, self-owned identity that isn’t locked to a single platform. On-chain KYC attaches verified attributes — like compliance status or a reputation tier — to that identity as cryptographic credentials. InSoBlok lets you verify those attributes with ZK proofs, so an app can confirm a user qualifies without ever seeing the sensitive data behind it.

Why choose InSoBlok for identity

CapabilityInSoBlokTypical alternatives
Identity modelSelf-sovereign DID + custody walletPlatform-held account
CredentialsW3C VCs, EIP-712, Merkle anchoredOff-chain database record
KYC privacyZK proof of tier/statusFull document/data sharing
RecoveryAccount recovery + delegated signersSeed-phrase-only
PortabilityResolves across 20+ chainsSingle ecosystem
Reputation linkBound to TasteScore + screeningIdentity only

Identity capabilities

Issue DIDs

Create self-sovereign identities with custody wallets and delegated signers.

Verifiable Credentials

Issue and verify W3C VCs with EIP-712 signatures and Merkle proof anchoring.

ZK KYC

Prove a user meets a tier or compliance requirement without revealing the data.

Account recovery

Offer social/delegated recovery instead of fragile seed-phrase-only flows.

Cross-chain resolution

Resolve the same identity and credentials across 20+ networks.

How it works

  1. Provision identity

    Issue a DID with a custody wallet and optional delegated signers.

  2. Attach credentials

    Bind verified attributes as W3C VCs anchored on-chain.

  3. Verify with ZK

    Apps request a proof of tier/status; users disclose only what’s needed.

  4. Resolve anywhere

    The identity and credentials resolve across supported chains.

Who it’s for

  • Apps needing compliant access without holding sensitive data
  • Wallets adding recoverable, portable identity
  • RWA and regulated DeFi requiring KYC’d participants
  • Communities issuing verifiable membership and badges
  • Platforms unifying identity with reputation and screening

Frequently asked questions

How is this different from traditional KYC?

Users keep a self-sovereign DID, and apps verify attributes via ZK proofs — confirming a tier or compliance status without collecting or storing the underlying personal data.

What credential standards do you use?

W3C Verifiable Credentials with EIP-712 typed signatures and Merkle proof anchoring, enabling selective disclosure.

Is the identity portable?

Yes. DIDs and credentials resolve across 20+ EVM and non-EVM networks, so identity and reputation travel with the user.

Can users recover a lost wallet?

Yes. Custody wallets support account recovery and delegated signers, avoiding seed-phrase-only failure modes.

Can identity be combined with risk scoring?

Yes. DID binds to TasteScore reputation and sanctions screening, so identity, trust, and compliance are unified.

Verify users privately — request access

Describe your KYC and identity needs — we’ll share an integration plan and pricing.

Prefer email? Reach us directly at hello@insoblokai.io. No spam — your details are used only to respond to this request.