BetterSign™.

BetterSign™

Prove it's really you — forever.

A cryptographically verifiable history of control.

Every change to your identity is cryptographically signed and linked, so your whole history is verifiable by anyone, any time — even offline.

Provenance logs are hash-linked entries, each authorized by the previous entry's lock script. The chain binds the VLAD at both the genesis and head entries for closed-loop verification.

  • A record of who you are that can't be faked
  • Anyone can check it, no permission needed
  • Impersonators and deepfakes don't hold up
  • seqno + prev + lipmaa links form the chain
  • each proof satisfies the prior entry's lock script
  • self-verifying from genesis to head

A stable name on the outside, freely changeable keys on the inside.

The picture

A logbook anyone can replay

Underneath your VLAD sits a tamper-proof logbook that records every key you've ever used. Anyone can replay it page by page, confirm each one is legitimate, and end up with your current, correct keys — without asking anyone for permission.

The provenance log is a hash-linked chain (seqno + prev + lipmaa). Each entry's proof must satisfy the previous entry's WACC lock script, and the VLAD is cryptographically bound at both genesis and head.

What it fixes

A name anyone can check, anytime

Ordinary identifiers

  • ✕Owned by a company that can revoke or redirect it
  • ✕Proven only when a middleman vouches for you
  • ✕Can be impersonated if the provider is fooled
  • ✕Stops working if the service disappears

A VLAD

  • ✓Owned by you and no one else
  • ✓Proven by math that anyone can check
  • ✓Cannot be forged without breaking the cryptography
  • ✓Still verifiable years later, even offline

How it works

How a VLAD works

You create an identity, which gives you a VLAD — your permanent name

BetterSign starts a signed logbook for it

Every key change adds a new signed page to the logbook

Anyone can replay the logbook and check every page is legitimate

They always end up with your current, correct keys — without asking anyone

The building blocks

Four ideas do all the work

◇

Stable identity

A VLAD remains stable while its keys and protected metadata rotate.

⛓

Self-verifying history

Every state transition is hash-linked and authorized by the previous log state.

⇋

Decentralized discovery

VLADemlia helps peers locate current records without becoming the trust root.

↻

Routine rotation

Key changes become signed updates that followers can verify and apply.

The jargon, translated

Plain-English words for the deep stuff

VLAD
your permanent name; short for Verifiable Long-lived Address
plog
the signed logbook behind a VLAD that records every change
rotation
swapping an old key for a fresh one without changing your identity
revocation
marking a key as no longer usable, for example after it leaks
recovery
using a stronger backup key to fix things if a normal key is lost
VLADemlia
the network address book that helps peers find each other; it never decides who to trust

Questions

The things people ask first

Do I need to understand the cryptography?

No. Point your tools at a VLAD and BetterSign keeps the keys current for you — SSH that doesn't break when keys rotate, TLS that renews itself, API tokens you can rotate freely.

What if I lose my key?

Recovery is built in. A stronger, better-protected backup key can fix things if a normal key is lost or stolen — no out-of-band scramble.

Why is changing keys a good thing?

The longer a single key stays in use, the more chances a copy ends up somewhere it shouldn't. Rotating retires old risk — like changing the locks now and then.

Can a company take my identity away?

No. A VLAD is owned by you and no one else, proven by math anyone can check, and still verifiable years later — even offline.

A name you keep. Keys you can change.

Point your tools at a VLAD and BetterSign keeps the keys current for you.