Common flows to create self-custodial user wallets include:
  • Creating wallets with a user owner. This configures wallets such that users are the only entity that can update policies, add additional signers, export the wallet, or change the wallet’s owner. If you create wallets via one of Privy’s client-side SDKs, your app’s wallets are automatically created with user owners.
  • Creating wallets with a 1-of-n key quorum, where one member of the key quorum is the user. This gives users full permissions over their wallet, while enabling other parties to easily update wallets (e.g. policies and signers) and take actions with them.
You can extend self-custodial user wallets to support various use cases, as outlined below.

Offline actions

Take actions with wallets while users are offline, such as limit orders, agentic trading, and portfolio rebalancing.

Multi-party approvals

Require that both users and servers sign transaction requests.

Send transactions from your server

Send transactions from your server for increased control over transaction flows.

Update wallets from your server

Update the policies and signers assigned to wallets from your server, even when users are offline.

Export wallets from your server

Export wallets from your server to enable users to recover their account outside of your core application.