Understand Pocket

Think of Pocket as the part of Cedar you keep within easy reach. It is designed for receiving tokens, making routine sends, and connecting to crypto apps without turning every action into a multi-step approval.

Pocket actions normally need only your passkey. That convenience is a deliberate trade-off: Pocket does not use Vault’s 2-of-3 approval for everyday activity, so balances that deserve an extra check belong in Vault.

Cedar presents one logical Pocket, even when you use it across more than one supported network. Changing the selected network changes what you are viewing; it does not create another user-facing Pocket.

What Pocket handles

Receive supported tokens whenever Cedar shows your Pocket address, including before activation.
Send supported tokens after activation.
Connect to crypto apps through the Cedar Chrome extension.
Show trusted tokens and custom tokens you have imported.
Receive funds made available by a Vault spending limit through Move funds to Pocket.

Setting a spending limit does not move tokens by itself. Cedar’s current apps do not offer a control to start Move funds to Pocket; the spending-limit guide explains the current boundary.

Before activation

Pocket can show its address before the wallet is active onchain. That is why you can receive tokens first, as long as the sender uses the same supported network shown in Cedar.

Under the hood: Cedar can calculate this counterfactual address before it creates the smart account onchain. Receiving does not create or activate the account; it simply sends tokens to the address that Pocket will use.

Receiving does not activate Pocket. Cedar waits for you to choose Activate and approve the setup with your passkey. Until it finishes, Pocket cannot send, use spending limits, sign messages, or approve app transactions.

If Cedar shows Pocket setup needed or Activate, return to Pocket and finish activation before retrying the blocked action. Follow Create your account and activate Pocket for the complete walkthrough.

Using Pocket

Before a send, app request, or signature, check the wallet, network, asset, amount, recipient, site, and requested action. Your passkey prompt should match something you just started.

Reject anything you do not recognize. Because one passkey can approve normal Pocket activity, keep routine balances here and use Vault for balances that should not depend on one approval method.

If Cedar says a token balance is unavailable, it has not confirmed the amount. Send and Max stay blocked until a refresh succeeds; an unavailable balance is not the same as zero.

Activity

Use Activity to follow receives, sends, app requests, and activation. It is also where Cedar lets you reopen work that needs attention or resume an unfinished action.