Veramo is an open source JavaScript framework for verifiable data and decentralized identity, successor to uPort. Built on W3C DID and Verifiable Credentials standards with zero biometric collection, no central server, and no data retention. Users control their own identity data stored exclusively in their own wallets. Supports multiple DID methods including did:web, did:key, and did:ethr. True self-sovereign identity where no corporation or government holds your credentials.
Interested in promoting your brand? Create yours free!
Launch Your Brand →Sign in to leave a comment
Sign In →Built authentication on Veramo. Users verify once, credential stays in wallet. True self-sovereign identity.
Open source DID framework. No central server, no data collection. Users control identity in their wallet.
Real-time community metrics & activity
Total Views
0
Total Upvotes
0
Active Brands
0
Comments Today
81
No posts yet. Be the first!
Brands getting discovered...
nowCommunity growing daily
1m agoUnlock full product intelligence
Deep analytics, privacy reports, competitor comparisons, and expert reviews. Everything you need to make informed decisions.
Try SeekerPro Free for 14 Days→$15.99/mo after trial. Cancel anytime. No card charged today.
Run a free AI-powered privacy audit. Compare data practices, transparency, and user rights.
Want AI-powered analysis?
Compare this brand against competitors, get growth predictions, and export reports.
Get deep-dive reports on every company that touches your data. SeekerPro members see breach timelines, DSAR success rates, and risk scores before anyone else.
Get Started FreeAdd your brand to the Noizz catalog of 28,697 brands · updated daily
NexusBro
AI Website QA Audits
Is your website as strong as your brand?
Run a free QA audit. 125+ checks. Copy-ready fix prompt in 60 seconds.
125+
Checks
100K
Pages
0-100
Score
Used by supabase.com, vercel.com, github.com, and 30+ sites
Free to get started. No credit card required.
Explore NoizzCeramic Network
Ceramic Network provides decentralized data streams for user-owned data and identity with no central server storing your information. ComposeDB enables decentralized data composition without vendor lock-in. Identity data stays with the user, never the platform. Used by GitcoinPassport, Orbis, and leading Web3 projects. Fully open source, community-governed, and censorship-resistant. Your data, your control, your infrastructure.
Spruce ID
SpruceID builds open source tools for decentralized identity using W3C standards. Sign-In with Ethereum enables wallet-based authentication without biometric collection. DIDKit library provides credential issuance and verification. Treehouse identity wallet stores credentials locally on your device. No biometric data is ever collected, transmitted, or stored. Active contributor to W3C DID and Verifiable Credentials specifications shaping the future of digital identity.
Dock.io
Dock provides a blockchain-based platform for issuing and verifying credentials with selective disclosure, allowing users to prove specific attributes without revealing their full identity. Certs platform enables organizations to issue tamper-proof digital credentials. Built on Substrate blockchain with proof-of-stake consensus. Some centralized SaaS components for enterprise users but core credential verification is decentralized and user-controlled.
Scandal alerts, breach notifications, DSAR deadlines, and protection guides. Join 2,400+ privacy-conscious professionals.
No spam. Weekly only. Unsubscribe anytime.
Tools trusted by thousands of privacy-conscious users worldwide
No card charged today. Cancel anytime.
Want unlimited access? Explore SeekerPro
SeekerPro gives you the full picture on every brand.
Self-sovereign identity (SSI) is a model where individuals own and control their digital identity without depending on any central authority. Instead of your identity data living on corporate servers at Facebook, Google, or government databases, SSI stores credentials in a digital wallet on your own device. You decide what to share, with whom, and for how long. The concept was formalized by Christopher Allen in 2016 around ten principles including user control, transparency, portability, and consent. SSI matters because the current identity model is broken: centralized databases are honeypots for hackers, companies monetize your personal data, and billions of people worldwide lack any formal identity at all. SSI enables financial inclusion by allowing people to build verifiable digital identities without needing traditional documentation. It also reduces the attack surface for identity theft since there is no central database to breach. Organizations like the Decentralized Identity Foundation and the W3C are building the technical standards that make SSI practical.
Zero-knowledge proofs (ZKPs) are cryptographic protocols that allow one party to prove a statement is true without revealing any information beyond the truth of that statement. In identity systems, this is transformative. Instead of handing over your full date of birth to prove you are over 18, a ZKP lets you prove the age requirement is met while the verifier learns nothing else about your birthdate. Similarly, you could prove your income exceeds a threshold for a loan application without disclosing your exact salary. The two main types used in identity are zk-SNARKs and zk-STARKs. Polygon ID uses ZKPs to enable private credential verification on the Ethereum blockchain. Zcash pioneered ZKPs in cryptocurrency for private transactions. The technology is computationally intensive but has become practical for mobile devices through recent optimizations. ZKPs solve the fundamental tension in identity verification: the need to prove something about yourself without creating a trail of overshared personal data that can be breached, sold, or misused.
Centralized identity systems store your data on servers controlled by a single organization. When you log in with Google, Facebook, or a government portal, that entity holds your identity data, controls access to it, and can revoke it at will. This creates single points of failure: if the server is breached, millions of identities are compromised. If the provider shuts down or bans your account, you lose access. Decentralized identity distributes control. Instead of one entity holding everything, your credentials are issued by trusted sources, stored in your personal wallet, and verified through cryptographic proofs without contacting the issuer. Blockchain or distributed ledger technology often serves as a trust anchor for verifying credential schemas and revocation status without storing personal data on-chain. Federated identity (like SAML or OAuth) sits in between: multiple providers can issue identity, but each still controls their piece. Decentralized identity removes the need to trust any single party and gives individuals genuine control over their digital presence.
Verifiable credentials (VCs) are a W3C standard for digital credentials that are tamper-evident, cryptographically signed, and can be verified without contacting the original issuer. They follow a three-party model: an issuer (like a university or government) creates and signs a credential, a holder (the individual) stores it in their digital wallet, and a verifier (like an employer or service) checks its authenticity. A VC contains claims about the holder, metadata about the credential itself, and a cryptographic proof signed by the issuer. When presented to a verifier, the signature is checked against the issuer public key, which may be registered on a blockchain or public key infrastructure. VCs can represent anything: diplomas, professional licenses, health records, citizenship, or employment history. Unlike physical documents, they cannot be forged, can be selectively disclosed (sharing only specific fields), and can be instantly revoked by the issuer if needed. The VC Data Model specification is now widely adopted by decentralized identity platforms.
Getting started with decentralized identity is increasingly accessible. Begin by choosing a digital identity wallet. Popular options include Spruce ID which uses Ethereum-based DIDs, Walt.id which supports multiple DID methods, and the EU Digital Identity Wallet being piloted across member states. If you are in the Web3 space, Polygon ID offers verifiable credentials integrated with the Polygon blockchain. Install the wallet app, which will generate your cryptographic key pair and DID. You can then collect verifiable credentials from participating issuers. Some universities now issue digital diplomas as VCs. Several countries including Bhutan, Estonia, and members of the EU are piloting government-issued digital credentials. For developers, the Veramo framework and DIDKit SDK provide tools to build decentralized identity into applications. The technology is still early, and you will find limited acceptance compared to traditional ID, but using it now puts you ahead of the transition and supports the ecosystem growth needed for mainstream adoption.
Blockchain-based identity can be private, but it depends entirely on the implementation. A common misconception is that any data written to a blockchain becomes public. Well-designed decentralized identity systems never store personal data on-chain. Instead, only references like DID documents, credential schemas, and revocation registries are on the ledger. Your actual personal information stays in your local wallet. When you present a credential, the verifier checks the cryptographic proof against the on-chain public key without your data touching the blockchain. However, poor implementations exist. Some early projects stored hashed personal data on-chain, but hashing alone is not sufficient protection since common data fields can be brute-forced. Transaction patterns can also leak metadata: if your DID interacts with specific verifiers at specific times, an observer might infer behavior patterns. Privacy-focused implementations use zero-knowledge proofs to prevent even this correlation. The blockchain layer should function as a decentralized trust registry, not a data store. Evaluate any system by asking what exactly is written on-chain.
DID (Decentralized Identifier) methods define how a DID is created, resolved, and managed on a specific infrastructure. The W3C DID specification is method-agnostic, and dozens of methods now exist. did:web uses standard web infrastructure, resolving to a DID document hosted on a domain, making it easy to adopt but somewhat centralized. did:key encodes a public key directly in the identifier, requiring no blockchain, making it simple and fast but not updatable. did:ethr is based on Ethereum, leveraging smart contracts for DID management. did:ion runs on Bitcoin layer 2 using the Sidetree protocol, offering high decentralization. did:sov is the Hyperledger Indy method used by the Sovrin Network, designed specifically for self-sovereign identity. did:pkh derives from blockchain account addresses, bridging existing crypto wallets to DIDs. Each method involves tradeoffs between decentralization, performance, cost, and features. For most users, the method matters less than the wallet and credential ecosystem supporting it. Interoperability between methods is improving through universal resolver implementations.
Privacy-preserving KYC aims to meet regulatory know-your-customer requirements without the traditional approach of copying and storing sensitive documents. The concept works by separating the verification event from the ongoing storage of identity data. In one model, a trusted issuer like a bank or government verifies your identity once and issues a reusable verifiable credential. When another service needs KYC, you present the credential from your wallet. The new service can verify it is authentic without receiving your raw documents. Zero-knowledge proofs enhance this further by letting you prove specific attributes, such as being over 18 or resident in a specific country, without revealing the full credential. Companies like Fractal ID, Polygon ID, and zkMe are building these systems. Regulatory acceptance is the main barrier: most financial regulators still require institutions to collect and store customer documents directly. However, the EU eIDAS 2.0 regulation is creating a framework for reusable digital identity that could make privacy-preserving KYC the standard approach in Europe.
Portable identity across services is one of the core promises of decentralized identity, and it is becoming practical. With a DID-based identity, you hold credentials in your wallet that can be presented to any verifier that supports the standard. A university-issued diploma credential could be used for job applications, professional licensing, and further education without each institution needing to verify it independently. In Web3, Sign-In with Ethereum (SIWE) already allows a single Ethereum address to authenticate across thousands of applications. The OpenID for Verifiable Credentials specification is bridging decentralized identity with the existing OpenID Connect infrastructure that powers most web authentication. The challenge is adoption: each service must choose to accept verifiable credentials, and network effects mean the ecosystem only becomes useful at scale. Interoperability standards from the Decentralized Identity Foundation and the W3C are critical. Currently, portability works best within specific ecosystems like Polygon ID applications or Sovrin Network participants, but cross-ecosystem interoperability is actively developing.
Identity recovery in decentralized systems cannot rely on a forgot password email from a central provider, so alternative mechanisms have been developed. Social recovery, popularized by Vitalik Buterin, designates trusted contacts as guardians who can collectively authorize recovery of your identity if you lose access. A threshold scheme might require three out of five guardians to approve. Multi-device recovery distributes key shares across your devices so that losing one does not mean losing everything. Hardware backup using security keys or hardware wallets provides offline recovery options. Some systems use Shamir Secret Sharing to split your master key into fragments stored in different locations, requiring a minimum number to reconstruct. Hierarchical deterministic key derivation allows regenerating all keys from a single seed phrase, similar to cryptocurrency wallet recovery. The EU Digital Identity Wallet specifications include provisions for government-backed recovery. Each approach involves tradeoffs between security and convenience. The critical practice is setting up recovery before you need it, as retroactive recovery in a truly decentralized system may be impossible.
Get deep-dive reports on every company that touches your data. SeekerPro members see breach timelines, DSAR success rate...
Learn MoreRun a full privacy and compliance audit on any website in 60 seconds. NexusBro scans cookie consent, tracker behavior, a...
Learn MoreStop wasting hours on manual DSAR filings and cookie consent management. BliniBot handles the busywork so your team can ...
Learn MoreCivic
Civic provides blockchain-based identity verification with a user-controlled credential wallet. Civic Pass enables on-chain identity verification for DeFi, NFT, and Web3 applications without centralized biometric storage. Users complete verification once and reuse credentials across platforms. Token-gated access control for decentralized applications. Some centralized verification steps during initial onboarding but ongoing data stored in user wallets, not corporate servers.