Logos Kit

Accounts

Public and private accounts, what each one reveals, and how apps see them.

A Logos Kit wallet holds any number of accounts on a zone, all derived from one recovery phrase. There are two kinds.

PublicPrivate
Balance and historyVisible to everyone on chainOnly the owner (and the wallet) can see them
SendingSigned and submitted by the wallet in secondsProved on the user's machine first: minutes, not seconds
Id an app seesThe account id (base58)An opaque per-app handle, pvt_…, never the account itself
Good forPosting testimonials, program authors, feesHolding and moving value privately
Public and private accounts in the wallet
Public and private accounts side by side. Private ones carry a lock.

Moving between them

Transfers pick their route from the two accounts:

From → toRouteProof
public → publicpublic transferno
public → your privateshieldyes
your private → publicdeshieldyes
private → privateprivate transferyes

Paying someone else's private account needs their public keys (a nullifier key and a viewing key). The wallet can export them as a small keys file that holds no secret: logos-kit account keys <account>.

What apps see

An app only ever sees the accounts the user chose to share in the connect sheet. Private accounts need an extra, explicit tick; the app then receives a pvt_… handle that means nothing to anyone else, including other apps.

kit.api.connect({ accountKinds: ["public", "private"] }).then(function (s) {
    s.accounts.forEach(function (a) {
        console.log(a.kind, a.address)   // "public" 9Qf…  /  "private" pvt_…
    })
})

Reads (getWalletBalance) and proposals (transfer, sendCall) accept the handle. The wallet resolves it, checks the app's grant, and answers.

Labels, restore and backup

  • Labels are yours: logos-kit account label <account> "Savings", or rename in the wallet. They are stored in LEZ's own label map, so the official CLI sees them too.
  • Restore from the recovery phrase finds your used accounts again. A "first used around" date skips older blocks and makes the first sync much faster.
  • Backups are encrypted files (logos-kit backup export <file>); they need the password they were made with.

See Security model for how keys are stored.

On this page