> 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/installation-pas-a-pas/connecter-votre-wallet.md). # Connect your wallet ## About the connection Botlyz uses **wallet signature** login (Sign-In-With-Ethereum, or SIWE). Connecting means proving that you control an Ethereum address, nothing more. No blockchain transaction is committed, no funds are authorized for transfer, and Botlyz never manages your private keys or your capital. ## Which wallet should you use? If you don't have a wallet yet, we recommend **Rabby Wallet** ([rabby.io](https://rabby.io)) over MetaMask: same idea (a browser extension), but a better DeFi experience, transaction simulation before signing, and smoother multi-network handling. MetaMask, Ledger and WalletConnect remain compatible. ## How it works The login flow is simple and transparent: ### Step 1: Request a nonce You enter your wallet address (for example `0x1234...`). Botlyz generates a **nonce** (a unique, single-use code) associated with that address. ### Step 2: Sign the message Botlyz presents you with a readable message including: * Your wallet address * The unique nonce * An explicit text: "Signing proves that you control this wallet. No transaction, free." You sign this message with your wallet (MetaMask, Ledger, WalletConnect, etc.) by clicking "Sign". It is an **off-chain** operation, **free**, and it changes nothing on the blockchain. ### Step 3: Verification and session Botlyz cryptographically verifies that the signature matches your address. If it is correct, you are connected. Botlyz creates a **JWT session** that authenticates you for the following actions (creating strategies, managing your accounts, etc.). The **nonce is immediately invalidated** after use, so it cannot be replayed by an attacker. ## Security: what the signature does not allow * **Your private keys stay with you**: you control them. They are never sent to Botlyz or to a third party. * **No funds are authorized**: the login signature gives Botlyz no access to your capital or your tokens. * **No blockchain transaction**: there is no on-chain trace of your connection, no gas fee, no delay. * **Single-use nonce**: the signed message can only be used once. Someone else cannot replay your signature. Botlyz is an automation software editor, in **non-custodial** mode: your funds and your keys stay with you, and you are the one who signs your configuration. To learn more, see [Non-custodial security](/docs/english/securite-non-custodial.md). ## If you forget your wallet If you log out or if your session expires: * Simply reconnect with the same address and sign a new message. * No personal account (email, password) to manage or reset. ## Next steps After connecting: 1. **Connect a Lighter account** to start trading (see [Connect your account to Botlyz](/docs/english/installation-pas-a-pas/connecter-un-compte-lighter.md)). 2. **Accept the terms and conditions** if this is your first time (acknowledgment of risks and review of fees). The only fee specific to Botlyz is a protocol fee of 10 bps (0.10%), automatically charged on each order, as detailed in [Fees](/docs/english/frais.md). 3. **Create or deploy a strategy** from the catalog or the builder (see [Deploy a strategy](/docs/english/installation-pas-a-pas/deployer-une-strategie.md)). As a reminder, trading carries a risk of capital loss and past performance does not guarantee future results. See [Risk warning](/docs/english/avertissement-risques.md). ## Frequently asked questions **Q. Does my connection collect personal data?** In the app, Botlyz only records your public Ethereum address (an anonymous identifier) and your preferences (language, strategies): no email, no password, and **no third-party tracker** (the app's audience measurement is anonymous and first-party). The marketing site (botlyz.com), however, uses Google Analytics for audience measurement **subject to your consent** (cookie banner); details in the [Privacy Policy](https://botlyz.com/en/confidentialite.html). **Q. Can I connect with multiple wallets?** Yes, each wallet gets its own Botlyz account. Your strategies and exchange accounts are isolated per wallet. **Q. What happens if I sign a login message by accident?** No risk. The login message is readable and explicit ("Botlyz, login"). A login signature can only connect you: it cannot send money, authorize access, or change anything. **Q. What if someone asks me to sign a message "to verify my identity"?** Be careful. Never sign a message you do not understand or that someone else requests. The only legitimate reason to sign a Botlyz message is connecting to botlyz.com (the flow you see here) or approving a strategy before its deployment. --- # 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 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/installation-pas-a-pas/connecter-votre-wallet.md?ask=&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 `automate deployments from our CI pipeline` 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.