Glossary OS

Plain meaning

Start with the shortest useful explanation before going deeper.

The latest version of the Squads multisig protocol on Solana, offering improved transaction batching, spending limits, time-locks, sub-accounts (Squads Vaults), and role-based permissions. Squads v4 introduces a more gas-efficient design with fewer accounts per transaction and supports programmable execution conditions. It is widely used for managing program upgrade authorities, treasury wallets, and protocol governance on Solana mainnet.

Mental model

Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.

Think of it as a building block that connects one definition to the larger Solana system around it.

Technical context

Place the term inside its Solana layer so the definition is easier to reason about.

Failure modes, audits, attack surfaces, and safe design patterns.

Why builders care

Turn the term from vocabulary into something operational for product and engineering work.

This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.

AI handoff

Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.

Squads v4 (squads-v4)
Category: Security
Definition: The latest version of the Squads multisig protocol on Solana, offering improved transaction batching, spending limits, time-locks, sub-accounts (Squads Vaults), and role-based permissions. Squads v4 introduces a more gas-efficient design with fewer accounts per transaction and supports programmable execution conditions. It is widely used for managing program upgrade authorities, treasury wallets, and protocol governance on Solana mainnet.
Related: Squads (Multisig), Multisig, Time-Lock

Glossary Copilot

Ask grounded Solana questions without leaving the glossary.

Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.

Open full Copilot workspace

Question

Explain this code

Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.

Ask a glossary-grounded question

The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.

Concept graph

See the term as part of a network, not a dead-end definition.

These branches show which concepts this term touches directly and what sits one layer beyond them.

Branch

Squads (Multisig)

A multisig protocol on Solana (Squads v3/v4) enabling M-of-N approval for transactions. Used to manage program upgrade authorities, treasury wallets, and DAO operations. Squads creates a multisig PDA that acts as the authority; members propose transactions that execute once the threshold is reached. Critical for production program security.

Authority Upgrade Authority

Open term

Branch

Multisig

An account controlled by multiple parties requiring M-of-N signatures to authorize actions. On Solana, multisig is implemented by programs like Squads rather than at the protocol level. Use cases: program upgrade authority (require 3-of-5 team members), treasury management, and DAO governance execution.

Open term

Branch

Time-Lock

A security mechanism that enforces a mandatory delay between proposing a privileged action (such as a program upgrade, treasury withdrawal, or parameter change) and its execution. Time-locks give stakeholders and users a window to review pending actions, detect malicious proposals, and exit the protocol if needed. On Solana, time-locks are typically implemented through multisig programs like Squads or governance frameworks that queue transactions for a configurable delay period before they become executable.

Open term

Next concepts to explore

Keep the learning chain moving instead of stopping at one definition.

These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.

Developer Tools

Squads (Multisig)

A multisig protocol on Solana (Squads v3/v4) enabling M-of-N approval for transactions. Used to manage program upgrade authorities, treasury wallets, and DAO operations. Squads creates a multisig PDA that acts as the authority; members propose transactions that execute once the threshold is reached. Critical for production program security.

Open term

Developer Tools

Multisig

An account controlled by multiple parties requiring M-of-N signatures to authorize actions. On Solana, multisig is implemented by programs like Squads rather than at the protocol level. Use cases: program upgrade authority (require 3-of-5 team members), treasury management, and DAO governance execution.

Open term

Security

Time-Lock

A security mechanism that enforces a mandatory delay between proposing a privileged action (such as a program upgrade, treasury withdrawal, or parameter change) and its execution. Time-locks give stakeholders and users a window to review pending actions, detect malicious proposals, and exit the protocol if needed. On Solana, time-locks are typically implemented through multisig programs like Squads or governance frameworks that queue transactions for a configurable delay period before they become executable.

Open term

Security

State Inconsistency

Vulnerability where a program's on-chain state becomes internally contradictory, often due to partial updates, missing account reloading after CPI, or race conditions between instructions. For example, a lending protocol's collateral ratio may become stale if account data is not refreshed after a CPI that modifies token balances.

Open term

Related terms

Follow the concepts that give this term its actual context.

Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.

Developer Toolssquads

Squads (Multisig)

A multisig protocol on Solana (Squads v3/v4) enabling M-of-N approval for transactions. Used to manage program upgrade authorities, treasury wallets, and DAO operations. Squads creates a multisig PDA that acts as the authority; members propose transactions that execute once the threshold is reached. Critical for production program security.

Open term

Developer Toolsmultisig

Multisig

An account controlled by multiple parties requiring M-of-N signatures to authorize actions. On Solana, multisig is implemented by programs like Squads rather than at the protocol level. Use cases: program upgrade authority (require 3-of-5 team members), treasury management, and DAO governance execution.

Open term

Securitytime-lock-security

Time-Lock

A security mechanism that enforces a mandatory delay between proposing a privileged action (such as a program upgrade, treasury withdrawal, or parameter change) and its execution. Time-locks give stakeholders and users a window to review pending actions, detect malicious proposals, and exit the protocol if needed. On Solana, time-locks are typically implemented through multisig programs like Squads or governance frameworks that queue transactions for a configurable delay period before they become executable.

Open term

Stay in the same layer and keep building context.

These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.

Security

Missing Signer Check

A vulnerability where a program accepts an account in a privileged role (e.g., admin, authority, payer) without verifying that the account actually signed the transaction, allowing any caller to impersonate that authority by simply passing the target pubkey as an instruction account. In native Solana programs, the check requires asserting account.is_signer == true; in Anchor, the Signer<'info> type enforces this automatically. Exploitation lets an attacker bypass all access control gated on authority equality checks, making it one of the most critical and commonly audited vulnerabilities in Solana programs.

Open term

Security

Missing Owner Check

A vulnerability where a program deserializes and trusts account data without first confirming that the account is owned by the expected program, allowing an attacker to substitute a maliciously crafted account owned by a different program whose byte layout happens to satisfy the deserialization. On Solana, every account stores a 32-byte owner field set to the program that created it; native programs must assert account.owner == &expected_program_id, while Anchor's Account<'info, T> wrapper performs this check automatically. Failure to validate ownership can lead to complete auth bypass if an attacker can construct a fake account whose data parses into a struct with elevated privileges.

Open term

Security

Arbitrary CPI

A vulnerability where a program accepts an arbitrary program account from the caller and invokes it via Cross-Program Invocation (CPI) without verifying it matches a known, trusted program ID, effectively letting an attacker substitute a malicious program that executes under the victim program's authority or manipulates accounts the victim program passes to it. A common pattern is accepting a token_program account without checking it equals spl_token::ID, so the attacker passes a lookalike program that records or drains account data. Prevention requires hard-coding or explicitly checking the program ID before every CPI call.

Open term

Security

PDA Substitution Attack

A vulnerability where a program derives a PDA internally but accepts an externally supplied account as that PDA without re-deriving and comparing the address, allowing an attacker to pass a different PDA (derived from attacker-controlled seeds) that the program will treat as legitimate. Because PDAs are deterministic, the only way to guarantee account identity is to call Pubkey::find_program_address (or equivalent) with the expected seeds inside the program and assert the result equals the supplied key. Anchor's seeds and bump constraints on the Account type automate this re-derivation and equality check.

Open term