Skip to content

Glossary

A member vote indicating support for a proposal. When enough approvals are collected to satisfy the vault threshold, a proposal becomes executable.


The privacy computation layer used by Privacy Pump for confidential workflows, private membership verification, and future private coordination features.


A routing mode that combines multiple compatible routes into a single release event to improve privacy and operational efficiency.


A private communication space available to authorized vault members.


A vault member authorized to participate in governance, proposal review, and approval decisions.


The wallet that originally creates a vault through the Privacy Pump Vault Factory.


The proposal state reached when sufficient approvals have been collected and the proposal can be executed.


The final stage of a proposal lifecycle where the requested action is performed on-chain.


A future Privacy Pump architecture concept where member identities are verified privately rather than publicly exposed.


The communication layer used by Privacy Pump for secure vault messaging and coordination.


An authorized participant within a vault who can interact with governance and communication systems according to their permissions.


A human-readable nickname assigned to a member wallet address.


A vault requiring multiple members to approve actions according to a configured approval threshold.


A unique cryptographic value used to prevent the same private action from being executed more than once.


The initial state of a proposal before it receives enough approvals or rejections.


A single-owner vault that provides access to Privacy Pump privacy infrastructure without requiring multiple signers.


The collection of privacy technologies used throughout Privacy Pump, including Arcium, ZK systems, and private routing.


The collection of deposits, routes, or participants contributing to privacy guarantees within the system.


A deposit workflow that routes assets through Privacy Pump privacy infrastructure before they arrive at a destination vault.


A future architecture where member authorization can be verified without publicly exposing member identities.


A collection of privacy-enhancing routing techniques designed to reduce direct linkability between transactions.


A future vault architecture focused on private membership verification and confidential coordination.


A withdrawal workflow that routes assets through Privacy Pump privacy infrastructure before final delivery.


A requested action submitted to a vault for member review and approval.


The member who originally submits a proposal for review.


The sequence of states a proposal passes through, from creation to execution or rejection.


A member vote opposing a proposal.


The number of rejections required to make proposal approval mathematically impossible.


A future routing enhancement where a transaction can be split into multiple independent routes to improve privacy.


A vault member capable of approving or rejecting proposals.


A token that follows the Solana Program Library token standard.


The minimum number of approvals required for a proposal to become executable.


The collection of assets owned and managed by a vault.


A secure on-chain account structure used to manage assets, governance, and coordination.


The main interface used to manage vault assets, proposals, members, and settings.


The Privacy Pump program responsible for creating and initializing new vaults.


Metadata associated with a vault, including its name, image, description, and labels.


The connection layer that allows wallets such as Phantom and Solflare to interact with Privacy Pump.


The privacy infrastructure used for private deposits, protected withdrawals, privacy sets, and future zero-knowledge enhancements.


A cryptographic proof that allows a statement to be verified without revealing the underlying information used to generate it.