> For the complete documentation index, see [llms.txt](https://documentation.justbeep.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.justbeep.it/product-overview/riffs/wallet-infrastructure.md).

# Wallet infrastructure

Every user and every riff gets its own self-custody Privy MPC wallet. Users can reach their funds at all times, and Beep never pools customer funds.

<figure><img src="https://2348763252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffrgr0Kse7wRCOlaPSZd7%2Fuploads%2FwEOrUPQE7WsJ0czQf7tQ%2Friffs-wallets.png?alt=media&amp;token=d9d4ccf8-7267-4725-a9e5-cae3f1522e68" alt=""><figcaption></figcaption></figure>

The agent signs trades only through the wallet policy, each riff trades from its own wallet, and every withdrawal path ends at the user.

* **One wallet per user, one funding wallet per riff.** A problem in one riff cannot touch another riff or another user's money.
* **MPC key management through Privy.** No single party holds a full private key. Riffs runs on Privy MPC wallets on Sui.
* **Policy-scoped agent signing.** The agent signs as a delegated signer with limits: allowed venues and contracts, maximum order size and leverage. The user can revoke it anytime.
* **Withdrawals go only to the user.** Funds can leave a riff wallet only for the user's own wallet or linked account.
* **Linked brokerage accounts.** Users connect their own Robinhood and Coinbase accounts through MPC-secured account links. Orders execute inside those accounts, and the money never leaves them.
