What is verified digital identity?
It's the difference between a name tag someone hands you at the door and a passport you walked in with.
Right now, almost every "verified" badge you see online is a name tag. A platform looked at your account, decided you're legitimate, and pinned a little symbol next to your handle. The day the platform changes its mind — or gets hacked, or sold, or shut down — the badge goes with it.
Verified digital identity flips that. You hold the key. The platform's job is just to display the proof.
The two pieces
It only takes two things to have an identity you actually own:
- A domain you control. Like
born.engineer. The domain is your name on the open internet — your address, your stationery, your signature line. - A cryptographic key stored at that domain. Anyone in the world can fetch your public key in a single HTTP request, and use it to verify anything you've signed.
did:web:born.engineer — read as "the identity that lives on the web at born.engineer". It resolves to a file at /.well-known/did.json containing the public key.What you can prove with it
- That a post on LinkedIn really came from you, word-for-word.
- That a recommendation a colleague wrote about you wasn't fabricated by someone else.
- That the CV a recruiter is reading hasn't been edited since you published it.
- That an email sent from
you@born.engineeris genuinely from you.
What changes for you
Honestly, for the first few months — nothing visible. You'll keep posting, keep accepting endorsements, keep being yourself. What's different is the receipt: every public thing you do is silently stamped, and anyone who cares can check.
The first time it matters is the first time someone tries to impersonate you. Or the first time a recruiter doesn't have to call a former boss because the signed recommendation is right there. Or the first time a journalist quotes something you "said" and you can prove instantly that you didn't.