One current name
One nickname per wallet in this namespace.
A project-local namespace
Choose an available lowercase name for your wallet.
Replace it when it no longer fits.
One nickname per wallet in this namespace.
3–24 letters, digits or underscores.
A held name cannot be claimed by another wallet.
Replacing your name releases the old one.
Local Demo · No public contract deployed
A little easier to recognize
Give your wallet a readable nickname inside Nyvora. It belongs to this contract's namespace — not the whole internet.
orbit_7
One current nickname
for its connected wallet.

A small, clear change
The transaction updates your current nickname and its holder lookup together. There is no administrator choosing a name on your behalf.
Your current name
Your new name. The previous one is free again.
Not an ENS name, internet domain, global identity or proof of a person.
The caller changes only its own nickname. Another wallet cannot replace yours.
Only lowercase ASCII letters, digits and underscore. No automatic normalization.
No bigger promise than the design
Holding a nickname says which wallet currently holds that string here. It does not verify a person's identity, reputation or rights elsewhere.
The contract is tested locally but not deployed. Onchain reads and writes are unavailable in this Demo.
Explore the name pageThe Nyvora design paper
Read how a name is held, how a replacement releases it and what a successful event does — and does not — prove.
Read the whitepaper
Project-local nickname namespace
Public by design. Limited by design.
Before you choose
No. It is only a nickname held by a wallet in this particular contract. It has no ENS resolution, global identity, person verification or rights in other projects.
Yes. A successful replacement updates your nickname and holder lookup and releases the old string. Another wallet may then claim the released name.
A name held by another wallet is rejected by the contract. A pre-submit availability read is not a reservation; availability can change while a wallet request is pending.
The separate name page offers a clearly marked tab-memory practice. It is not shared, not onchain and not saved. Real onchain changes stay disabled until a verified deployment is separately authorized.
Make it readable.
Try the local practice. No wallet needed for it.
Choose your name