Register a handle
Names are validated and canonicalized under the registry’s policy. Registration records the owner and the applicable lease conditions.
A handle for the signer
Make an identity easy to recognize.
Bind an @-handle to a Sigil identity and give wallets, explorers, and applications a readable way to identify participants.
UsernamesIllustrated study
Signer → signature → record
Identity establishes attribution. Trust needs context.
01 / Built for a purpose
Keep the identifier. Improve the interface.
A cryptographic identity does not need to be the text a person copies into every form. Usernames give applications a human-readable layer while retaining a verifiable binding to the underlying DID.
Resolve in both directions
Look up the owner of a handle or retrieve a DID’s selected reverse handle. Wallets can display a recognizable participant alongside the identity they are using.
Manage the lifecycle
Owners can transfer, release, and update supported metadata. Reverse records are kept consistent with ownership changes.
Premium auctions with anti-snipe rules
Premium usernames use their own bidding and finalization policy. Anti-snipe behavior and minimum increments keep the auction lifecycle explicit.
A configured dispute process
Where enabled, bonded disputes can lock a handle for resolution by configured signers. A readable name still needs a procedure for contested ownership.
The details matterGood questions.
Good questions.
Clear answers.
Does a handle prove a person’s real-world identity?
No. It binds a registered name to a DID. Any additional identity or organizational claims need their own verification.
Can my application trust the displayed name alone?
Resolve and verify the underlying identity, especially before signing or sending funds. The readable label should help the user recognize the destination without replacing the destination check.
Keep exploringOne capability.