Identity protocol for public ledgers
Identity, verified.
The chain, unchanged.
Blockchain networks prove that keys are valid. They do not prove who owns them. This protocol asks a third-party trust manager — before broadcast — whether the intended participant is who they claim to be.
What to try
Six moves. The chain only hears four of them.
Register once, then run the four counterparties and the Trust Wallet send. Elena and Marcus go through. Jordan can, on the fly. The unknown wallet never reaches the ledger.
01
Register yourself
Open Register. Enter any legal name and a credential of at least six characters. Submit to Meridian National Bank.
Expect: Status becomes verified. Keys stay on this device.
Open console
02
Send to Elena Voss
She is already on file at Meridian. The manager answers from its local database — no federation.
Expect: Verified. Transaction confirms.
Open console
03
Send to Marcus Chen
Meridian has no record. It federates the request to his home manager in Singapore.
Expect: Pacific Trust attests. Then broadcast.
Open console
04
Send to Jordan Hale
Leave on-the-fly on. He was never pre-registered, so the manager collects credentials before answering.
Expect: On-the-fly verification succeeds.
Open console
05
Send to Unknown wallet
No manager knows this key. The wallet still builds the transfer, then refuses to publish it.
Expect: Not verified. Broadcast withheld.
Open console
06
Send from Trust Wallet
Open Wallet, tap Send with Trust Wallet, review the amount, and slide to confirm. Identity is checked before the chain sees anything.
Expect: Slide to send. Same gate, wallet chrome.
Open console
The problem
Keys are authentic. People are not.
A network will not record a double-spend. It will happily record a transfer to a stranger posing as a known counterparty. Public-key cryptography authenticates the signature, not the citizen, the company, or the wallet behind it. That gap is where fraud, sanctions evasion, and stolen-key impersonation live — and where civic ledgers lose the ability to say one person, one vote.
The method
Verify first. Publish second.
01
Pre-register with a trust manager
A bank, government agency, or private notary confirms you are who you claim to be — in person or online against issuing authorities.
02
Construct, then hold
The wallet builds a transaction that still carries a non-verified identifier. Nothing is sent to the chain yet.
03
Ask the trust manager
A verification request is encrypted to the manager’s public key and signed with the initiator’s private key.
04
Broadcast only if attested
If the response is positive, the transaction is released. If not, it is cancelled. The ledger records keys, not names.
Properties
Anonymity on the ledger. Accountability beside it.
Identity off-chain
Trust managers hold the verified-entity database. The chain never learns a legal name, document number, or address.
Signed requests
Every verification request is encrypted and digitally signed, so the manager knows who asked and that the payload was not altered.
Federated managers
If the recipient is not in the local registry, the request is forwarded to a second trust manager that already holds the record.
Ordinary cryptography
Public keys still identify participants on-chain. The protocol adds a gate in front of broadcast — it does not replace the ledger.
Who attests
Banks, agencies, notaries — already in the business of knowing you.
Initial trust is established the way it always has been: a branch visit, a passport, a charter, a query to a motor-vehicle department or a credit bureau. After that, the institution becomes a third-party trust manager for blockchain participants it has already verified.
View the networkChartered institutions
Depository banks already collect identity at account opening.
Public authorities
Agencies verify credentials against the records they themselves issue.
Private notaries
Cross-border trust companies attest when the local manager has no file.
Watch a transfer get stopped — or cleared — before it ever reaches a node.
Register with a trust manager, construct a transaction, and run the verification protocol against a live directory of counterparties. Unverified wallets never land on the ledger.