Identity you own.
Signatures that outlast
quantum computers.
Elabify brings self-sovereign identity to institutions and individuals, secured by NIST-standardised post-quantum cryptography and selective disclosure, anchored on EVM-compatible chains.
Digital identity is broken, and getting more fragile
Today’s identity systems rely on centralised databases, elliptic-curve signatures vulnerable to future quantum computers, and trust hierarchies you didn’t choose.
Elabify replaces this with a stack where you hold your own keys, credentials are presented with selective disclosure (revealing only what you choose to share), and issuer keys live behind a FIPS 140-3-boundary backed by HashiCorp Vault. HSM and zero-knowledge predicate proofs are on the roadmap.
-
1Generate your DID For users, the DID is derived from your own ML-DSA-65 public key. For issuers, it is a project-named handle (`did:elabify:<network>:issuer:<name>`) registered on chain.
-
2Receive credentials Issuers sign claims about you (age, nationality, credit rating, KYC status) with their ML-DSA-65 key. Each claim is committed to a flat RPO-256 Merkle tree; the root is anchored on chain.
-
3Disclose selectively Holders disclose only the claims the verifier asked for, with RPO-256 Merkle inclusion proofs and an ML-DSA signature over a verifier-bound challenge. Undisclosed claims stay private.
-
4Verify in milliseconds An off-chain verifier service checks the signature, the Merkle proofs, and the schema. On chain, a lightweight contract confirms the issuer is registered, the credential is not revoked, and the root is current. Read calls cost no gas.
Claims → flat RPO-256 Merkle root ML-DSA-65 over canonical JSON
Reveals: nationality=AE · Hides: passport #, DOB RPO-256 · ML-DSA challenge sig
On chain: eth_call → isCredentialValid() 9-step check matrix · GRANT / DENY
RevocationRegistry · LightweightVerifier ethers v6 · MetaMask · zero-gas reads
Built for a world
with quantum computers
Every primitive in the Elabify stack was chosen because it survives Shor’s algorithm. These are NIST-finalised standards with audited reference implementations available today, not experiments.
ML-DSA-65
Lattice-based digital signatures. Signs credentials, presentations, and verifier challenges. Replaces ECDSA and Ed25519.
FIPS 204 · NISTML-KEM-768
Key encapsulation for encrypted PII handoff between holder and verifier. Replaces ECDH and RSA-OAEP.
FIPS 203 · NISTRPO-256
STARK-friendly hash over the Goldilocks field. Powers selective-disclosure Merkle trees today; same primitive enables zk-STARK predicate proofs in v2.
Polygon Miden specVault-anchored
Production issuers hold ML-DSA-65 keys in HashiCorp Vault transit (FIPS 140-3 boundary). HSM integration via PKCS#11 is on the roadmap.
Production target“Harvest Now, Decrypt Later” attacks are already happening. Adversaries record today’s encrypted traffic to decrypt once quantum computers arrive. Identity credentials signed with classical ECDSA today will be forgeable by 2030 to 2035. Elabify lets you migrate now, before the deadline, not after.
From individuals to
global institutions
Cross-border KYC
A customer KYC’d by HSBC London proves identity to HSBC Hong Kong with a single selective-disclosure presentation. No re-KYC, no bulk data sharing, instant verification.
Tokenised deposits
On-chain assets gated by verified identity. Holders prove accredited investor status or jurisdiction eligibility; the smart contract sees only the on-chain registration check, not the holder’s underlying claims.
Stablecoin compliance
Issuers gate mint and transfer to wallets holding valid jurisdiction credentials. MiCA and MAS compliance built in at the protocol level.
AI agent authorisation
Autonomous agents carry verifiable credentials proving their operator, authorised scope, and compliance status. Every action is cryptographically attributable.
Academic credentials
Universities issue tamper-proof degree credentials. Employers verify in seconds without calling the institution; the holder chooses which fields to disclose.
Healthcare access
Patients share specific health attributes with providers (vaccination status, prescription authorisation) without exposing their full medical record.
Four steps from issuance to verification
Key generation
Issuer’s PQC keypair is held in a FIPS 140-3 vault. User DIDs are derived from the user’s own ML-DSA public key.
Credential issuance
Issuer signs a credential with their PQC key. Claims are committed via a flat RPO-256 Merkle tree; the root is anchored in the on-chain RevocationRegistry.
Selective disclosure
Holder discloses only the claims the verifier asked for, with RPO-256 Merkle inclusion proofs and an ML-DSA signature over a verifier-bound challenge. Undisclosed claims stay private.
Verification
Off-chain verifier-server validates the signature, the Merkle proofs, and the schema. On chain, LightweightVerifier confirms (issuer registered ∧ not revoked ∧ root current) for free via eth_call.
From Vault to HSM, when you’re ready
Production Elabify deployments today use HashiCorp Vault transit signing for issuer ML-DSA-65 keys, sitting at the FIPS 140-3 boundary. Both major enterprise HSM vendors now ship native post-quantum support; integration via standard PKCS#11 is on the roadmap.
Thales Luna HSM v7.9+
ML-DSA and ML-KEM integrated into firmware. FIPS 140-3 Level 3 certified. Available via standard PKCS#11; planned drop-in replacement for the Vault transit backend.
Entrust nShield v13.8+
NIST CAVP validated for ML-DSA, ML-KEM, and SLH-DSA. FPGA-accelerated signing. FIPS 140-3 Level 3 submission in progress.
The quantum clock
is already ticking
Walk the full flow on real Sepolia in your browser. Elabify works alongside your existing identity infrastructure; no rip-and-replace.