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

# Wallet Setup

> Create or import Solana wallets in fees.fun to start saving on fees across all supported platforms.

## Your default wallet

When you log in to fees.fun for the first time, a default Solana wallet is automatically created for you. It's ready to use right away — you can start creating wallets in fees.fun and import them into your launch platforms, or if you already have wallets on those platforms, import them into fees.fun too.

fees.fun needs the private key for any wallet you want to trade with so it can sign transactions at the lower fee rate on your behalf.

<Note>**Axiom is the exception** — it doesn't need wallet import at all. fees.fun works on Axiom automatically without any wallet setup.</Note>

## Choose your path

<Tabs>
  <Tab title="Create a new wallet" icon="plus">
    Want a fresh wallet? fees.fun can create one for you instantly.

    <Steps>
      <Step title="Open the extension popup">
        Click the fees.fun icon in your Chrome toolbar.
      </Step>

      <Step title="Click Create New Wallet">
        In the wallet manager, click the option to create a new wallet.
      </Step>

      <Step title="Name your wallet">
        Give it a descriptive name like "Main Deployer" or "Sniper 1".
      </Step>

      <Step title="Select Solana">
        Choose **Solana** as the chain and click **Create**.
      </Step>
    </Steps>

    Your wallet is created instantly using Turnkey, a non-custodial wallet provider. No seed phrases to deal with — your keys are generated and encrypted on your device.

    <Tip>If you create a new wallet in fees.fun, you'll also need to import its private key into the platform you want to use it on (RapidLaunch, Uxento, J7, etc.).</Tip>
  </Tab>

  <Tab title="Import an existing wallet" icon="file-import">
    Already have wallets on your launch platforms? Import them into fees.fun.

    <Steps>
      <Step title="Get your private key">
        Use the same private key you have on your launch platform. It should be a base58-encoded string.
      </Step>

      <Step title="Open the import flow">
        In the extension popup, click **Import Wallet**.
      </Step>

      <Step title="Paste and save">
        1. Paste your private key
        2. Give the wallet a name
        3. Click **Import**

        Your key is sent straight to Turnkey's secure infrastructure.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Assigning wallets to platforms

After setting up your wallet, you need to tell fees.fun which wallet to use on each platform. This is called assigning a **deployer wallet**.

<Steps>
  <Step title="Open your wallet details">
    In the extension popup, tap on any wallet to see its details.
  </Step>

  <Step title="Assign to platforms">
    You'll see options for each platform (RapidLaunch, Uxento, J7 Tracker). Enable the platforms you want this wallet to deploy on.

    <Info>Each platform uses one deployer wallet at a time. Your first wallet is automatically assigned to all platforms by default.</Info>
  </Step>
</Steps>

<Tip>You can use the same wallet across all platforms, or assign different wallets to different platforms — whatever matches your current setup.</Tip>

## Multiple wallets for sniping & bundling

If you use sniper or bundle features, you'll want multiple wallets in fees.fun:

* **Deployer wallet** — the main wallet that creates the token
* **Sniper / bundle wallets** — additional wallets that buy the token right after launch

Import every wallet you use for sniping on your platforms into fees.fun. The wallet addresses need to match so fees.fun can find the right key when it's time to sign.

<Card title="Learn about sniper wallets" icon="crosshairs" href="/features/sniper-wallets" horizontal>
  Set up multi-wallet bundles for RapidLaunch, Uxento, and J7.
</Card>

## How your keys are protected

<Columns cols={2}>
  <Card title="No keys in our database" icon="database">
    We store zero private keys on our servers. All wallets — created or imported — are managed by Turnkey's secure infrastructure.
  </Card>

  <Card title="Turnkey for key management" icon="shield-halved">
    Wallets created in fees.fun are powered by Turnkey, a non-custodial key infrastructure provider. Your keys live in their hardware-secured environment, not on our servers.
  </Card>
</Columns>

<Note>For more details, see the [Security page](/security).</Note>

## FAQ

<AccordionGroup>
  <Accordion title="Do I still need my wallets set up on the platforms?">
    Yes. You keep your wallets configured on RapidLaunch, Uxento, J7, etc. as usual. fees.fun needs the same wallets imported so it can sign transactions at lower fees.
  </Accordion>

  <Accordion title="Can I use the same wallet across multiple platforms?">
    Yes. Assign the same wallet as the deployer for RapidLaunch, Uxento, and J7 simultaneously — as long as it's set up on those platforms too.
  </Accordion>

  <Accordion title="Do I need SOL in my wallets?">
    Yes — your deployer wallet needs enough SOL to cover the transaction plus the 0.25% fee. Sniper wallets each need SOL equal to the buy amount you set.
  </Accordion>

  <Accordion title="What if I create a new wallet in fees.fun?">
    You'll need to also import that wallet's private key into whatever platform you want to use it on. The private key needs to be on both sides — in the platform and in fees.fun.
  </Accordion>
</AccordionGroup>