The private execution layer
A wallet-native architecture for confidential value transfer on public infrastructure.
Protocol behavior is proposed. This release is an interface preview; no funds or wallet signatures are accepted.
A different default
A public address is a persistent financial identifier. Its balances, counterparties, and payment history can be indexed and correlated. Jammer explores a different model: publicly verifiable settlement with privately held transaction state.
The proposed protocol puts a privacy-aware RPC between an existing EVM wallet and a shielded pool. Users authorize familiar transactions; the privacy layer constructs proofs and manages encrypted notes. The wallet remains the authority for spending.
Design principles
| Principle | Intended behavior |
|---|---|
| Wallet continuity | Keep the existing address, signer, and seed backup. |
| Private state | Represent value with commitments and encrypted notes. |
| Verifiable execution | Enforce authorization and conservation of value in proofs. |
| Selective visibility | Separate viewing permissions from spending authority. |
| Explicit trust boundaries | Document the role of the RPC, relayer, guard, and upgrades. |
Current release
This is a product and protocol-design preview. The website, documentation, and invite-code gate are functional. No Jammer pool, proof system, wallet connection, RPC service, or asset transfer is deployed through this interface.
All protocol behavior described here is a proposed design unless a page explicitly states otherwise. Network support, performance, audit status, and deployment addresses require implementation and independent verification before use.
Reading paths
- Users: Getting started → Shield & unshield → Private transfers.
- Engineers: System architecture → Keys & authorization → Notes & nullifiers → Wallet RPC.
- Reviewers: Security & trust → Selective disclosure → Release scope.