Getting mail

sithbit mail get [to_address] \
  [--message-id <id>]... \
  [--range] \
  [--directory <path>] \
  [--keypair <path>] \
  [--delegated-key-path <path>] \
  [--gateway <url>]

to_address defaults to your own address. --message-id can be repeated to fetch specific message ids; --range instead treats the given ids (or all known ids, if none given) as a range. --directory writes fetched messages to a directory instead of printing them.

The on-chain listing for each message shows a From-hash: line — the chain stores only the blake3 hash of the from address, never the string. The readable From:/Subject: headers appear once the sealed body is fetched and decrypted (they live inside it).

Note: the decryption flags below (--keypair, --delegated-key-path) require the CLI’s rand feature (enabled by default).

There are two ways to supply the key that decrypts a fetched message:

• --keypair — a Solana wallet keypair file (the default: your own configured wallet decrypts mail sealed straight to it).
• --delegated-key-path — a delegated X25519 key file, for mail sealed to a delegated key instead of your wallet directly.

If you’ve already fetched a message but need to decrypt it separately, use sithbit mail decrypt <file> with the same key flags as a standalone step.