An everyday Pocket. A 2-of-3 Vault. Explore a clearer way to separate daily activity from decisions that deserve another approval.
Interactive concept only. No wallet connection, real funds or transactions.
01 / A clearer division
The reference introduces two roles: Pocket for everyday transfers and app use, and Vault for a more deliberate approval path. This page makes that distinction visible through an interactive concept—not a claim about a deployed CEDAR service.
THE EVERYDAY LAYER
01Imagine a separate place for routine activity: check what you are doing, review the destination and understand the request before confirming it.
THE DELIBERATE LAYER
02The 2-of-3 model asks for any two of three distinct signers. It adds an approval threshold; its real protection depends on implementation and keeping the signers meaningfully separate.
CEDAR
Authentication is one step. Your decision is another.
02 / Familiar access
Passkeys can use your device's familiar unlock method, such as a PIN or biometrics. Authentication and authorization are different: proving who you are does not by itself decide which transaction should be approved.
Check the website or app you intended to use before starting.
In a real implementation, the device and passkey provider handle authentication. This preview does not request it.
Review the network, destination, permissions and fees in an actual service. A familiar sign-in is not a reason to skip the details.
03 / Make the rule tangible
Tap the signer cards. See what happens with one approval, two approvals, or an unavailable device. Everything here stays an illustration; no signing or blockchain call takes place.
Signer A is unavailable. B and C can still meet the illustrated threshold; a real recovery outcome depends on the actual setup.
Select any two available signer cards to explore the rule.
04 / Think in situations
Use the Pocket concept to think about routine activity. Keep the destination and requested permissions visible, even when the action feels familiar.
Use the Vault concept to explore a pause for a second signer. Independent review is more useful than repeatedly clicking through on the same device.
Test your recovery plan before it matters. Know which signers remain available and where replacement procedures are documented.
05 / Plan before you need it
A threshold is only part of the picture. Access to your remaining signers, the service's replacement rules and the way backups are stored all matter.
Know what each signer is, who controls it and whether it shares a failure point with another.
Two devices in one bag or credentials tied to the same account may fail together. Consider the dependencies, not just the device count.
For an actual testnet service, use test tokens only and follow its documentation. This page itself has no network connection to a wallet.
No. This is a landing-page concept inspired by the supplied CEDAR material. The interactive panel illustrates approval counts; it cannot hold assets or sign transactions.
No. A threshold is not an absolute safety guarantee. Implementation, signer independence, compromise, loss of access and recovery rules all affect the outcome.
No. A passkey is an authentication method. A Vault approval rule determines which authorizations are required. How the two are combined depends on the actual service.
The supplied reference mentions web, iOS and an extension. Verified download links were not provided, so this concept offers only the browser-based demonstration.
Understand the rule. Then explore the experience.
Try one approval. Add a second. Switch to the unavailable-device scenario. A few clicks make the concept much clearer.
Try the approval demo↗Interactive concept only. No wallet connection, real funds or transactions.