Skip to content

Identity

Your identity in Kunuleco belongs to you. It is cryptographic, self-sovereign, and cannot be revoked by anyone else.

Why this matters

On most platforms, "your account" is not really yours. The platform can suspend it, reset it, rename it, mine it, or vanish with it. A Kunuleco identity is a keypair on your own machine, protected by a password only you know. There is no authority to appeal to, which also means no authority can take it away.

The three layers

Layer Example Purpose
Cryptographic root did:key:z6Mk… Permanent, unforgeable anchor: an Ed25519 key
Name#Discriminator Mira#472913 Human-friendly. The number is derived from your key, so you cannot pick it. Once your node has seen a name paired with a key, it refuses that name under any other key
Short / intro code tiger-castle-7 A speakable code for first contact and invites

Names can change; the key cannot. Across the social layer your canonical key is written as a DID (like did:key:z6Mk…) and treated as the single source of truth about who someone is. Petnames, friendships, and grants all anchor to it.

The documents you will see named

  • AIRO: your private credential blob, encrypted on disk. This is "your identity".
  • PIRO: your public, shareable identity document: how peers learn to reach you across transports.
  • NIRO: the node's own identity.

Key events

Kunuleco keeps a KERI-style append-only event log on your node. Each event commits in advance to the next event key, so the chain cannot be forked by someone who steals the current one, and your own node replays the chain at login. What that log covers today is your session keys, not the root key behind your did:key. The root does not rotate yet, and sharing the event history with peers so they can verify it themselves is not built yet either. Until root rotation lands (it is on the roadmap), treat your identity backup the way you would treat a wallet seed phrase. If it leaks, the fix is a new identity, not a rotation.

No resets, real backups

There is no password reset, by design. You can change your password while logged in, but you cannot recover one you have lost. Your safety net is an encrypted export:

export-identity ~/kunuleco-backup.kuneid <base64_passphrase>
import-identity ~/kunuleco-backup.kuneid <base64_passphrase> --overwrite

After an import, restart and log in with that identity's username and password.

The export is also how you move to a new machine. It carries your identity, not your world. History, grants, and boards are rebuilt as you reconnect to peers. Anyone with the file and the passphrase holds your identity, so store both like keys, separately if you can.