Verification

What a verified badge means

A verified badge on this registry means the operator has independently confirmed that a handle's owner is the person, business, or institution the name suggests. It does not vouch for the content those owners publish.

In the data model, verification is a single nullable verified_at timestamp on the handle row. It is set by an admin holding the handles.verify permission and is logged to the public audit trail.

Who can get one

We verify handles when all of the following are true:

1. The handle clearly refers to a real-world identity (an individual with a public profile, a registered business, a named institution).
2. There is a strong likelihood that someone might impersonate the handle's owner if the binding were ambiguous.
3. The owner can demonstrate control of the real-world identity. The simplest evidence is a signed message posted under the controlled identity's existing public channel (a Twitter/X account with a blue check, a corporate domain that hosts a /.well-known/tpsocial file, etc.).

We do not verify based on follower count, content volume, "importance," or payment. There is no purchasable tier.

What we revoke for

Verification is not permanent. We will revoke a badge when:

• The handle changes hands.
• The owner asks us to (no questions asked).
• We become aware that the verification was issued in error.
• The handle is used to impersonate or defame the very identity it was verified for.

Revocations are logged to the audit trail just like grants.

How to apply

Verification is not open for applications in the website. The registry operators add a badge by hand. To ask for one, write to the contact address on the About page from a channel that already shows control of the real-world identity.

Self-serve verification is not built. It would need at least one of:

• DNS-record proof of domain control.
• A signed reply on an existing verified identity elsewhere.

What a badge looks like

In the UI, a verified handle shows a small badge next to its name on the public profile and on every page rendered under it. Clients can detect verification from the attestation_wire payload, which includes a verified_at field set by the registry. There is no public audit endpoint for verification.