Test Cedar end to end
This checklist is for early-access testers evaluating Cedar’s main journeys. It does not replace the task guides: open the linked guide, complete one scenario, then return here to record what happened.
Before you start
Section titled “Before you start”- Choose where to use Cedar and open the apps needed for your scenarios.
- Create an account and activate Pocket with a test account.
- Use only test tokens with no real monetary value.
- Record the device, browser, operating system, selected network, and test asset before you begin.
Follow Send and receive test tokens, then send a small routine test amount from Pocket.
Verify that:
- Pocket becomes usable only after explicit activation.
- Receive stays available when Cedar shows an address before activation.
- The balance updates after test tokens arrive.
- The send reaches a final status in Activity.
Follow Set up Vault, then make one small Vault transfer with Send test tokens.
Verify that:
- Fresh setup finishes in Cedar Wallet for iOS.
- The recovery phrase appears only during protected setup.
- A regular Vault action requests passkey and phone approval.
- Vault and Activity show the final status.
Spending limit
Section titled “Spending limit”Follow Set a spending limit. Create a limit, change it, then remove it.
Verify that:
- Each change uses Vault approval.
- The limit shows the intended amount and reset period.
- Removing the limit changes its status to Off.
- Each change reaches a final status in Activity.
The current Cedar apps do not offer a control to start Move funds to Pocket, so this checklist does not include that transfer.
Crypto app connection
Section titled “Crypto app connection”Follow Connect Cedar to a crypto app. For an end-to-end transaction, continue only when every network the crypto app will use appears in Cedar’s network selector.
Verify that:
- The extension shows the expected site, wallet, and network before connecting.
- Rejecting a request does not connect or submit anything.
- A Pocket request can finish in the extension after activation.
- Removing the connection takes effect in the extension immediately.
Vault request from a crypto app
Section titled “Vault request from a crypto app”Follow Start a Vault request.
Verify that:
- The extension explains that final approval happens on the phone.
- Cedar Wallet for iOS reopens the same request.
- The extension or app shows the final status after approval or rejection.
- Vault message signing is not offered in the extension.
Optional: change a security method
Section titled “Optional: change a security method”Changing a security method can remove an existing approval path. Test it only with an account you control and a replacement method you have already prepared. Follow Change a passkey, trusted phone, or recovery phrase.
Verify that Cedar shows the method and approval path, Activity finishes successfully, Security shows the replacement, and the old method no longer approves actions that now use the replacement.
Optional: recover a passkey
Section titled “Optional: recover a passkey”This scenario replaces account access. Run it only with a test account you control and recovery material you prepared yourself. Follow Recover access after losing a passkey.
Verify that recovery starts while signed out on iOS, requires the trusted phone and recovery phrase, and lets the replacement passkey sign in. The previous passkey must no longer sign in or approve actions as the primary passkey.
What to report
Section titled “What to report”Report problems in the Cedar Discord. A useful report includes:
- the scenario and linked guide
- device, browser, and operating system
- selected network and asset
- where progress stopped
- expected and actual results
- final Activity status, if available
A redacted screenshot can help when it shows the visible state without private material. Never include recovery phrases, private keys, passkey prompts, raw handoff links, or other approval secrets.