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 k51qzi5uqu5dg… Permanent, unforgeable anchor: an Ed25519 key
Name#Discriminator Mira#7291 Human-friendly. The number is derived from your key, so no one can squat Mira#7291
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 rotation

Kunuleco uses KERI-style key rotation: each key event commits in advance to your next key and is recorded in an append-only chain. If a key is ever compromised, you rotate to the pre-committed next key without losing your identity, and the event history shows exactly when the change happened.

No resets, real backups

There is no password reset, by design. Your safety net is an encrypted export:

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

The export is also how you move to a new machine. Anyone with the file and the passphrase holds your identity, so store both like keys, separately if you can.