Privacy Pump Vault Factory
The Privacy Pump Vault Factory is responsible for creating and initializing new vaults within the Privacy Pump ecosystem.
Every vault begins its lifecycle through the factory layer, which configures governance parameters, member relationships, metadata, and treasury controls before the vault becomes operational.
The factory serves as the entry point for both Private Multisigs and personal vaults.
Purpose Of The Vault Factory
Section titled “Purpose Of The Vault Factory”The Vault Factory exists to standardize vault creation.
Rather than manually creating and configuring accounts, users interact with a guided setup process while the factory handles the underlying initialization.
This ensures that every vault is deployed using the same security and governance framework.
What Happens During Vault Creation
Section titled “What Happens During Vault Creation”When a user creates a vault, the factory performs several actions behind the scenes.
These include:
- Creating the vault account
- Assigning the initial owner
- Registering members
- Setting the approval threshold
- Initializing governance settings
- Linking metadata
- Preparing treasury controls
Once these steps are complete, the vault becomes active.
Supported Vault Types
Section titled “Supported Vault Types”The Vault Factory currently supports two vault models.
Private Multisigs
Section titled “Private Multisigs”Private Multisigs are designed for groups, teams, DAOs, and shared treasuries.
Features include:
- Multiple members
- Approval thresholds
- Proposal-based treasury management
- Shared governance
Every treasury action must follow the vault’s approval rules.
Personal Vaults
Section titled “Personal Vaults”Personal vaults are designed for individual users.
Features include:
- Single owner
- No multisig approvals required
- Private deposits
- Protected withdrawals
- Personal treasury management
Personal vaults use the same privacy infrastructure as Private Multisigs while maintaining a simplified governance model.
Metadata Initialization
Section titled “Metadata Initialization”Vault metadata is configured during creation.
Metadata may include:
- Vault name
- Description
- Vault image
- Member labels
This information improves organization and user experience while remaining separate from treasury operations.
Governance Configuration
Section titled “Governance Configuration”The factory also establishes the vault’s governance model.
Examples include:
- Number of members
- Approval threshold
- Proposal requirements
- Execution permissions
These parameters define how future treasury decisions will be handled.
Treasury Readiness
Section titled “Treasury Readiness”A newly created vault does not require any assets to exist.
The vault becomes treasury-ready immediately after creation.
Users can:
- Receive deposits
- Create proposals
- Add members
- Configure settings
- Begin treasury operations
without additional setup.
Relationship To Other Components
Section titled “Relationship To Other Components”The Vault Factory is only responsible for creation.
Once a vault has been deployed, responsibility shifts to other system components.
| Component | Responsibility |
|---|---|
| Vault Factory | Creates vaults |
| Private Vault Layer | Manages vault state |
| Privacy Pump ZK Pool | Handles privacy infrastructure |
| Arcium Layer | Provides private authorization mechanisms |
| Logos Layer | Enables private communication |
Design Goals
Section titled “Design Goals”The Vault Factory was designed around three principles:
Simplicity
Section titled “Simplicity”Vault creation should be accessible to both individuals and organizations.
Consistency
Section titled “Consistency”Every vault should follow the same deployment standards.
Extensibility
Section titled “Extensibility”Future vault types and governance models should be supported without redesigning the entire system.
Key Takeaway
Section titled “Key Takeaway”The Privacy Pump Vault Factory is the foundation of the platform.
Every vault begins here.
By standardizing vault creation, the factory ensures that governance, privacy, communication, and treasury systems are initialized consistently before a vault becomes operational.