Protected Withdrawals
Introduction
Section titled “Introduction”A Protected Withdrawal allows funds to leave a vault through Privacy Pump’s Privacy Layer.
Instead of sending funds directly from a vault to a recipient through a standard blockchain transfer, the withdrawal is processed through privacy infrastructure before reaching its destination.
The objective is straightforward:
Reduce unnecessary public visibility during treasury distribution operations.
Why Use A Protected Withdrawal?
Section titled “Why Use A Protected Withdrawal?”Standard blockchain withdrawals create a direct relationship between:
- The vault
- The recipient
- The transferred amount
This information becomes visible on-chain.
Protected Withdrawals introduce an additional privacy layer between the vault and the final destination.
This helps reduce direct exposure of treasury spending activity.
How Protected Withdrawals Work
Section titled “How Protected Withdrawals Work”At a high level, the process is simple:
- A withdrawal is approved
- Funds enter Privacy Pump’s Privacy Layer
- Privacy infrastructure processes the operation
- Funds are delivered to the recipient
The experience remains simple while Privacy Pump handles the underlying workflow.
Standard Withdrawal vs Protected Withdrawal
Section titled “Standard Withdrawal vs Protected Withdrawal”Standard Withdrawal
Section titled “Standard Withdrawal”Vault
↓
Recipient
Direct blockchain transfer.
Simple and transparent.
Protected Withdrawal
Section titled “Protected Withdrawal”Vault
↓
Privacy Layer
↓
Recipient
Additional privacy infrastructure is used before funds reach their destination.
Supported Vault Types
Section titled “Supported Vault Types”Protected Withdrawals can be used with:
- Personal Vaults
- Private Multisigs
The privacy workflow remains consistent regardless of vault type.
Treasury Distribution Privacy
Section titled “Treasury Distribution Privacy”Treasury spending can reveal valuable operational information.
Examples include:
- Vendor payments
- Contributor compensation
- Treasury management decisions
- Strategic allocations
- Operational activity
Protected Withdrawals help reduce the amount of information directly exposed during these operations.
Designed For Simplicity
Section titled “Designed For Simplicity”Users do not need to understand:
- Zero-knowledge systems
- Routing infrastructure
- Privacy set mechanics
- Cryptographic proofs
The process remains straightforward:
Create the withdrawal.
Approve it if required.
Confirm the transaction.
Privacy Pump handles the rest.
Relationship To The ZK Pool
Section titled “Relationship To The ZK Pool”Protected Withdrawals use Privacy Pump’s privacy infrastructure.
The ZK Pool is one of the core components involved in processing these operations.
Users interact with the withdrawal interface.
The Privacy Layer handles the underlying workflow.
Privacy Is Optional
Section titled “Privacy Is Optional”Privacy Pump supports multiple treasury workflows.
Users may choose:
- Standard Withdrawals
- Protected Withdrawals
This flexibility allows organizations and individuals to select the workflow that best fits their needs.
Security
Section titled “Security”Protected Withdrawals remain secured by Solana’s underlying blockchain.
Solana remains the settlement layer; review every transaction and account for network risk.
Transactions continue to be finalized on-chain.
What Happens Next?
Section titled “What Happens Next?”Protected Withdrawals describe the privacy-enabled withdrawal process.
The next pages explain the different routing modes available:
- Automatic Mode
- Controlled Mode
- Batch Routing
These modes determine how privacy-enabled transfers are processed.
A Protected Withdrawal allows funds to leave a vault through Privacy Pump’s privacy infrastructure before reaching their final destination.