Private Membership System

Membership is one of the most important components of a vault.

Members control proposals, treasury actions, governance decisions, and vault security.

Privacy Pump is designed to minimize unnecessary exposure of membership information while maintaining secure governance and authorization workflows.

Why Membership Privacy Matters

In traditional multisig systems, membership alone can reveal valuable information.

Observers may be able to infer:

Business relationships
Team structures
Treasury controllers
DAO governance participants
Operational responsibilities

Even when assets remain secure, exposed membership data can reveal how an organization operates.

Privacy Pump Approach

Privacy Pump separates three different concepts:

Membership

Who belongs to the vault.

Governance

Who can approve or reject proposals.

Communication

How members coordinate and discuss decisions.

Each layer can evolve independently while preserving vault security.

Vault Membership Structure

Every vault contains a defined set of members.

Example:

Vault AlphaMember AMember BMember CMember DMember E

The vault threshold determines how many members are required to authorize actions.

Membership and Governance

Membership alone does not execute actions.

Actions require governance approval.

Members
  |
  v

Proposal
  |
  v

Approvals
  |
  v

Threshold Reached
  |
  v

Execution

This prevents individual members from acting unilaterally unless the vault is intentionally configured as a 1/1 vault.

Member Labels

Privacy Pump supports custom member labels.

Examples:

Treasury manager
Operations
Founder
Signer 1
Signer 2
Security team

Labels improve organization while helping members identify responsibilities within the vault.

Membership Changes

Membership can evolve over time.

Supported governance actions include:

Add member
Remove member
Update threshold
Update vault settings

These changes are controlled through proposals and approval workflows.

Membership and Vault Chat

Membership also controls access to communication.

Vault Member
  |
  v

Vault Chat Access
  |
  v

Logos Communication Layer

Only authorized vault members can participate in vault-specific discussions.

Membership and Arcium

The Arcium privacy layer is designed to support future confidential authorization workflows.

As the architecture evolves, membership-related authorization logic can leverage confidential computation while preserving vault security.

Membership and Treasury Control

Members collectively govern vault assets.

Members
  |
  v

Proposal
  |
  v

Approvals
  |
  v

Treasury Action

No treasury action bypasses the configured governance model.

Example Vault Structures

Personal Vault

1 MemberThreshold: 1/1

Single-user control.

Small Team

3 MembersThreshold: 2/3

Balanced flexibility and security.

DAO Treasury

7 MembersThreshold: 4/7

Distributed governance model.

High-Security Treasury

9 MembersThreshold: 7/9

Maximum governance protection.

Future Membership Enhancements

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

Enhanced membership privacy
Advanced authorization workflows
Confidential governance features
Additional Arcium-powered authorization models
Expanded vault identity systems

Key Takeaway

The Private Membership System forms the foundation of vault governance.

Members create proposals, discuss decisions, authorize actions, and collectively control vault assets.

Combined with Multisig Governance, Logos Communication, Arcium Privacy, and the ZK Pool, membership becomes part of a broader privacy-focused architecture designed to protect both assets and relationships.