> For the complete documentation index, see [llms.txt](https://elysia.gitbook.io/elysia-perps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elysia.gitbook.io/elysia-perps/getting-started/connect-and-login.md).

# Connect & Login

Elysia Perps has **no sign-up form and no password**. Your wallet *is* your account. You log in by signing a short message that proves you control your address. Nothing leaves your wallet except a signature, and no funds move during login.

## What you need

* An Ethereum wallet (e.g. MetaMask or any EIP-712-compatible wallet).
* A small amount of the network's gas token for later on-chain actions (deposits and withdrawals). Login itself costs no gas.

## How login works

Logging in takes a single signature:

1. **Connect your wallet.** Click *Connect Wallet*, and approve the connection in your wallet. The app now knows your address but cannot act on your behalf.
2. **Sign the login message.** The app shows you a one-time message containing your address and a random code (a *nonce*). Your wallet asks you to sign it. This signature proves you own the address.
3. **You're in.** The signature is verified and a session is created. The first time you ever log in, your account is created automatically. There is no separate registration step.

```
Connect wallet ─▶ Sign one-time message ─▶ Session created
   (no gas)         (proves ownership)        (auto-created on first login)
```

> **Why a signature instead of a password?** A signature can't be reused or phished into a working password, and it never exposes your private key. The message you sign is single-use and expires in a few minutes, so it can't be replayed later.

## Staying logged in

Once you're in, the app keeps your session alive for you:

* Your session is held in secure, browser-managed cookies, not in a token you have to copy or store.
* A short-lived access credential is **refreshed automatically** in the background as you trade, so you won't be logged out mid-session.
* If you've been away long enough, you'll simply be asked to sign in again.

You never see or handle the session tokens directly. They are stored so that website scripts cannot read them, which protects you from common browser-based attacks.

## Security model

A few protections worth knowing about:

* **One session, one user.** A live connection is bound to the address that signed in; it can't be silently switched to another account.
* **Reuse detection.** Sessions renew using one-time credentials. If an old, already-used credential is ever presented again (a sign of theft), **all of your sessions are invalidated at once** and you'll need to log in again. This is a safety feature, not an error on your part.
* **Rate limiting.** Login and API requests are rate-limited to protect the service from abuse.

## Disconnecting

To disconnect, click your **wallet address** in the top bar to open the menu, then click *Disconnect*. This ends your session and clears the session cookies from your browser. To fully revoke access, also remove the site from your wallet's connected apps.

## Where to go next

* Fund your account: **Getting Started →** [**Deposit**](/elysia-perps/getting-started/deposit.md).
* Understand the unit your balance is shown in: **Getting Started →** [**Collateral**](/elysia-perps/getting-started/collateral.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://elysia.gitbook.io/elysia-perps/getting-started/connect-and-login.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 `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.