Arcium Privacy Layer

Arcium provides Privacy Pump’s confidential computation layer.

While the ZK Pool focuses on privacy-preserving asset movement, Arcium is responsible for enabling private decision-making and private authorization workflows.

Together, these systems form the core privacy architecture of Privacy Pump.

---

Why Arcium?

Traditional multisig systems expose nearly everything on-chain.

Observers can often see:

• Who approved
• Who rejected
• Proposal activity
• Member participation
• Governance patterns

Arcium introduces a confidential computation layer that can reduce information exposure during sensitive authorization workflows.

---

Privacy Pump Architecture

Privacy Pump separates privacy responsibilities across multiple layers.

ZK Pool

Responsible for:

• Privacy-enabled deposits
• Protected withdrawals
• Routing
• Controlled releases
• Batch processing

Arcium Layer

Responsible for:

• Private authorization workflows
• Confidential approval logic
• Private proposal validation
• Future confidential governance features

---

High-Level Architecture

Members
  |
  v

Privacy Pump Private Multisig
  |
  v

Arcium Privacy Layer
  |
  v

Authorization Result
  |
  v

Proposal Execution

Arcium operates between user actions and final execution.

It acts as a privacy-preserving authorization layer.

---

Current Role in Privacy Pump

The current Arcium integration focuses on authorization architecture.

Its primary responsibilities include:

• Authorization verification
• Approval validation
• Proposal authorization workflows
• Future confidential governance support

The integration is intentionally modular so new privacy capabilities can be added over time.

---

Future Privacy Capabilities

The architecture has been designed to support future enhancements such as:

Confidential Approvals

Allow approvals to be processed through confidential computation workflows.

---

Confidential Rejections

Reduce visibility into rejection activity.

---

Private Governance

Enable governance actions without exposing unnecessary participation data.

---

Private Membership Logic

Support future confidential membership verification models.

---

Private Threshold Validation

Validate approval requirements while minimizing exposed information.

---

Relationship to Private Multisigs

Arcium is deeply connected to the Privacy Pump Private Multisig architecture.

Vault
  |
  v

Proposal
  |
  v

Approval Workflow
  |
  v

Arcium Layer
  |
  v

Execution Decision

The goal is to keep vault management secure while reducing information leakage.

---

Relationship to the ZK Pool

Arcium and the ZK Pool serve different purposes.

Layer	Purpose
ZK Pool	Privacy-preserving asset movement
Arcium	Privacy-preserving computation
Multisig	Governance and authorization
Logos	Private communication

Together these systems form the complete Privacy Pump privacy stack.

---

Design Philosophy

Privacy Pump follows a layered privacy model.

No single component is responsible for all privacy guarantees.

Instead:

• ZK Pool protects movement.
• Arcium protects computation.
• Logos protects communication.
• Multisig protects governance.

Each layer contributes to the overall privacy architecture.

---

Simplified Privacy Stack

Users
  |
  v

Privacy Pump Private Multisig
  |
  v

Arcium Privacy Layer
  |
  v
ZK Pool
  |
  v

Destination

---

Key Takeaway

Arcium serves as Privacy Pump’s confidential computation layer.

While the ZK Pool focuses on private movement of assets, Arcium focuses on private decision-making, authorization, and governance workflows.

Together, they create a privacy architecture that extends beyond asset transfers and into the logic that controls them.

---