> For the complete documentation index, see [llms.txt](https://docs.clique.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clique.tech/clique-wallet/what-is-clique-wallet/key-concepts.md).

# Key Concepts

Understanding Clique Wallet requires familiarity with several key concepts:

**Embedded Wallets**: Unlike traditional wallet applications that require separate installations or browser extensions, Clique Wallet's embedded wallets are integrated directly into your application. Users interact with their wallets seamlessly within your interface, creating a unified experience without context switching.

**Trusted Execution Environment (TEE)**: TEE is a secure area within a processor that ensures code and data are protected from unauthorized access, even from privileged software. Clique Wallet uses Intel SGX, a specific TEE implementation, to create hardware-protected enclaves where all cryptographic operations—key generation, storage, and transaction signing—are performed in complete isolation.

**Custodial vs. Self-Custodial**: Traditional custodial wallets give service operators access to user private keys, creating a trust dependency. Self-custodial wallets give users full control but require them to manage seed phrases and private keys. Clique Wallet combines both approaches: users get the convenience of a custodial wallet (no seed phrase management) with the security guarantees of self-custody (service operators cannot access keys).

**Multi-Chain Support**: Clique Wallet natively supports multiple blockchain networks, allowing users to manage assets across different ecosystems from a single account. Each network type (Solana, EVM-compatible chains, Hyperliquid) has its own wallet addresses, but they're all managed under one unified user account.

**Wallet Sets**: Users can create multiple wallets on each supported blockchain. The primary wallet (Main) is created automatically, while additional wallets (Forward wallets, Secondary wallets) can be created for different purposes such as separating funds, managing different trading strategies, or organizing assets by use case.

**Authentication Methods and Account Binding**: Clique Wallet supports multiple authentication methods including social OAuth (Google, X/Twitter, Telegram, etc.), email/phone verification, Apple Sign-In, and external wallet connections (MetaMask, Phantom, Okx, Rabby, Coinbase Wallet, etc.). Users can bind multiple authentication methods to a single account, enabling flexible access while maintaining the same wallets and assets.

**API Keys**: For programmatic access, Clique Wallet provides API keys with customizable permission scopes. These keys enable automated operations while maintaining security through IP whitelisting and granular permission controls.

**Export Functionality**: Users can export their private keys through a secure two-step process with verification. This provides an escape hatch, allowing users to migrate their wallets to other services if needed. The export process requires active authentication with verification to prevent unauthorized access.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.clique.tech/clique-wallet/what-is-clique-wallet/key-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.