> ## 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.

# MPC Wallets Overview

> Ship self-custodial wallets with no seed phrase across 84 chains. You hold the wallet, WalletSuite holds a co-signing share, and both are needed to sign.

WalletSuite MPC gives your users self-custodial wallets with no seed phrase. Each wallet is a 2-of-2: you hold one half, WalletSuite holds the other, and both are needed to sign. The SDK returns the wallet to you to store or hand to your end user. No full key is ever assembled and there is no seed phrase to phish.

Sign transactions across 84 chains including Ethereum, Base, Bitcoin, Solana, Tron, and more. See [Supported chains](/supported-chains).

| Language   | Package               |
| ---------- | --------------------- |
| **Node**   | `@walletsuite/wallet` |
| **Python** | `walletsuite-wallet`  |

## The model

* **2-of-2 by default.** Each wallet has two shares and both are needed to sign. You hold one. The WalletSuite signing service holds the other.
* **Self-custodial.** Because both shares are needed, WalletSuite can never sign on its own and never has custody. There is no full key sitting anywhere and no seed phrase to phish.
* **One wallet, every chain.** A single wallet works across all 84 chains. The same wallet signs on Ethereum, Bitcoin, Tron, Solana, and the rest. See [One wallet, every chain](/mpc/curves).
* **You hold the wallet.** The SDK returns the wallet to you and never persists it, so you decide where it lives. Store it yourself or hand it to your end user. See [Shares & thresholds](/mpc/key-shares).

## When to use it

|                 | MPC Wallets                                           | Bring-your-own-signer                         |
| --------------- | ----------------------------------------------------- | --------------------------------------------- |
| **Key custody** | Two shares, both needed to sign. No party signs alone | You own the signer (KMS, HSM, custodian)      |
| **You manage**  | One wallet per user. Nothing else to hold             | Your entire signing stack, end to end         |
| **Best for**    | Self-custodial user wallets                           | Plugging into a signing layer you already run |

## Explore the docs

<CardGroup cols={3}>
  <Card title="Quickstart" icon="rocket" href="/mpc/quickstart">
    Install the SDK, create a wallet, derive an address, and sign a transaction end to end.
  </Card>

  <Card title="Architecture" icon="sitemap" href="/mpc/architecture">
    How the two shares work together to keep wallets self-custodial.
  </Card>

  <Card title="Signing" icon="signature" href="/mpc/signing">
    Sign transactions across 84 chains from a single wallet.
  </Card>

  <Card title="One wallet, every chain" icon="diagram-project" href="/mpc/curves">
    Which chains each wallet covers and how addresses are derived.
  </Card>

  <Card title="Shares & thresholds" icon="key" href="/mpc/key-shares">
    Store the wallet you hold, run the default 2-of-2, and see what's on the roadmap.
  </Card>

  <Card title="Recovery" icon="life-ring" href="/mpc/recovery">
    How the default 2-of-2 works and the roadmapped recovery mode.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="SDK reference" icon="book" href="/mpc/sdk-reference">
    Every client, method, argument, and error category in one place.
  </Card>

  <Card title="Security" icon="shield-check" href="/security/overview">
    Audits, build provenance, and the WalletSuite key-management model.
  </Card>

  <Card title="FAQ" icon="circle-question" href="/mpc/faq">
    Short answers to the most common questions about MPC wallets.
  </Card>
</CardGroup>