THE MOST ANONYMOUS IDP
did:uiid SCHEME
SPECIFICATION CORES.
A revolutionary identity provider standard giving you 100% anonymous, zero-knowledge, decentralised single sign-on capabilities. No remote tracking, no server logs, zero database honeypots.
CENTRALIZED IDENTITY IS
A MASSIVE HONEYPOT.
Traditional Identity Providers (like Auth0, Okta, Google, or Meta) track every single session. When you click "Sign in with Google", they record the exact timestamp, your IP address, device specifications, and target domain context.
This surveillance capitalism infrastructure sells your profile details. Furthermore, a breach at any centralized Identity Provider exposes authentication tokens, letting hackers hijack thousands of client accounts simultaneously.
Surveillance Tracking Loop
Google and Meta track your navigation history globally to target invasive, un-consented ads.
Central Compromise risk
A single server vulnerability in centralized SaaS platforms compromises billions of enterprise users instantly.
THE DECENTRALIZED
did:uiid SPECIFICATION.
UIID operates as the world's most anonymous Identity Provider. Utilizing the `did:uiid` standard schema, logins are verified locally via offline zero-knowledge enclaves, guaranteeing that we (the provider) cannot track your sessions.
True Peer-to-Peer Logins
Establish encrypted direct communication channels, letting clients verify identities with zero remote callbacks.
Zero Metadata Footprint
Our servers never see who you are authenticating with, achieving complete metadata isolation.
TOTAL DECENTRALIZATION
- ✓ No central user sessions database
- ✓ Dynamic cryptographic signature keys
- ✓ 100% Open-Source software core
- ✓ Compliant with W3C DID specifications
did:uiid PROTOCOL ELEMENTS
DID Document
Public keys and service endpoints reside strictly inside decentralized, cryptographically verifiable DID Documents.
OIDC Integration
Exposes standard OpenID Connect endpoints, allowing companies to upgrade their security in under 10 minutes.
Sovereign Keys
Your private keys reside strictly inside your device enclaves, meaning you hold exclusive master control.
Dynamic Formats
Express identifiers in secure alphanumeric, emoji, or word formats to ensure high user readability.
did:uiid RESOLUTION METHOD
Resolve Query
The target client application queries the DID resolver with the target user's custom `did:uiid` URI.
Public Key Extraction
The resolver parses the signed cryptographic document on-demand, extracting active encryption and signature public keys.
Local Authentication
The user authorizes access using their mobile biometrics, verifying signature authentication in under five milliseconds.
did:uiid DOCUMENT SCHEMA
The resolved W3C-compliant DID Document structures public cryptographic access paths cleanly:
{
"@context": ["https://www.w3.org/ns/did/v1"],
"id": "did:uiid:9D1B-5D1D-4C9A-FF21",
"verificationMethod": [{
"id": "did:uiid:9D1B-5D1D-4C9A-FF21#keys-1",
"type": "Ed25519VerificationKey2020",
"controller": "did:uiid:9D1B-5D1D-4C9A-FF21",
"publicKeyMultibase": "z6MkmL6zSj..."
}],
"authentication": ["did:uiid:9D1B-5D1D-4C9A-FF21#keys-1"]
}
GLOBAL SPECIFICATION TRUST
W3C Recommendation
Conforms perfectly to the World Wide Web Consortium's standards for decentralized identifiers.
eIDAS 2.0 Architectural Core
Preconfigured to support the European Self-Sovereign Identity Framework (ESSIF) rules.
NIST FIPS 186-5
Asymmetric signature generations strictly utilize approved mathematical cryptographic algorithms.
FREQUENTLY ASKED QUESTIONS
THE PROTOCOL OF THE FUTURE.
Upgrade to W3C-compliant decentralized identity today with the did:uiid specification.