How Liir names things

One mark. Different kinds of address.

Some names are chosen. Some are generated. Some belong to one relationship, one place, or one moment. Liir keeps each kind in its own namespace so a person, an agent, a private path, and a live interaction can never be mistaken for one another.

Name explorerNamed realm
Liir name

iamamassivedork1234@liir.net

A chosen name for a person, business, institution, or government body. Private, not secret: knowing it lets no one in.

2Visual match
Shown to people, never used as the capability.
Created byThe owner
Visible toIts owner · others see nameplates and doors
LifetimeStable

The public map

Six spaces. Six different promises.

The shape can still be a Liirlit. The namespace tells the decoder what the mark is allowed to mean, who may create it, and how long it can remain valid.

01 · Liir names

A chosen name, kept private

iamamassivedork1234@liir.net

People, businesses, institutions, and government bodies choose a globally unique name at liir.net. It is private, not secret: it isn’t a password, so knowing it lets no one in, and Liir never prints it where someone else can see it. People are handed nameplates and doors instead.

Maximum 28 characters: a-z, 0-9, period, underscore, and hyphen.
02 · Agents

Named as an agent

mara@liir.tv

An agent is visibly an agent before it speaks or acts. It cannot occupy the namespace used by a person or organization.

The liir.tv domain carries the agent class.
03 · Pairwise

Generated for one relationship

giant-kitty-cat-00000@liir.net

Mutual Greet creates a private name in each direction. The words make it recognizable; the relationship capability makes it work.

Three generated words plus five digits. The exact grammar is reserved from public registration.
04 · Nameplates

A name you wear in public

anamegoeshere-0000

A vanity nameplate is the name people see on your letters, worn over your private doors. It is not an email address and not a person’s underlying authority: inside Liir, a letter to it travels over a door its sender already holds with the owner.

Up to 16 lowercase letters, one hyphen, and a four-digit count.
05 · Surfaces

A stable authorized place

First Bank · Teller 2

A teller desk, manager office, ATM, or website surface stays recognizable while operators, sessions, and keys change beneath it.

Authorized by an organization. Labeled for humans, identified cryptographically.
06 · Interactions

A capability for right now

No public address

A browser tab, Greet session, request, or scan receives a random temporary Liirlit. Nobody types it and nobody keeps it as a name.

128-bit random capability. Matching number shown separately. Expires after use or time.
Why reserve the pairwise pattern? Because pairwise names and chosen Liir names both end in @liir.net. Public registration never issues the exact three-word-plus-five-digit grammar, so typed addresses remain unambiguous.

What happens when you scan

A personal Liirlit or stable organizational surface can be shown again and again. Each scan creates a fresh encounter beneath it. Mutual acceptance then creates new pairwise names and capabilities for that relationship.

On the web, the stable website surface authorizes a unique Interaction Liirlit for each browser tab. Only that tab spins. The bank remains the counterparty, and the temporary mark disappears when the interaction is complete.

First Bank · Online BankingReady
1
Stable surfaceOnline Banking remains the same
Ready
2
Browser interactionFresh mark for this tab
Waiting
3
Visual confirmationChoose the number shown on the phone
Waiting
4
Bank relationshipReturn through the private pairwise path
Waiting
Surface: stable · interaction: fresh · relationship: private

For builders

Human names and machine capabilities never share an interpretation.

The traditional three-ring Liirlit has enough room to carry a namespace header without reducing user input.

Realm 0

Named things

Addresses and labels people can recognize, choose, copy, or type.

Liir name@liir.net
Agent@liir.tv
Pairwise namerelationship scoped
Vanity nameplateworn over doors
Realm 1

Capability things

Cryptographic objects that software resolves and people never need to type.

Stable surfaceorganization scoped
Interaction128-bit random
Formatversioned
Interpretationtype bound
Exact three-ring allocation

The Interaction realm occupies 4028 numeric values, approximately 7.206 × 1044. A structured interaction uses 4 version bits, 6 type bits, 2 flag bits, and a 128-bit random capability.

realm 1 | version 4 | type 6 | flags 2 | capability 128

That is 140 structured bits inside a roughly 149-bit realm. Every version, type, and flag combination retains the complete 2128 capability space. The matching number is presentation state and is not part of the cryptographic identifier.

A nameplate can be remembered. A pairwise name can be trusted inside one relationship. A surface can stay put. An interaction can safely disappear.

See how Liir works