Private Routing
It is achieved by making movement difficult to trace.
Private Routing is the system that powers protected withdrawals and privacy-preserving asset movement inside Privacy Pump.
Instead of moving assets directly from a vault to a recipient, Privacy Pump can route assets through privacy-preserving workflows designed to reduce linkability between the sender and destination.
Why Routing Matters
Section titled “Why Routing Matters”A normal blockchain transfer is simple:
Vault | v
RecipientAnyone observing the chain can often see:
- Source
- Destination
- Amount
- Timing
This creates a direct relationship between sender and receiver.
Privacy Pump Approach
Section titled “Privacy Pump Approach”Privacy Pump introduces an additional routing layer.
Vault | vZK Pool | v
Routing Layer | v
RecipientThe goal is to reduce direct traceability between the vault and the final destination.
Protected Withdrawals
Section titled “Protected Withdrawals”Protected Withdrawals use the routing layer automatically.
A typical workflow looks like:
Proposal | v
Approval | v
Execution | v
Private Routing | v
RecipientThe vault authorizes the action.
The routing layer handles the privacy-preserving movement.
Automatic Mode
Section titled “Automatic Mode”Automatic Mode prioritizes simplicity.
Vault | v
Private Route | v
RecipientAfter approval and execution, the routing process occurs automatically.
Users receive a streamlined experience while still benefiting from the privacy layer.
Controlled Mode
Section titled “Controlled Mode”Controlled Mode gives users additional control over delivery.
Vault | v
Private Route | v
Queue | v
Manual Release | v
RecipientFunds remain queued until released.
This separates authorization from delivery.
Batch Routing
Section titled “Batch Routing”Batch Routing allows multiple compatible routes to be grouped together.
Routes A, B, and C | v
Batch | v
ReleaseGrouping routes can increase privacy by making individual transfers more difficult to isolate.
Routing Compatibility
Section titled “Routing Compatibility”For routes to be grouped together, they must share compatible routing characteristics.
Examples include:
- Same routing type
- Same destination rules
- Same release mode
- Same routing configuration
Compatible routes can be combined into a single batch release.
Relationship to the ZK Pool
Section titled “Relationship to the ZK Pool”The routing layer operates alongside the ZK Pool.
Vault | vZK Pool | v
Private Routing | v
RecipientThe ZK Pool provides the privacy-preserving asset layer.
The routing system determines how assets move after authorization.
Relationship to Governance
Section titled “Relationship to Governance”Routing never bypasses governance.
Every protected withdrawal still requires:
Proposal | v
Approvals | v
Threshold Reached | v
Execution | v
RoutingRouting occurs only after the vault authorizes the action.
Future Routing Enhancements
Section titled “Future Routing Enhancements”The architecture has been designed to support future capabilities such as:
- Enhanced route fragmentation
- Advanced batch processing
- Additional privacy strategies
- Improved routing controls
- Expanded privacy set growth
Key Takeaway
Section titled “Key Takeaway”Private Routing is the movement layer that sits between vault authorization and final delivery.
Vault | v
Proposal | v
Approval | v
Execution | v
Private Routing | v
RecipientIt works together with the ZK Pool, Privacy Pump Private Multisig, Arcium, and Logos to create a privacy stack that protects not only assets, but also the paths those assets take.