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

# Wallet Types

> Overview of the three wallet types supported on Limitless Exchange

Limitless supports three wallet types: **Externally Owned Accounts (EOA)**, **Embedded Wallets**, and **Smart Wallets**. Each type has different characteristics and tradeoffs for users.

## Externally owned account (EOA)

An **Externally Owned Account (EOA)** is a blockchain account controlled by a user via a private key. The private key is a secret value used to sign transactions. It must be kept secure and never shared.

**Common EOA wallet interfaces:** [MetaMask](https://metamask.io/), [Rainbow](https://rainbow.me/en/), [Coinbase Wallet](https://www.coinbase.com/en-pt/wallet), [Rabby](https://rabby.io/), and similar browser extensions or mobile apps.

**On Limitless:** You connect an EOA from the main login menu. For every on-chain transaction, you must approve it in your wallet interface (e.g., MetaMask).

<Frame caption="EOA wallet connection options on Limitless">
  <img className="block dark:hidden" src="https://mintcdn.com/limitless/KX4_j-Y88TyVRbCP/images/externally-owned-accounts-light.png?fit=max&auto=format&n=KX4_j-Y88TyVRbCP&q=85&s=757acd1241eb13c5adbca9608fd87400" alt="Login screen showing MetaMask, Coinbase Wallet, Base, and other wallet options" style={{maxWidth: "320px"}} width="720" height="1356" data-path="images/externally-owned-accounts-light.png" />

  <img className="hidden dark:block" src="https://mintcdn.com/limitless/KX4_j-Y88TyVRbCP/images/externally-owned-accounts-dark.png?fit=max&auto=format&n=KX4_j-Y88TyVRbCP&q=85&s=27d3f43f5842c43d264e23fb43808aae" alt="Login screen showing MetaMask, Coinbase Wallet, Base, and other wallet options" style={{maxWidth: "320px"}} width="720" height="1356" data-path="images/externally-owned-accounts-dark.png" />
</Frame>

## Embedded wallet

An **Embedded Wallet** is a non-custodial wallet created and operated within an application by a third-party provider, without a separate wallet app.

**On Limitless:** When you sign in via social login (e.g., Google, Twitter), an embedded wallet is created automatically after authentication. You can execute transactions directly from the app without an extra approval step in an external wallet.

<Frame caption="Social login options for creating an embedded wallet">
  <img className="block dark:hidden" src="https://mintcdn.com/limitless/KX4_j-Y88TyVRbCP/images/embedded-wallets-light.png?fit=max&auto=format&n=KX4_j-Y88TyVRbCP&q=85&s=663bb33546171d3dd1fd272ffe82be51" alt="Login screen showing email, Google, Twitter, and other social sign-in options" style={{maxWidth: "320px"}} width="720" height="1556" data-path="images/embedded-wallets-light.png" />

  <img className="hidden dark:block" src="https://mintcdn.com/limitless/KX4_j-Y88TyVRbCP/images/embedded-wallets-dark.png?fit=max&auto=format&n=KX4_j-Y88TyVRbCP&q=85&s=d1be16c5bf517f88242a91e4a431a3dd" alt="Login screen showing email, Google, Twitter, and other social sign-in options" style={{maxWidth: "320px"}} width="720" height="1556" data-path="images/embedded-wallets-dark.png" />
</Frame>

## Smart wallet

A **Smart Wallet** is an account implemented as a smart contract on-chain. It supports features such as:

* Account recovery
* Programmable logic for custom behavior
* Gas fee abstraction and batched transactions

**On Limitless:** Smart wallets are used primarily to remove the need to hold native tokens (e.g., ETH) to pay transaction fees. You sign in via social login, and a smart wallet instance is created based on your embedded wallet. Limitless sponsors transaction fees, so you only need to hold **USDC** for trading activity.

## Trading wallet mode

Accounts connected with an external wallet may see a one-time **"choose your trading wallet"** prompt offering 1-click (smart wallet) trading. Accepting it sets your profile's trading mode to smart wallet: app trades then run gas-free through a smart wallet instead of requiring a confirmation in your external wallet for every action. The prompt does not reappear after you choose.

This choice matters if you later trade **through the API**: in smart-wallet mode, orders signed with your external wallet's own key are rejected. Developers can switch the profile back to EOA trading mode with a single authenticated call. See [Trading wallet mode](/developers/eip712-signing#trading-wallet-mode-whose-address-signs) in the developer docs.

## Summary

| Wallet Type  | Created When                        | Fee Responsibility    | User Experience                                      |
| ------------ | ----------------------------------- | --------------------- | ---------------------------------------------------- |
| **EOA**      | External wallet connection          | User pays gas in ETH  | Requires approval per transaction in external wallet |
| **Embedded** | Social login                        | User pays gas in ETH  | In-app transactions; no external approval step       |
| **Smart**    | Social login (from embedded wallet) | Platform sponsors gas | You hold only USDC; no native token needed for fees  |

## Exporting private keys

How (and whether) you can export a private key depends on the wallet type:

* **EOA wallet**: your wallet interface (MetaMask, Rabby, Coinbase Wallet, etc.) manages the private key. Follow that wallet's export instructions — Limitless never has access to it.
* **Embedded wallet**: the wallet is created and secured by the embedded-wallet provider (Privy). By design, the raw private key is **not exposed** to the app or to the user. This is a provider-level security guarantee, not a Limitless restriction, so the key cannot be exported for external signing.
* **Smart wallet**: a smart wallet is a contract account and does not have a single private key. It is controlled by its owner key (the embedded wallet), which is also non-exportable.

<Note>
  For programmatic trading from a social-login account, you cannot lift the
  embedded wallet's key into an external script. Instead, either:

  * Trade from a **separate EOA** whose private key you control (sign orders yourself), or
  * Use **delegated signing** via the [Programmatic API](/developers/programmatic-api), where the server signs on your behalf using the managed embedded wallet — no private key handling required.

  See [Authentication](/developers/authentication) and
  [EIP-712 Order Signing](/developers/eip712-signing) for the full flows.
</Note>

<Warning>
  A Limitless **API token secret** is not a wallet private key. It is shown
  **once at creation** and cannot be retrieved afterward — if you lose it, derive
  a new token from the Limitless UI.
</Warning>

## Depositing and withdrawing funds

Limitless does not hold a platform balance — your USDC always lives in your wallet on **Base**. Depositing and withdrawing therefore look different depending on your wallet type.

### Depositing

* **EOA wallet**: bridge or send USDC on Base to your EOA address. Once the balance is on Base, it is immediately usable for trading.
* **Embedded or smart wallet** (social login): the Limitless UI shows your embedded and smart wallet addresses. Send USDC on Base to that address to fund the account. You do not need to hold ETH for gas when trading from a smart wallet.

### Withdrawing

* **EOA wallet**: your USDC already sits in your own wallet. To move it elsewhere, send it from your wallet interface (MetaMask, Rabby, etc.) like any other ERC-20 transfer on Base. Limitless does not need to be involved.
* **Embedded or smart wallet** (social login): use the **Withdraw** action inside the Limitless UI to transfer USDC from your smart wallet to another address on Base. Gas is sponsored by the platform.
* **Programmatic partners**: server-managed wallets withdraw via the [`POST /portfolio/withdraw`](/api-reference/portfolio/withdraw) endpoint. The destination address must either be the authenticated account, its smart wallet, or an allowlisted withdrawal address on the profile.

<Note>
  All deposits and withdrawals settle on **Base**. Sending USDC from another chain (Ethereum mainnet, Arbitrum, etc.) without bridging first will not be credited — bridge to Base before sending.
</Note>