> For the complete documentation index, see [llms.txt](https://cre8-docs.gitbook.io/cre8-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cre8-docs.gitbook.io/cre8-docs/other-products/cre8-wallet/wallet-architecture-and-key-management.md).

# Wallet Architecture and Key Management

* **Key Generation:** When a user signs up for CRE8 and doesn’t already have a Solana wallet, the platform will assist in creating one. This likely involves generating a new keypair (public/private key) for the user. The private key can be derived from a mnemonic seed phrase. The wallet generation process emphasizes that **the user must back up their seed phrase** in a safe place (just like any crypto wallet). CRE8 might provide a user-friendly onboarding with warnings and a step-by-step backup flow.
* **Non-Custodial Nature:** The private keys are typically stored locally on the user’s device:
  * In the web app, the key might be stored in the browser’s local storage encrypted by a password the user sets (or integrated with existing browser wallet extensions, meaning the user might not even expose their key to the web app if they use Phantom, etc.).
  * In the mobile apps, the key would be stored securely, often using the device’s secure enclave or keystore. The user might unlock the app with a PIN or biometrics, which then decrypts the key for use.
* **Multi-Account Support:** The wallet could allow managing multiple accounts (keypairs) if a user wants to separate different identities or businesses.
* **Standard Compatibility:** The wallet likely adheres to Solana’s standards (using ed25519 keys, possibly the same derivation path as other Solana wallets) so that it’s interoperable. A user could import their Phantom wallet into CRE8 Wallet or export their CRE8 Wallet keys to other wallets if they wish.