About · Under the hood
Your identity lives in BetterSign, not on a device. It’s a permanent name with a signed logbook behind it. Anyone can check that logbook, and no company sits in the middle. An organization’s directory is built the same way.
A VLAD (Verifiable Long-lived ADdress) binds a nonce to the CID of a WASM verification function. It commits to a verifier, not a key, and resolves through a Kademlia-style DHT to the head of a hash-linked provenance log. An org directory is the same structure, controlled by a quorum.
Your VLAD stays the same for life, even as the keys behind it change.
The VLAD isn’t derived from a key, so it survives rotation. Key history lives in the log.
Every change is signed and linked, and anyone can verify it, even offline.
Each entry’s proof must satisfy the previous entry’s WASM lock script, from genesis to head.
A shared network address book helps people find you. It never decides who to trust.
The DHT maps VLAD to head CID for discovery only. Validity comes from replaying the log.
Your private keys are sealed in your phone’s secure chip and never leave it.
Non-exportable TEE wrapping: Secure Enclave on iOS, StrongBox/Keystore on Android.
About › How it works
BetterSign in plain words: what a VLAD is, why keys beat passwords, and why changing them is a good thing.
Read →A decentralized PKI in 60 seconds: a stable name, a signed history, and followers who verify it themselves.
Read →VLADs, provenance logs, lock and unlock proofs, and the VLADemlia network, in detail.
Read →How keys are created, rotated, revoked and recovered while the name stays the same.
Read →