> For the complete documentation index, see [llms.txt](https://docs.squads.so/squads-v3-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/squads-v3-docs/basics/whats-a-multisig.md).

# What's a Multisig?

## What's a Multisig?

The most widely known example of a smart contract wallet is a multisig. They have been around since the early days of Bitcoin and are widely used for the purposes of self-custody of crypto assets across blockchains.

A multisig is a non-custodial solution where control over assets is not exercised by a single private key, but rather by multiple private keys. It can be thought of as a safe that requires multiple unique keys to open it and move the assets. That means that even if one of the keys is compromised the assets remain secure (no single point of failure).

Every Squad is a multisig at its core, which ensures that any transaction or action taken within Squads requires the approval of multiple members of the team. As a result, the risk of unauthorized or malicious activity is greatly reduced, as it becomes impossible for a single owner to access and manipulate funds or trigger harmful transactions to the protocol. On top of that multisignature technology serves as a consensus mechanism allowing teams to make decisions over core team assets together in a decentralized manner.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.squads.so/squads-v3-docs/basics/whats-a-multisig.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
