Skip to content

Private Vault Architecture

A Private Vault is the core treasury container within the Privacy Pump ecosystem.

It combines governance, privacy infrastructure, communication tools, and treasury controls into a single operational environment.

Rather than functioning as a simple wallet, a Private Vault serves as a coordinated treasury management system designed for individuals, teams, and organizations.


Each vault consists of several independent components working together.

These components include:

  • Governance Layer
  • Treasury Layer
  • Privacy Layer
  • Communication Layer
  • Metadata Layer

Together they form the complete vault environment.


The Governance Layer controls decision making.

Responsibilities include:

  • Member management
  • Approval collection
  • Rejection collection
  • Threshold enforcement
  • Proposal execution

Every treasury action passes through the governance layer before execution.

This ensures that vault operations follow predefined authorization rules.


The Treasury Layer manages vault assets.

Responsibilities include:

  • SOL custody
  • SPL token custody
  • Asset transfers
  • Deposit tracking
  • Withdrawal tracking

The treasury layer is responsible for managing assets regardless of whether privacy features are used.


The Privacy Layer provides optional privacy protections for treasury activity.

Primary components include:

  • Privacy Pump ZK Pool
  • Private deposits
  • Protected withdrawals
  • Controlled release queues
  • Batch routing

These systems help reduce unnecessary information exposure during treasury operations.


The Communication Layer enables vault members to coordinate directly inside the vault environment.

Primary component:

  • Logos Vault Chat

This allows discussions surrounding treasury activity to occur within the same environment where governance actions take place.


The Metadata Layer improves vault organization.

Examples include:

  • Vault names
  • Vault descriptions
  • Vault images
  • Member labels

Metadata does not affect treasury authorization or governance decisions.

It exists to improve usability and vault management.


A vault generally follows the following lifecycle:

Vault Creation
|
v
Member Setup
|
v
Threshold Configuration
|
v
Treasury Funding
|
v
Proposal Creation
|
v
Approvals / Rejections
|
v
Execution
|
v
Ongoing Management

This process repeats throughout the life of the vault.


Private Multisigs contain multiple authorized members.

Characteristics:

  • Shared ownership
  • Approval thresholds
  • Proposal-based governance
  • Team coordination

Treasury actions require sufficient approvals before execution.


Personal vaults are designed for individual users.

Characteristics:

  • Single owner
  • No multisig approval process
  • Private treasury management
  • Direct execution model

Personal vaults use the same privacy infrastructure while maintaining simplified governance.


A vault can operate with or without privacy-enabled treasury actions.

Standard treasury operations remain available at all times.

When users choose privacy-enabled actions, the vault integrates with:

  • Privacy Pump ZK Pool
  • Private routing system
  • Controlled release queues
  • Batch routing mechanisms

The vault itself remains unchanged while the privacy layer provides additional protection.


The Private Vault Architecture is designed around four principles:

Treasury actions require explicit authorization.

Sensitive treasury activity should minimize unnecessary exposure.

Teams should be able to coordinate effectively.

Advanced functionality should remain accessible to non-technical users.


Users
|
v
Private Vault
|-- Governance
|-- Treasury
|-- Privacy
|-- Communication
|-- Metadata

Each layer performs a specialized role while contributing to the overall vault experience.


A Private Vault is more than a wallet.

It is a complete treasury environment that combines governance, privacy, communication, and asset management into a single system.

The vault serves as the central operating unit of the Privacy Pump ecosystem.