The checker makes only the availability conclusion returned by the registry.
KYKY Names / signed records
A readable name.A signed record.
An active KYKY name resolves to a public, controller-signed record. The profile checks that signature against the controller named in the same record and states the limits beside the result.
Every name points to a controller-signed record. Public profiles are server-checked and readable without an app.
Three to twenty characters. Start with a letter; use lowercase letters, numbers, and single underscores.
01
From handle to public record
The client creates the canonical record and signs it with the controller key.
The signed record and the controller named inside it are returned together.
Supported fields render only after the record/controller signature match passes.
The signed object
Readable fields.
Narrow conclusion.
Changing a canonical signed value makes the controller-signature check fail. Public V1 profiles withhold address types whose exact case is not safely authenticated.
KYKY-NAME-RECORD-V1
name@maya
controller0x7a31…91c0 · neutral demo key
addreip155:* · one address, every EVM network
web rulecase-sensitive V1 destinations withheld
sequence000004
updatedcontroller-signed field
DEMO RECORD · CONTROLLER SIGNATURE CHECK REQUIRED
The canonical record format with neutral demonstration data. No user address is shown.
02
The public profile
DEMO RECORD / PASS-STATE PREVIEW
Maya Chen
@maya · Personal
A valid controller signature renders this state
Resolve an EVM name
For a supported EVM network, open KYKY and resolve @maya.
The wallet shows the destination published for that network.
Receives on
All EVM networks · 0x7a31…91c0
Case-sensitive V1 destinations · withheld on web
Illustrative profile data, not a live @maya record. The production renderer checks the record against its named controller and ships zero client JavaScript.
Checked before display
Public by design.
Scoped on purpose.
The delivered page runs zero client JavaScript. A valid signature establishes a match to the controller named in that record; it does not establish a real-world person, organization, handle history, or payment purpose.
THE CHECK ESTABLISHES
Record ↔ named controller
The renderer checks that the displayed canonical record was signed by the controller named inside that record.
THE CHECK DOES NOT ESTABLISH
Person, history, or purpose
It does not independently prove a real person, organization, handle history, payment purpose, or that a recipient is safe.
Supported EVM resolution
Choose the network.
Then inspect the record.
For supported EVM networks, KYKY pairs the selected network with the destination published in the record. Do not rely on V1 names for case-sensitive destination types.
DEMO RECORD / RESOLUTION PREVIEW
Resolve @maya
Network chosen.
Record checked.
Record checked.
Illustrative resolution with neutral data, not a live record or payment request. Case-sensitive V1 destinations are withheld on the web.
Continue through KYKY
Start with the name.
Check availability, understand the record, and continue through an official KYKY client.
Every name points to a controller-signed record. Public profiles are server-checked and readable without an app.
Three to twenty characters. Start with a letter; use lowercase letters, numbers, and single underscores.