Security Overview

Privacy Pump uses several security layers. No layer removes the need to review wallet requests and protect signing devices.

Wallet security

Wallet signatures authorize user actions. Protect recovery phrases and signing devices, verify the connected wallet, and read each approval request before signing.

Private Multisig security

A Private Multisig requires its configured threshold before an action can execute.

Create a proposal
  |
  v
Members review it
  |
  v
Collect the required approvals
  |
  v
Verify and execute the approved payload

A threshold reduces dependence on one signer, but it does not protect against enough authorized signers approving a harmful action.

Privacy infrastructure

Privacy-focused routing, the ZK Pool, hidden signer authorization, and confidential-computation paths are designed to reduce unnecessary public exposure. Public blockchains still reveal some activity, and Privacy Pump does not promise complete anonymity.

Communication

Vault chat keeps coordination inside the access-controlled vault experience. Messages do not authorize transactions, and members must not share signing secrets or other sensitive proof material.

Shared responsibility

Privacy Pump provides authorization and privacy controls. Users remain responsible for:

• Protecting wallets and recovery material
• Choosing a workable approval threshold
• Managing membership carefully
• Verifying recipients, amounts, fees, and proposal payloads
• Following safe operational practices

Review the known limitations before relying on the system for sensitive activity.