Proof of Identity: We Did Not Invent the Term, and It Is Not How This Chain Reaches Agreement

The claim this page was supposed to make

It was planned as an explanation of the one term we invented.

We did not invent it. A public code search for the hyphenated phrase returns seventy-seven repositories, the oldest visible one dating to 2016, in this same field. The phrase was in circulation roughly a decade before this project existed.

What that establishes and what it does not. It establishes prior public use. It does not establish who coined it, and we are not going to award that to anybody, including ourselves.

The page keeps its address, because somebody searching that phrase deserves the true answer rather than a missing page.

And the second half is wrong too

The phrase appears in our own keyword material beside the word "consensus".

Identity is not a consensus mechanism on this chain. A search of the consensus crate for identity or identifier vocabulary returns nothing outside a struct name and test code.

CONTROL: the same search over the execution crate matches six files. So the searcher finds that vocabulary where it exists, and its absence from the agreement path is real.

Agreement here is reached the ordinary way: a leader proposes, a quorum certifies, and a block is committed two rounds later. Nothing in that path consults an identity, a credential or an identifier.

What the phrase does honestly describe

Identity is what this chain is FOR, not how it agrees.

Creating an identifier, updating it, recovering it, issuing a credential and revoking one are transaction types, handled at the execution layer like any other operation. And they are the ones the fee schedule exempts, for a reason the code states: an identifier anchor is value-free by construction.

So a defensible reading of the phrase is "a chain whose payload is identity". An indefensible one is "a chain that reaches consensus by checking who you are", and the second is what the word "consensus" beside it invites.

Why this matters more than a naming quibble

A consensus mechanism is a Sybil-resistance story. Naming one is a claim about what stops a stranger from spinning up a thousand participants.

On this chain, that answer is not identity and it is not economics. The four validators producing blocks report no stake and arrived from genesis. What limits participation today is that one operator controls the set.

That is an ordinary and honest answer for a development network, and it is a completely different answer from the one the phrase implies.

What is actually true and worth saying

The identifier method is registered in the W3C DID Method Registry, which is a listing and is checkable in one request.

Identity operations are first-class transaction types with their own handlers, their own fee treatment and their own on-chain records.

And the chain does anchor real identifiers, which you can resolve yourself.