> For the complete documentation index, see [llms.txt](https://botlyz.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://botlyz.gitbook.io/docs/english/securite-non-custodial.md).

# Non-custodial security

## Your funds belong to you

Botlyz is a **software editor** and an **automation tool**, not a fund manager.

**Fundamental point: you retain custody of your funds.** Your private keys and your seed phrase never leave your wallet, and Botlyz can neither withdraw nor transfer your capital.

Your cryptocurrencies (USDC and other assets accepted by Lighter) stay in your Lighter account, which only your Ethereum wallet (MetaMask, Ledger, etc.) can access. Botlyz can never withdraw or transfer your capital. A trade-only API key entrusted to Botlyz does, however, allow trading orders to be placed; keep it secure (see [Risk management](#risk-management) below). This non-custodial custody does not remove market or liquidation risk, which remains entirely your responsibility.

## Security architecture

### What you control

✅ Your **MetaMask wallet**: your private key, your seed phrase (12 secret words) ✅ Your **Lighter account**: your Ethereum address, your cryptocurrencies ✅ Your **Lighter API key**: created and stored by you at Lighter

### What Botlyz controls

⚙️ **Only**: your API keys (trade-only) to place **trading** orders

### What Botlyz CANNOT do

❌ Withdraw your funds to an external address ❌ Access your seed phrase or your private key ❌ Change your withdrawal address ❌ Perform non-trading operations (transfers, unlocking, etc.) ❌ Modify the security settings of your Lighter account

## API key configuration

### How the Lighter API key works

When you connect Botlyz to Lighter, you create an **API key with limited permissions**:

1. **You create the key** in your Lighter account (<https://app.lighter.xyz/apikeys>)
2. **The key has specific permissions**: only to **place and cancel orders** (trading)
3. **No withdrawal access**: the key cannot initiate a "secure withdrawal" or other financial operations
4. **You copy it** and give it to Botlyz
5. **Botlyz uses it** to send your trading orders

### Precise permissions

Your Lighter API key:

| Permission          | Allowed | Detail                            |
| ------------------- | ------- | --------------------------------- |
| Place orders        | ✅       | Entry, exit, stop-loss orders     |
| Cancel orders       | ✅       | Cancel unfilled orders            |
| View positions      | ✅       | See the state of your account     |
| View history        | ✅       | See your past trades              |
| **Withdraw funds**  | ❌       | **Not possible with the API key** |
| Modify settings     | ❌       | Not possible                      |
| Create sub-accounts | ❌       | Not possible                      |

> The capabilities of a trade-only key are defined by Lighter, not by Botlyz. With a properly created trade-only key, the key entrusted to Botlyz allows neither withdrawal, nor transfer, nor modification of your account's security settings. Always refer to the effective permissions indicated by Lighter when creating the key.

### EIP-712: personal signature

The Lighter API key is created by signing with **EIP-712**, an Ethereum signature standard:

* **You sign** with MetaMask: this is the only way to authenticate the configuration
* **Botlyz does not have your signature**: only your wallet generates it
* It is like two-factor authentication: Botlyz sends the order, Lighter verifies it with your signature

For more details on signing your configuration, see [Signature and transparency](/docs/english/signature-et-transparence.md).

## Risk management

### If your API key is compromised

**Scenario**: someone else obtains your API key

**What they can do**:

* Place trading orders from your account
* View your history and your positions

**What they CANNOT do**:

* Withdraw your funds
* Access your cryptocurrencies (transfer them or move them out of the account)
* Change your address
* Modify security settings

**Your protection**:

1. **Revoke the key immediately**: go to <https://app.lighter.xyz/apikeys> and delete the compromised key
2. **Create a new key** with a new API Private Key
3. **Reconnect Botlyz** with the new key

The process takes less than 2 minutes. Your funds cannot be withdrawn by a third party, but revoke the key without delay to prevent any unwanted trading orders: as long as the key is active, a third party can place orders that may lead to losses.

### If Botlyz were compromised

**Scenario**: the Botlyz infrastructure is hacked

**Maximum impact**:

* Attackers would obtain the API keys stored on our servers
* They could place or cancel trading orders

**What would remain out of reach**:

Even in the event of a Botlyz compromise, no private key or seed phrase is exposed (Botlyz does not hold them) and no withdrawal of your funds is possible with a trade-only key: your capital cannot be diverted out of your Lighter account. On the other hand, an attacker holding the API key could place or cancel trading orders on your account, which may lead to losses; this is why you must immediately revoke the key at Lighter at the slightest suspicion. No system is infallible, and your capital also remains exposed to market and liquidation risk, as always in trading.

**Security procedure**:

1. We would **immediately revoke all API keys**
2. You would be **notified promptly**
3. You would create a new API key in 2 minutes
4. Botlyz would restart with the new configuration

## Security best practices

### Do

✅ **Back up your seed phrase** (12 words) on paper, in a safe place, offline ✅ **Keep your seed phrase secret**: never photograph it, never share it ✅ **Use a strong password** for MetaMask (12+ characters, unique) ✅ **Enable approval validation** on MetaMask to confirm each transaction ✅ **Verify URLs**: <https://app.lighter.xyz/> and the official Botlyz Telegram channel ✅ **Regularly review** your Lighter history to detect unusual orders ✅ **Revoke the API key** if you do not recognize trades or orders

### Don't

❌ **Never share your seed phrase** ❌ **Never download "wallet generators"** claiming to create a free wallet (scam) ❌ **Never connect your wallet** to suspicious links or application clones ❌ **Never give your API Private Key** to anyone other than Botlyz (via the official channel) ❌ **Do not keep your seed phrase** online (email, cloud, screenshot, text file) ❌ **Never sign** messages you do not understand in MetaMask

## Support and assistance

If you have questions about security or if you suspect an anomaly, contact us via the [Support](/docs/english/support.md) page.

Describe your problem and attach screenshots if possible.

## Ethics statement

Botlyz commits to:

* **Respecting your financial sovereignty**: you remain in control of your funds and your keys
* **Being transparent**: fees and permissions are documented (see [Fees](/docs/english/frais.md))
* **Reducing the technical security risk surface**: relying on Ethereum standards (EIP-712), the non-custodial model, trade-only keys, and encryption of keys at rest. These measures concern only the security of the software and of the keys; they do nothing to reduce market or liquidation risk, which remains entire and independent of these measures. No system is infallible.
* **Never collecting more data than necessary**: only the trading API key is required
* **Informing promptly**: in the event of an incident, you are notified without delay

**You can revoke the API key at any time to regain control over Botlyz's execution.**

> Trading carries a risk of capital loss. You remain solely responsible for your configuration and your decisions. See the [risk warning](/docs/english/avertissement-risques.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://botlyz.gitbook.io/docs/english/securite-non-custodial.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.