Connect to crypto apps
The Cedar Chrome extension lets a crypto app see one Cedar wallet and ask for actions. Connecting shares the selected public address and network; it does not approve future messages or transactions.
Connect an app
Section titled “Connect an app”- Install the Chrome extension and sign in.
- Select Pocket or Vault and the intended network.
- In the crypto app, choose its connect-wallet action and select Cedar Wallet.
- In Cedar, check the site address, wallet, and network, then choose Connect app.
Pocket can share its address before activation, but signing and transaction requests stay blocked until Pocket is active. Finish Vault setup before connecting Vault to a new app.
Review each request
Section titled “Review each request”Before approving, compare the requesting site, wallet, network, token, amount, recipient, message, and contract action with what you started. Reject anything you cannot explain.
Pocket requests can normally finish in the extension. A Pocket message signature may prove control of the wallet without moving tokens, but you should still read the message or payload first.
If Cedar offers Queue this request, queuing only saves it briefly. It does not approve, sign, or submit anything; each queued request still receives its own review.
Vault requests
Section titled “Vault requests”Supported Vault transactions can start in the extension, but approval finishes in Cedar Wallet for iOS. Choose Continue on phone, then confirm that the site, wallet, network, and action match before completing the passkey and phone approvals.
Vault message signing is not supported in the extension. Extension-started Vault sends use phone approval rather than the recovery phrase.
Disconnect an app
Section titled “Disconnect an app”Open Connected apps, choose the app and wallet, then remove one network or all connected networks. The extension stops sharing the account immediately; other Cedar surfaces may take a moment to update.
Disconnecting cannot make an app forget an address it already saw. It also does not revoke token allowances or other permissions recorded onchain.