> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crossmint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Device Key Signer

> Configure a device key signer that uses the device's secure enclave for wallet operations.

<Warning>
  **You are viewing docs for the previous version of the Wallets SDK.** We recommend upgrading to V1.
  See the [updated version of this page](/wallets/guides/signers/device-key) or the [V1 migration guide](/wallets/guides/migrate-to-v1).
</Warning>

A device key signer uses P-256 keys generated inside the secure storage of the user's phone, computer, or browser — such as the iOS Secure Enclave, Android Keystore, or the browser's built-in credential store. These keys are non-extractable and never leave the device.

By default, signing is silent — transactions can be authorized without requiring the user to actively confirm each one. Device keys can optionally be configured to require biometric authentication on every use, or after a configurable idle period.

For a conceptual overview, see [Device key](/wallets/v0/concepts/wallet-signers#device-key) in the Wallet Signers guide. To learn how to register additional operational signers on an existing wallet, see [Registering a signer](/wallets/v0/guides/signers/registering-a-signer).

## Configuration

<Info>
  Detailed configuration guides for device key signers are coming soon. <a href="https://www.crossmint.com/contact/sales" target="_blank">Contact our team</a> if you need help setting up device key signers for your project.
</Info>
