Overview

Beam supports private transfers on privacy-capable EVM chains using local ZK proofs and the Payy-EVM privacy protocol.

Beam's privacy support is built on the Payy-EVM privacy protocol. Each privacy-capable chain ships with (or accepts) a privacy profile that pins the bridge contract, prover settings, and supported tokens.

Identity

Beam derives every wallet's privacy key from its EVM key using a canonical domain-separated rule (keccak256("payy/grumpkin/v1" || evm_key_bytes)). You don't manage two separate keys — the EVM keystore IS the privacy identity.

Inspect your derived private address:

$ beam privacy address
0x...

What you can do

Mint into the privacy pool from a public ERC20 balance.
Send privately to another private address.
Burn back to a public EVM recipient.
Create claim links for bearer-style sends.
Watch incoming transfers and claim them.

Proofs

Proofs are generated locally. Public release binaries ship with the Barretenberg bindings backend, so privacy operations work without any extra installation. Local development builds default to the bb CLI backend.