> For the complete documentation index, see [llms.txt](https://docs.proxima.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxima.tools/settings/settings.md).

# Settings

## Settings

Configure your account, trade behavior, and display preferences. Access Settings from the bottom bar of the interface.

<div align="left"><figure><img src="/files/zgS1mBOYgLecAREQUKCs" alt="" width="563"><figcaption></figcaption></figure></div>

***

### General

<div align="left"><figure><img src="/files/ZMp9z0lLnkH9omgruEfb" alt="" width="563"><figcaption></figcaption></figure></div>

#### Provider Racing&#x20;

#### Shield

Deploy a personal on-chain program to replace the shared public one. This isolates your execution and prevents on-chain tracking through the default public program.

* **Deploy**: Creates your private program (\~6.5 SOL, refundable on close)
* **Manage**: View status and close your program

Click **Manage** to access Shield controls.

{% hint style="info" %}
Deployment can take up to 3 minutes. If it fails, you can retry.
{% endhint %}

#### Balance Preferences

Choose how balances are displayed across the interface:

* **% Supply**: As a percentage of total supply
* **Token Amount**: As raw token count

***

### Trade Panel

Controls that affect the Live panel behavior globally.

<div align="left"><figure><img src="/files/JpgdmHwjDLBzazkUvkq5" alt="" width="563"><figcaption></figcaption></figure></div>

#### Instant Trade

When enabled, quick trade buttons (preset %) execute immediately without confirmation.

#### Ask for Nuke Confirmation

When enabled, a confirmation modal appears before executing Nuke.

#### **Confirm Dev Trades**&#x20;

When enabled, a confirmation modal appears before executing trades with the dev wallet.

#### Use Nuke Value as Holdings

Switches how Holding and Unrealized P\&L are calculated:

* **Off**: Uses price × quantity of tokens
* **On**: Uses the estimated nuke (sell all) value

***

### Trade Wallets

Controls that affect per-wallet buy and sell behavior in the wallet table.

<div align="left"><figure><img src="/files/5dPZ10ZT9vuZIkyprncH" alt="" width="563"><figcaption></figcaption></figure></div>

#### Individual Instant Buy & Sell

When enabled, each wallet in the table gets instant buy / sell buttons.

* **Instant Buy / Sell Values** : Customize the preset buttons (e.g. 25, 50, 75, 100)
* Add or remove values with **+** and the trash icon
* Reset to defaults with the refresh icon

***

### Licenses

Displays the licenses associated with your account and your current account status.

* Each license is listed by name. The license currently in use is flagged with a green **Current** tag.
* **Dissociate** : remove a license from your account.
* **Associate a new license** : link an additional license to your account.
* **Logout** : disconnect your account.

<div align="left"><figure><img src="/files/mWpdKhbUSGH14HCRKCFX" alt="" width="375"><figcaption></figcaption></figure></div>

### Connections

Manage the authentication methods linked to your account. Each connected method can be used to sign in.

→ See Authentication & Sign-Up for the full sign-in flow.

* **Email** : connect an email address for email-based login. Use **+ Connect email** to add one.
* **Passkeys** : register a device-based passkey (Face ID, Touch ID, security key). Use **+ Add passkey** to add one.
* **Wallets** : connect a wallet as an authenticator. Use **+ Connect wallet** to add one.

{% hint style="info" %}
Connecting multiple methods lets you sign in from different devices and keeps backup access if one method becomes unavailable.
{% endhint %}

<div align="left"><figure><img src="/files/RDhLLh7jFGV43iUYMQkA" alt="" width="375"><figcaption></figcaption></figure></div>

### 2FA

Add a second verification step before protected actions. Once enabled, you are challenged before any protected action runs.

#### Enabling 2FA

Toggle **Two-factor authentication** on, then pick a second factor :

* **Authenticator app** : TOTP code from an app such as Google Authenticator, 1Password, etc.
* **Wallet signature** : sign a confirmation message with your non-custodial wallet.

Once configured, the active method is shown next to the toggle (for example : Wallet · SOLANA · 7tBMjm...Dhbj).

<div align="left"><figure><img src="/files/6RYcaPrjv6wZw1hictrd" alt="" width="375"><figcaption></figcaption></figure></div>

#### Protected actions

Choose which actions require a 2FA challenge :

* **Protect everything** : challenge every protectable action, ignoring the per-action toggles below.
* **wallet.withdraw** : withdraw funds from your wallets.
* **wallet.export\_funder** : export a funder wallet's private key.
* **twofa.change\_settings** : change your 2FA settings.

<div align="left"><figure><img src="/files/kmPdbmQykJ3Nuu4Jfup8" alt="" width="375"><figcaption></figcaption></figure></div>

#### Completing a challenge

When you trigger a protected action, a **Two-factor authentication** modal opens. Complete it with your configured method :

* **Authenticator app** : enter the current TOTP code, then confirm.
* **Wallet signature** : a signature request opens in your connected wallet (for example : Phantom). Sign the message, then click **Verify Signature**.
* **Use Backup Code** : enter a backup code if you cannot use your primary method.
* **Cancel** : stops the action without running it.

<div align="left"><figure><img src="/files/6gu9kFuXC0LPBSD1Wc7X" alt="" width="375"><figcaption></figcaption></figure></div>

#### Backup codes

One-time codes used to regain access if you lose your 2FA device.

* Click **Generate** to create a set. The counter shows how many remain (for example : 0 of 0 remaining).

{% hint style="warning" %}
Generate and save your backup codes when you enable 2FA. Without them, losing access to your 2FA device can lock you out of your account.
{% endhint %}

<div align="left"><figure><img src="/files/VQGIxc1Az1YOuoVZUkdK" alt="" width="375"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/pojxBiiVJ5ck2uYO3UHf" alt="" width="375"><figcaption></figcaption></figure></div>

### Sessions

Review every device currently signed into your account from **Settings > Active Sessions**.

Each entry shows the **OS & Browser**, approximate **Location** (IP-based), and **Last Active** time. Your current session is flagged with a green **Current** tag.

To end a session remotely, click **Log Out** next to the entry — the targeted device is signed out on its next request.

<div align="left"><figure><img src="/files/267mmLOf7oJE5Q5eM5m3" alt="" width="375"><figcaption></figcaption></figure></div>

***

### Customization

Light and dark theme support with customizable appearance.

<div align="left"><figure><img src="/files/HoLdp88XYywS0Xu34cjk" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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.proxima.tools/settings/settings.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.