Skip to content
nokto/docsGitHub (opens in a new tab)

Accounts

An account is a receiving account: a person's own payout account, a rideshare or delivery platform's payout record, a marketplace seller account, or an agent earning on someone's behalf. Nothing in the protocol branches on which — an agent account composes into its owner exactly as a job composes into a person.

An account has:

  • a holder type — person, company, or agent
  • a subject binding — proof of control over the secret behind the account's identity
  • a vault position — the account's claim on custodied shielded value
  • an income log — a running Merkle log of committed income events
  • a committed aggregate — a running total, tier, and period, committed rather than stored in the clear

The holder is whoever controls the account's secret. A person, a company, or an agent — the protocol does not branch on which.

Identity is derived, never claimed

An account's identity is a domain-separated hash of a witness-held secret, never ownPublicKey() — that value is prover-claimed and unbound to the signer, so any caller could supply whatever a check expects if authorization depended on it. This is why a claim like "record this income against my account" or "create this composition" can only ever be made about the account whose secret the caller actually holds — the discipline INV-8 states as a requirement.

Subject binding is interim, by design

Today, every account's subject binding uses the self-asserted binding scheme: a holder proves control of a key and declares their own holder type. That is a proof of key control and nothing more — it does not establish that the holder is a person, a company, or the actual operator of a given agent.

Midnight Passport is reserved as a second, stronger binding scheme, but is not implemented. The binding scheme is tracked as data on the account rather than assumed by the contracts, specifically so that when Passport ships it becomes a new scheme alongside self-asserted binding, not a rewrite of everything that depends on a subject id. A subject id is derived from the holder's own secret, never issued by the binding scheme, which is what makes a later re-binding possible without disturbing anything that references the account.

Binding schemes and assurance tiers are two different strength orderings, and they run in opposite directions:

  • Assurance tiers: lower is stronger — see Assurance tiers.
  • Binding schemes: higher is stronger — self-asserted is 1, Midnight Passport (reserved) is 2.

An account's income does not stand alone once it starts composing into other accounts — see Composition.