Vaults
Vaults are the core operational construct in SQRL. A vault is an organisational asset container that enforces multi-party signing. Every movement originates from a vault. Whether it is a mint, a redemption, or a transfer, it requires signatures from the vault's authorised signers.
A vault is a workspace-level resource. It belongs to a specific workspace and is governed by that workspace's policies and permissions. It inherits the network of its workspace.
Each vault is configured with a threshold, an M-of-N signing requirement. A 2-of-3 vault has three registered signers. Any two of them must sign a movement before it is finalised and broadcast to the Bitcoin network. Even a vault with a single signer is expressed as a 1-of-1 threshold.
Vaults can own SCL token contracts and hold token balances. The vault's address is a Bitcoin address derived from its multi-signature configuration, the combination of its signers' keys and its threshold.
#Funding a vault
A vault has its own Bitcoin address. To fund it, use the Receive option on the vault to display the vault's address, then send BTC to that address from an external source. Incoming funds appear once the network confirms them.
A vault is not a personal wallet. It belongs to the workspace, and no value moves out of it without the required number of signatures. Balances you see are held on-chain at the vault's address, not by SQRL.
Read Creating a vault, then Threshold signing and Vault policies.