Controlled Mode
Introduction
Section titled “Introduction”Controlled Mode gives users greater control over privacy-enabled treasury operations.
Instead of immediately completing a routing operation, Privacy Pump places the operation into a queue.
The user can then decide when the operation should be released.
This creates additional flexibility for organizations and treasury managers who want more control over timing and routing behavior.
The Philosophy Behind Controlled Mode
Section titled “The Philosophy Behind Controlled Mode”Some treasury operations benefit from additional control.
Examples include:
- Scheduled treasury activity
- Coordinated team operations
- Batch processing
- Operational planning
- Privacy-sensitive distributions
Controlled Mode was designed for these situations.
Instead of immediate completion, users decide when a queued operation should be finalized.
How Controlled Mode Works
Section titled “How Controlled Mode Works”At a high level:
User Creates Operation
↓
Privacy Queue
↓
User Releases Operation
↓
Destination
Controlled Private Deposits
Section titled “Controlled Private Deposits”When using Controlled Mode for Private Deposits:
- A deposit is created
- The operation enters the queue
- The user chooses when to release it
- Funds are delivered to the destination vault
The deposit does not automatically complete immediately.
The user remains in control of the release process.
Controlled Protected Withdrawals
Section titled “Controlled Protected Withdrawals”When using Controlled Mode for Protected Withdrawals:
- The withdrawal is created
- Required approvals are completed (for Private Multisigs)
- The operation enters the queue
- The user releases the operation
- Funds are delivered to the recipient
This provides greater flexibility compared to Automatic Mode.
Why Use Controlled Mode?
Section titled “Why Use Controlled Mode?”Controlled Mode can be useful when timing matters.
Examples include:
Treasury Coordination
Section titled “Treasury Coordination”Release multiple treasury actions at a chosen time.
Operational Planning
Section titled “Operational Planning”Prepare transactions ahead of time and release them later.
Privacy Management
Section titled “Privacy Management”Combine multiple operations into a coordinated release workflow.
Batch Processing
Section titled “Batch Processing”Prepare operations that may later be grouped together.
Queue Management
Section titled “Queue Management”Controlled Mode introduces a queue layer.
Queued operations remain pending until released.
Depending on the routing configuration, users may release:
- Individual operations
- Multiple operations
- Batch groups
The release process remains under user control.
Controlled Mode vs Automatic Mode
Section titled “Controlled Mode vs Automatic Mode”Automatic Mode
Section titled “Automatic Mode”- Immediate processing
- No queue
- Fastest workflow
- Simplest experience
Controlled Mode
Section titled “Controlled Mode”- Queued operations
- User-managed releases
- More flexibility
- Supports advanced routing workflows
Neither mode is better.
They are designed for different use cases.
Private Multisig Support
Section titled “Private Multisig Support”Controlled Mode works with Private Multisigs.
Approval requirements still apply before treasury actions can proceed.
Once approvals are completed, the operation can enter the queue and wait for release.
Personal Vault Support
Section titled “Personal Vault Support”Controlled Mode also works with Personal Vaults.
Although no approval process is required, users may still prefer controlling when operations are released.
This can be useful for treasury planning and privacy-sensitive activity.
Relationship To Batch Routing
Section titled “Relationship To Batch Routing”Controlled Mode is the foundation for Batch Routing.
Operations must first enter the queue before they can be grouped together.
The next section explains how multiple queued operations may be processed through Batch Routing.
Security
Section titled “Security”Controlled Mode does not change Privacy Pump’s security model.
The difference is operational control.
Privacy infrastructure, blockchain security, and treasury protections remain the same.
What Happens Next?
Section titled “What Happens Next?”Controlled Mode introduces the queue system.
The next section explains Batch Routing, which allows compatible queued operations to be grouped together and released as a single workflow.
Controlled Mode allows users to queue privacy-enabled operations and decide when those operations should be released.