Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Create a domain

sithbit domain create <domain> \
  [--authority-keypair <path>] \
  [--keypair <postmaster keypair>] \
  [--payer-keypair <path>] \
  [--skip-preflight]

Creating a domain involves up to three distinct roles:

  • Authority (--authority-keypair) — the mail server’s signing key for this domain: SendMail into a mailbox is only accepted when the transaction signer is the recipient domain’s recorded authority, and the authority collects the operator share of DeleteMail settlement. (Transferring, deactivating, and closing a domain are postmaster operations, not authority ones.)
  • Postmaster (--keypair) — must always sign; only the postmaster can authorize a new domain.
  • Payer (--payer-keypair) — funds the account’s rent; defaults to the postmaster if not given separately.
sithbit domain create sithbit.com --authority-keypair ./authority.json

One key may hold any number of domains: domain accounts are keyed by the domain name alone, so a mail-server deployment that serves several domains registers each of them with the same authority key (its gateway’s DEFAULT_KEYPAIR) and lists them all in [smtp] local_domains. Nothing else changes — the send path checks each recipient’s own domain account, and per-domain DKIM signers keep outbound signatures aligned.

Domain creation charges a fixed protocol fee — see Economics for the exact amount.

Note: a domain operator doesn’t have to ask the postmaster to run this command by hand. See DNS setup and the domain-sithbit service for a self-service flow: prove ownership of a domain via a DNS TXT record, and the service submits this authorization on your behalf.