Candide Documentation

Safe Simulation is a transaction simulation system designed specifically for Safe accounts to detect security-critical operations that generic wallets often miss. It identifies changes to the Safe's security model—such as adding modules, changing owners, modifying multisig thresholds, or executing delegate calls—and presents them in clear language before a user signs a transaction.

Key security-critical operations detected include:

• enableModule(): Adding new modules that may execute transactions without signatures.
• addOwnerWithThreshold() / removeOwner(): Changes to account ownership.
• changeThreshold(): Modifications to the required number of signatures.
• Delegate calls and guard modifications.

Calibur allows WebAuthn passkeys (such as Face ID, fingerprint sensors, or security keys) to act as secondary signers for a smart account.

Key architectural constraints:

• Registration: Passkey registration must be signed by an admin key (the EOA root key), as only admin keys have permission to call key management functions.
• Usage: Once registered, the passkey can sign regular transactions independently without requiring the root key.
• Key Settings: Each registered key can have its own expiration time, hook, and admin flag.

The Safe Recovery Service API allows developers to register an email address or phone number as a recovery method for a Safe account. Once registered, the service acts as a service-managed guardian. During the recovery process, the user verifies a one-time password (OTP) to obtain a guardian signature, which counts as one approval toward the account's recovery threshold in the Social Recovery Module.

Prerequisites:

• Deploy a Safe account with the Social Recovery Module enabled.
• Obtain a service URL and Bearer token by requesting service access.
• Register recovery methods while the user still has control of the account (registrations are specific to an account and chain).