About
BetterSign is a third path: decentralized verification and stable identity, with practical lifecycle discovery, status synchronization, and optional public distribution infrastructure.
About › Why BetterSign
The protocol. This page describes the BetterSign protocol and its open-source core. For what the BetterSign app and products do today, see Products.
Web PKI solves key status lookup with centralized authorities, but that makes trusted third parties part of the failure surface. PGP-style web of trust removes the central authority, but key rotation and revocation propagate slowly and unreliably.
BetterSign combines decentralized trust with efficient lifecycle distribution. Authenticity comes from VLADs, plog history, locks, unlocks and proofs. Distribution can use public infrastructure without making that infrastructure the root of trust.
| PKI and web of trust | BetterSign |
|---|---|
| PKI has efficient status lookup but central authority risk | Stable VLAD identity survives key changes |
| Web of trust is decentralized but weak at status propagation | Plogs publish lifecycle history and current state |
| Both struggle when keys rotate across many relying parties | Peers verify locally instead of trusting distribution servers |
Many systems use a public key as both the identifier and the verifier. That can be elegant for short-lived or ephemeral actors, but it becomes brittle when the identity is supposed to outlive any one key or algorithm.
When identity and key are the same object, normal security hygiene becomes socially and operationally expensive. Rotating an SSH host key can look like a man-in-the-middle attack. Replacing a user login key means updating every authorized_keys file. Migrating from one algorithm to another can feel like abandoning the identity itself.
That pressure causes keys to live longer than they should. Operators avoid rotation because the cost is not just cryptographic. It is distribution, audit continuity, access control, monitoring, policy enforcement and human recognition, all tangled around one public-key value.
BetterSign breaks that coupling. The VLAD is the durable identity, while keys and algorithms are current state inside a verifiable provenance log. A key can be replaced, revoked, recovered, delegated or upgraded without forcing relying parties to learn a new identity.
The identity persists while cryptographic material evolves.
| Routine rotation | Keys can change because rotation is a signed state update, not an identity replacement. |
| Recovery without reset | A higher-priority recovery authority can repair compromised operational keys under the same VLAD. |
| Algorithm agility | Identities can move from classical to post-quantum or hybrid algorithms without changing names. |
| Audit continuity | Logs, policy, access decisions and monitoring remain tied to the stable identity. |
| Operational automation | Watchers can update SSH, TLS, WireGuard and service config from verified state. |
| Human continuity | Relationships, aliases, permissions and trust decisions survive key replacement. |
| Key as identifier | VLAD as identity |
|---|---|
| Rotation changes the apparent identity | Keys are replaceable verified state |
| Algorithm migration breaks existing bindings | Algorithms can evolve under one stable address |
| Recovery often depends on out-of-band reset | Recovery is part of the signed lifecycle policy |
| Audit trails must stitch old and new keys together | Audit and authorization stay attached to one identity |
BetterSign treats key changes as normal identity activity, not as exceptional maintenance. Creation, rotation, revocation, recovery, delegation and algorithm migration are signed lifecycle events in the provenance log.
That changes the operational posture. A strong system should expect keys to age, move, fail and be replaced. The relying party should not have to guess whether a changed key is a breach, a renewal, a recovery action or a planned algorithm upgrade.
Because lifecycle events are part of the same verifiable history as the identity itself, followers can see what changed, who authorized it, which policy accepted it, and what state is current now.
The practical result is that key changes can become routine. Organizations can shorten key lifetimes, rotate aggressively, adopt post-quantum or hybrid algorithms, and recover from exposure without forcing identity resets or manual redistribution.
| Traditional key change | BetterSign lifecycle |
|---|---|
| Often handled as an outage or manual migration | Handled as a signed state transition |
| Requires broadcast through separate channels | Distributed through normal plog synchronization |
| Leaves relying parties to reconcile old and new keys | Preserves provenance and current authority |
| Discourages frequent rotation | Makes key changes safe enough to be routine |
Key management is a business problem of trust, complexity and fragility. Organizations need strong cryptographic control, but expired certificates, unclear key ownership, brittle renewal processes and CA incidents can create outages and emergency remediation work.
BetterSign reduces that fragility by making lifecycle changes routine, verifiable events. Rotation, revocation and recovery are not exceptional manual projects. They are part of the identity state machine.
Key changes should be normal operating procedure. A healthy system expects keys to age, move, fail and be replaced, then gives relying parties a provable way to follow those changes.
| Trust | Avoid depending on one external institution as the root of key truth. |
| Complexity | Reduce manual certificate and key distribution workflows. |
| Fragility | Make expiration, rotation and recovery normal verified operations. |
| Ownership | Tie lifecycle control to explicit VLAD and plog authority. |
DIDs, blockchain PKI and identity-based encryption (IBE) all address parts of the same problem, but each introduces tradeoffs. DIDs can improve user control, but DID documents still need key update broadcast, distribution and relying-party synchronization. Many DID methods do not provide a built-in, provable provenance log for every key lifecycle event, so rotation and recovery history can become method-specific or external to the identifier.
Blockchain PKI adds transparency but can introduce cost, latency and ecosystem constraints. IBE simplifies public-key lookup but depends on a key generation center.
BetterSign focuses on stable identity, verifiable lifecycle history, flexible distribution and local verification. It can integrate with existing identity systems when introduction or real-world verification is needed, without requiring that system to become the universal root of cryptographic truth.
| Other approaches | BetterSign focus |
|---|---|
| DIDs still need key update broadcast, distribution, synchronization and provenance policy | Decouple identity from current key material |
| Blockchain PKI carries ledger-specific costs and delays | Publish lifecycle events as verifiable plog history |
| IBE reintroduces a trusted key generation center | Use public services for discovery without trusting them |
Certificate lifespans are getting shorter, which increases the cost of manual certificate lifecycle management. More frequent renewal means more opportunities for outages if rotation remains a brittle operational task.
BetterSign is designed around frequent, verified lifecycle changes. The same pattern that handles a key rotation can also drive watchers for TLS material, service identity, SSH access and other local integrations.
BetterSign supports multiple distribution mechanisms and storage options. Operators can use public services for reachability, local daemons for automation, and stronger custody for higher-priority keys.
The flexibility does not weaken the trust model, because fetched data remains untrusted until local verification succeeds.
| Problem | Trust, complexity and fragility |
| Approach | Decentralized verification with practical distribution |
| Outcome | Routine key lifecycle automation |