privacy send

Usage

$ beam --chain payy-testnet privacy send [private-address] <token> <amount>
$ beam --chain payy-testnet privacy send --ephemeral <token> <amount> [--claim-link-message <text>]
$ beam --chain payy-testnet privacy send --memo <bytes32> <private-address> <token> <amount>

Direct send

Send privately to a recipient's private address. The recipient discovers the incoming note via their scanner and can claim it on their next privacy operation.

$ beam --chain payy-testnet privacy send 0xPrivateAddress USDC 1

Claim link

Pass --claim-link-message <text> to generate a shareable claim link instead of (or alongside) targeting a private address. The recipient redeems the link with beam privacy claim.

$ beam --chain payy-testnet privacy send --ephemeral USDC 1 \
  --claim-link-message "invoice 042"

Ephemeral / bearer

--ephemeral produces a self-contained bearer artifact that anyone holding it can claim. Useful for handoffs to people without an existing private address.

The artifact is printed to stdout once and never written to REPL history. Treat it like a one-time secret.

Memo

--memo <bytes32> attaches an arbitrary 32-byte memo to the send. The memo is encrypted along with the note payload, so it is only readable by the recipient.

Flags

• --from <wallet|address|ens> — choose the sender. Must be a wallet in the local keystore.
• --chain <name|id> — must be a privacy-capable chain.
• --format json — emit the submitted hash, operation id, and (when applicable) the claim link / artifact.

Confirmation

Sends confirm the on-chain transaction first. Beam then refreshes both the sender's spent-state and (where applicable) any locally tracked claim links.

Ctrl-C stops the wait without losing the submitted hash.

History scrubbing

Privacy claim artifacts, ephemeral sends, claim-link messages, memos, and private-payment fetch commands are excluded from REPL history. Beam scrubs previously persisted entries on startup as well, including mistyped slash-prefixed variants.