> ## Documentation Index
> Fetch the complete documentation index at: https://docs.walletsuite.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Shares & Thresholds

> What a share and a threshold are, and the default 2-of-2 model behind every wallet.

Every wallet is self-custodial with no seed phrase. You hold the wallet, WalletSuite holds a co-signing share, and both are needed to sign. This page explains what a share and a threshold are. For where to store the wallet and how recovery works, see [Recovery](/mpc/recovery).

## What a share is

A share is one half of the wallet's signing key. `createWallet` returns your half as an opaque blob under a single `keyId`, and WalletSuite holds the other half server-side. Neither side ever holds the full key, and the full key is never assembled to sign.

The SDK does not persist your half. You pass the wallet back on every `deriveAddress` and `sign*` call, so store it in durable storage you control. See [Recovery](/mpc/recovery) for storage patterns.

## Thresholds

A threshold is how many shares must cooperate to sign. Every wallet is **2-of-2**: two shares exist and both are required. WalletSuite cannot sign on its own, and neither can you. That is what keeps the wallet self-custodial, with no single party able to move funds.

Custom thresholds and an opt-in recovery mode for extra redundancy are on the roadmap. See [Recovery](/mpc/recovery).

## Next steps

<CardGroup cols={2}>
  <Card title="Recovery" icon="life-ring" href="/mpc/recovery">
    Where to store the wallet, backup patterns, and the roadmapped recovery mode.
  </Card>

  <Card title="Signing" icon="signature" href="/mpc/signing">
    Sign transactions across 84 chains with the wallet you hold.
  </Card>
</CardGroup>