Decentralized identity is a way to identify yourself and prove things about yourself without depending entirely on one central account provider.

Instead of every interaction relying on “Google says this is you” or “this website owns your account,” you control cryptographic keys that let you prove control of an identity. Other parties can issue signed credentials about you, which you can present when needed.

Definition

Decentralized identity is an approach where control over who you are — what can be proven about you, and who is allowed to read it — does not depend on a single party’s willingness to issue, store, or revoke that control.

In a centralized model, one party plays two roles at once: it stores your identity data, and it decides who gets to read or verify it. Those two roles being the same party is the actual thing “decentralized” is trying to remove — not the data’s physical location, the coupling between storage and permission.

What Is Decentralized Identity?

Three things remain distinct:

Identity: Which key or identity do you control?

In .me, your identity grows locally from a SEED — pure, sovereign math that doesn’t require servers, network calls, or central providers.

SEED - .me

Credentials: What has someone attested about you?

Third parties can issue signed assertions bound to your public identity fingerprint (identityHash), which you carry with you across contexts.

// 1. Instantiate your local identity from the SEED
const user = Me(SEED);

// 2. Third parties sign claims directly into your identity namespace
user.credentials.degree(issuer.sign("Degree: CS"));

// 3. Resolve the credential in any context
user("credentials.degree");

In .me, state writes use function calls — path(value)—instead of JS assignments (=).

Because the underlying Proxy lacks a set trap, using = bypasses the kernel completely. This skips hash-chain logging and prevents upper monad layers from triggering reactive updates.

O(k) Semantic Kernel Architecture

Authorization: What does this service allow you to do?

Rather than relying on a platform’s permissions table, authorization in .me uses an algebra of encrypted audiences (such as secret-scoped _ paths). The cryptographic structure of the data itself determines who gets to read or execute it.

The Algebra of Encrypted Audiences

For example, you could prove membership in an organization to an application. The application verifies that credential and decides whether it grants access.

“Decentralized” does not automatically mean blockchain, anonymity, or no servers. Recovery, revocation, storage, and trust still need mechanisms.

For .me, the relevant idea is: your identity remains yours while you enter different contexts; each context determines your permissions there.

Underneath, this identity doesn’t live on a server or a blockchain network — it grows locally from a single SEED. Whether it’s generated randomly or derived from two strings you remember (who + secret), your identity is pure math: portable, sovereign, and entirely under your control before it ever touches a network.

.me

What Is Decentralized Identity? was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.