> For the complete documentation index, see [llms.txt](https://bewinxed.gitbook.io/niftybot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bewinxed.gitbook.io/niftybot/niftypay/multisig-wallets.md).

# MultiSig Wallets

![](/files/MJKJUTdVd51KReeIfEFi)

NiftyPAY MultiSig wallets are **Discord** **Integrated** wallets that are stored within NiftyBOT:

* 🌌 **Cross-Server:** A multisig wallet can be used for multiple guilds at once.
* 📝 **MultiSig:** Any transactions using these wallets will need to be ✍**signed** by multiple parties.
* ✍ **AuditLog:** Any transactions or setting changes are logged in the bot and can be traced back.
* 💬 **Custodial:** The wallets can only be accessed using the bot.
* 🔐 **Secure:** The wallets are stored securely in NiftyBOT and are encrypted, They can't be used by anyone outside NiftyBOT even if the database was leaked.

You can use these wallets to manage your DAO funds or simply have a shared wallet between you and someone else.

## Security

NiftyPAY Multisig wallets can be configured with a number of signers required for any transaction, No transaction can be made without the explicit sign of each member.

### 👥 MultiSig Approvals

![](/files/49ABivEHYka0TOJW7QK2)

Any transfer, withdrawal or settings change to the wallet needs to be approved by the **minimum number of signers** who have the **manage** permission.

### 🔐 Two-Factor Authentication

![](/files/1RFGoHETafYhYHE4MrCP)

All members have the option to secure their account with a two-factor authentication code, even if your account is compromised, no signature happens without your two factor auth code.

### ⚖ Signer Permissions

![](/files/caimBZiJjWMx1xbLJZ7z)

Each signer in the multisig can be given granular control over the wallet's funds:

* **Send:** Send funds from the wallet to another wallet.
* **Transfer:** Transfer funds from one Multisig wallet to another under the same **Guild**.
* **Manage:** Manage the wallet (Add and remove **signers**, Add **whitelisted** recipients)

### ✋ Thresholds

![](/files/wApMjeIQBBsU24Xywwro)

Each signer in the multisig can be given a specific threshold that they can initiate multisig for, you can set as many thresholds as needed for each kind of token, **SOL/SPL supported.**

If the signer is not authorized for the **amount** and **type** of token being transacted, they won't be eligible to sign.

### 📃 Whitelisted Recipients

If selected, transfers from the wallet can only be made to the addresses in this list, **Adding** or **removing** recipients will need to be ✍**signed** by the members in the multisig.


---

# 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://bewinxed.gitbook.io/niftybot/niftypay/multisig-wallets.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.