Wallet Lifecycle

An MPC wallet moves through a small set of steps, each unlocking a different set of SDK calls. You create the wallet, store it, derive an address with no network call, and sign. It is 2-of-2 by default, so keep the wallet you store safe.

State	What it means	SDK calls you can make	How you reach the next state
Created	You created the wallet and hold it. You have the wallet blob in memory.	`createWallet` / `create_wallet` returned.	Save the wallet to your own storage.
Persisted	The wallet lives in durable storage you control. Keep it safe.	Load the wallet back, then call `deriveAddress` / `derive_address`.	Derive an address from the wallet.
Address derived	You have an on-chain address. No network call was made.	`deriveAddress` / `derive_address` (repeatable, including custom derivation paths).	Fund the address, then sign.
Signing	The wallet is ready to sign.	`signEvm7702`, `signEvm1559`, `signTron`, `signBitcoin`, `signSolana`. The SDK signs but does not broadcast.	Broadcast the signed transaction through your own RPC or the WalletSuite API.

In the default 2-of-2 setup, the wallet you save is your half, so keep it somewhere durable. See Recovery.

Next steps

Quickstart

Run the full lifecycle in code. Create, save, derive, and sign end to end.

Shares & thresholds

Save the wallet, run the default 2-of-2, and see what’s on the roadmap.

End-to-end walkthrough Architecture & Security

Get Started

Concepts

Building

Reference

Next steps

Quickstart

Shares & thresholds

​Next steps

Quickstart

Shares & thresholds

Next steps